{
  "$schema": "folio-library-document/v1",
  "id": "9789240101197-eng",
  "title": "Digital transformation handbook for health supply chain architecture",
  "variant": "pdf",
  "pages": 78,
  "tocSource": "inferred",
  "tocMethod": "contents",
  "toc": [
    {
      "level": 1,
      "title": "Acknowledgements",
      "number": null,
      "page": 6,
      "pageLabel": "iv",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-000-acknowledgements"
    },
    {
      "level": 1,
      "title": "Abbreviations and acronyms",
      "number": null,
      "page": 7,
      "pageLabel": "v",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-001-abbreviations-and-acronyms"
    },
    {
      "level": 1,
      "title": "Glossary",
      "number": null,
      "page": 8,
      "pageLabel": "vi",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-002-glossary"
    },
    {
      "level": 1,
      "title": "Introduction",
      "number": null,
      "page": 11,
      "pageLabel": "1",
      "confidence": 0.75,
      "evidence": [
        "contents",
        "body"
      ],
      "source": "inferred",
      "section": "sec-003-introduction"
    },
    {
      "level": 1,
      "title": "Defining a holistic DHSC strategy",
      "number": "1",
      "page": 19,
      "pageLabel": "9",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-004-1-defining-a-holistic-dhsc-strategy"
    },
    {
      "level": 2,
      "title": "Why is a strategy necessary?",
      "number": null,
      "page": 20,
      "pageLabel": "10",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-005-why-is-a-strategy-necessary"
    },
    {
      "level": 2,
      "title": "Step 1. Identify and engage all relevant stakeholders",
      "number": null,
      "page": 22,
      "pageLabel": "12",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-006-step-1-identify-and-engage-all-relevant-stakehol"
    },
    {
      "level": 2,
      "title": "Step 2. Analyse the current state of HSCISs",
      "number": null,
      "page": 23,
      "pageLabel": "13",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-007-step-2-analyse-the-current-state-of-hsciss"
    },
    {
      "level": 2,
      "title": "Step 3. Define the DHSC vision and strategic goals and objectives",
      "number": null,
      "page": 24,
      "pageLabel": "14",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-008-step-3-define-the-dhsc-vision-and-strategic-goal"
    },
    {
      "level": 2,
      "title": "Step 4. Define a strategic roadmap and performance indicators",
      "number": null,
      "page": 25,
      "pageLabel": "15",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-009-step-4-define-a-strategic-roadmap-and-performanc"
    },
    {
      "level": 1,
      "title": "Defining the DHSC architecture",
      "number": "2",
      "page": 27,
      "pageLabel": "17",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-010-2-defining-the-dhsc-architecture"
    },
    {
      "level": 2,
      "title": "Is a DHSC architecture necessary?",
      "number": null,
      "page": 28,
      "pageLabel": "18",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-011-is-a-dhsc-architecture-necessary"
    },
    {
      "level": 2,
      "title": "What are the risks of forgoing a DHSC architecture?",
      "number": null,
      "page": 28,
      "pageLabel": "18",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-012-what-are-the-risks-of-forgoing-a-dhsc-architectu"
    },
    {
      "level": 2,
      "title": "Step 1. Assess the current state of HSCISs",
      "number": null,
      "page": 30,
      "pageLabel": "20",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-013-step-1-assess-the-current-state-of-hsciss"
    },
    {
      "level": 2,
      "title": "Step 2. Define a target DHSC architecture",
      "number": null,
      "page": 32,
      "pageLabel": "22",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-015-step-2-define-a-target-dhsc-architecture"
    },
    {
      "level": 2,
      "title": "DHSC architecture framework",
      "number": null,
      "page": 32,
      "pageLabel": "22",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-014-dhsc-architecture-framework"
    },
    {
      "level": 2,
      "title": "Illustrative architectural approaches and governance options",
      "number": null,
      "page": 35,
      "pageLabel": "25",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-016-illustrative-architectural-approaches-and-govern"
    },
    {
      "level": 2,
      "title": "Step 3. Identify implementation activities and map them to strategic goals",
      "number": null,
      "page": 42,
      "pageLabel": "32",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-017-step-3-identify-implementation-activities-and-ma"
    },
    {
      "level": 1,
      "title": "Planning for scalable implementation and sustainable operations",
      "number": "3",
      "page": 44,
      "pageLabel": "34",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-018-3-planning-for-scalable-implementation-and-susta"
    },
    {
      "level": 2,
      "title": "Step 1. Plan the implementation of each DHSC intervention",
      "number": null,
      "page": 47,
      "pageLabel": "37",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-019-step-1-plan-the-implementation-of-each-dhsc-inte"
    },
    {
      "level": 2,
      "title": "Step 2. Develop an operational plan for each DHSC intervention",
      "number": null,
      "page": 48,
      "pageLabel": "38",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-020-step-2-develop-an-operational-plan-for-each-dhsc"
    },
    {
      "level": 2,
      "title": "Step 3. Develop a budget for each DHSC intervention",
      "number": null,
      "page": 49,
      "pageLabel": "39",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-021-step-3-develop-a-budget-for-each-dhsc-interventi"
    },
    {
      "level": 2,
      "title": "Step 4. Implement each DHSC intervention",
      "number": null,
      "page": 51,
      "pageLabel": "41",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-022-step-4-implement-each-dhsc-intervention"
    },
    {
      "level": 1,
      "title": "Using the DHSC to implement traceability",
      "number": "4",
      "page": 53,
      "pageLabel": "43",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-023-4-using-the-dhsc-to-implement-traceability"
    },
    {
      "level": 2,
      "title": "What is traceability?",
      "number": null,
      "page": 54,
      "pageLabel": "44",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-024-what-is-traceability"
    },
    {
      "level": 2,
      "title": "Why is traceability important?",
      "number": null,
      "page": 54,
      "pageLabel": "44",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-025-why-is-traceability-important"
    },
    {
      "level": 2,
      "title": "Traceability models",
      "number": null,
      "page": 54,
      "pageLabel": "44",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-026-traceability-models"
    },
    {
      "level": 1,
      "title": "Country examples",
      "number": "5",
      "page": 57,
      "pageLabel": "47",
      "confidence": 0.8,
      "evidence": [
        "contents",
        "body",
        "number"
      ],
      "source": "inferred",
      "section": "sec-027-5-country-examples"
    },
    {
      "level": 2,
      "title": "Ethiopia’s DHSC initiative",
      "number": null,
      "page": 58,
      "pageLabel": "48",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-028-ethiopias-dhsc-initiative"
    },
    {
      "level": 2,
      "title": "Malawi’s DHSC initiative",
      "number": null,
      "page": 60,
      "pageLabel": "50",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-029-malawis-dhsc-initiative"
    },
    {
      "level": 2,
      "title": "Rwanda’s DHSC initiative",
      "number": null,
      "page": 63,
      "pageLabel": "53",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-030-rwandas-dhsc-initiative"
    },
    {
      "level": 1,
      "title": "References",
      "number": null,
      "page": 65,
      "pageLabel": "55",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-031-references"
    },
    {
      "level": 1,
      "title": "Principles for digital development",
      "number": "Annex 1",
      "page": 66,
      "pageLabel": "56",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-032-annex-1-principles-for-digital-development"
    },
    {
      "level": 1,
      "title": "Steering committee example structure",
      "number": "Annex 2",
      "page": 67,
      "pageLabel": "57",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-033-annex-2-steering-committee-example-structure"
    },
    {
      "level": 1,
      "title": "Template for prioritizing DHSC challenges to address",
      "number": "Annex 3",
      "page": 68,
      "pageLabel": "58",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-034-annex-3-template-for-prioritizing-dhsc-challenge"
    },
    {
      "level": 1,
      "title": "Illustrative template that maps today’s challenges to future outcomes",
      "number": "Annex 4",
      "page": 69,
      "pageLabel": "59",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-035-annex-4-illustrative-template-that-maps-todays-c"
    },
    {
      "level": 1,
      "title": "Template for listing health supply chain information systems",
      "number": "Annex 5",
      "page": 70,
      "pageLabel": "60",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-036-annex-5-template-for-listing-health-supply-chain"
    },
    {
      "level": 1,
      "title": "Risk register template",
      "number": "Annex 6",
      "page": 71,
      "pageLabel": "61",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-037-annex-6-risk-register-template"
    },
    {
      "level": 1,
      "title": "Resource matrix for DHSC implementation",
      "number": "Annex 7",
      "page": 72,
      "pageLabel": "62",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-038-annex-7-resource-matrix-for-dhsc-implementation"
    }
  ],
  "sections": [
    {
      "id": "sec-front-matter",
      "number": null,
      "title": "Front matter",
      "level": 1,
      "pageStart": 1,
      "pageEnd": 6,
      "labelStart": "A",
      "labelEnd": "iv",
      "words": 787,
      "summary": {
        "text": "Front matter of the Digital transformation handbook for health supply chain architecture (SMART Guidelines collection), giving the title, ISBNs, 2024 WHO copyright, CC BY-NC-SA 3.0 IGO licence terms, suggested citation, disclaimers and the table of contents covering the introduction, five chapters, references and seven annexes.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "dhsc architecture",
          "heading": false
        },
        {
          "term": "dhsc initiative",
          "heading": false
        },
        {
          "term": "dhsc intervention",
          "heading": false
        },
        {
          "term": "chain architecture",
          "heading": false
        },
        {
          "term": "transformation handbook",
          "heading": false
        },
        {
          "term": "digital transformation",
          "heading": false
        },
        {
          "term": "creative commons",
          "heading": false
        },
        {
          "term": "step",
          "heading": false
        }
      ],
      "extract": "Digital transformation handbook for health supply chain architecture Digital transformation handbook for health supply chain architecture Digital transformation handbook for health supply chain architecture (SMART Guidelines collection) ISBN 978-92-4-010119-7 (electronic version) ISBN 978-92-4-010120-3 (print version) © World Health Organization 2024 Some rights reserved. This work is available under the Creative",
      "extractCut": true,
      "blocks": [
        "library/9789240101197-eng/blocks/prose-sec-front-matter"
      ]
    },
    {
      "id": "sec-000-acknowledgements",
      "number": null,
      "title": "Acknowledgements",
      "level": 1,
      "pageStart": 6,
      "pageEnd": 7,
      "labelStart": "iv",
      "labelEnd": "v",
      "words": 365,
      "summary": {
        "text": "Acknowledgements naming the handbook's authors, Carl Leitner and Swaroop Jayaprakash of the WHO Department of Digital Health and Innovations and Ramy Guirguis of USAID, listing the reviewers and their organizations (including GS1, PATH, GIZ, Global Fund, Gavi, UNICEF and the ministries of health of Rwanda and Zambia), noting that declarations of interest identified no conflicts, and stating that the work was funded by USAID.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "usaid ghsc-psm",
          "heading": false
        },
        {
          "term": "ramy guirguis",
          "heading": false
        },
        {
          "term": "swaroop jayaprakash",
          "heading": false
        },
        {
          "term": "carl leitner",
          "heading": false
        },
        {
          "term": "usa",
          "heading": false
        },
        {
          "term": "global fund",
          "heading": false
        },
        {
          "term": "palladium",
          "heading": false
        },
        {
          "term": "south africa",
          "heading": false
        }
      ],
      "extract": "The World Health Organization (WHO) is grateful for the contributions of many individuals and organizations in the development of this handbook. This handbook was authored by Carl Leitner and Swaroop Jayaprakash of the WHO Department of Digital Health and Innovations (DHI) and Ramy Guirguis of the United States Agency for International Development (USAID). The following individuals (in alphabetical order) reviewed",
      "extractCut": true
    },
    {
      "id": "sec-001-abbreviations-and-acronyms",
      "number": null,
      "title": "Abbreviations and acronyms",
      "level": 1,
      "pageStart": 7,
      "pageEnd": 8,
      "labelStart": "v",
      "labelEnd": "vi",
      "words": 151,
      "summary": {
        "text": "List of abbreviations and acronyms used in the handbook, including DHSC (digital health supply chain), HSCIS, DIIG, eRIS, ERP, GFPVAN, GHSC-PSM, NPC, NSCA, OpenHIE, SCISMM, SCSA, SMART, TOGAF, TSS, TWG and WMS.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "chain information",
          "heading": false
        },
        {
          "term": "information system",
          "heading": false
        },
        {
          "term": "digital health",
          "heading": false
        },
        {
          "term": "working group",
          "heading": false
        },
        {
          "term": "request",
          "heading": false
        },
        {
          "term": "open",
          "heading": false
        },
        {
          "term": "architecture",
          "heading": false
        }
      ],
      "extract": "DH&I WG Digital Health and Interoperability Working Group DHSC digital health supply chain DIIG Digital Implementation Investment Guide eRIS Electronic Regulatory Information System ERP enterprise resource planning FTE full-time equivalent GFPVAN Global Family Planning Visibility and Analytics Network GHSC-PSM Global Health Supply Chain Program–Procurement and Supply Management HSCIS health supply chain information",
      "extractCut": true
    },
    {
      "id": "sec-002-glossary",
      "number": null,
      "title": "Glossary",
      "level": 1,
      "pageStart": 8,
      "pageEnd": 11,
      "labelStart": "vi",
      "labelEnd": "1",
      "words": 906,
      "summary": {
        "text": "Glossary defining terms used in the handbook, such as deployment, digital health, digital health supply chain intervention, digital transformation, digitalization, digitization, enterprise architecture, functional and nonfunctional requirements, health supply chain information system, interoperability, open-source software, open standards, order management, registry, SMART Guidelines, systems architecture, total cost of ownership, traceability, use case and warehouse management system.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "warehouse management",
          "heading": false
        },
        {
          "term": "requisition orders",
          "heading": false
        },
        {
          "term": "digital transformation",
          "heading": false
        },
        {
          "term": "open-source software",
          "heading": false
        },
        {
          "term": "digital system",
          "heading": false
        },
        {
          "term": "business processes",
          "heading": false
        },
        {
          "term": "digital technologies",
          "heading": false
        },
        {
          "term": "digital health",
          "heading": false
        }
      ],
      "extract": "deployment Making a software system available for use beyond testing purposes. digital health The systematic application of information and communications technologies, computer science and data to support informed decision-making by individuals, the health workforce and health systems, to strengthen resilience to disease and improve health and wellness (1, 2). digital health supply chain intervention An",
      "extractCut": true
    },
    {
      "id": "sec-003-introduction",
      "number": null,
      "title": "Introduction",
      "level": 1,
      "pageStart": 11,
      "pageEnd": 19,
      "labelStart": "1",
      "labelEnd": "9",
      "words": 3151,
      "summary": {
        "text": "Introduction describing public health supply chain partners, processes and information flows, the challenges of manual and siloed systems, and the meaning of a digital health supply chain (DHSC); it sets out what the handbook covers, its stepwise four-chapter approach, its alignment with the DIIG and the five SMART Guidelines knowledge layers, how it was developed through consultations in Ethiopia, Malawi and Rwanda and a DH&I WG small working group, and its target audiences (Table 1).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "dhsc implementations",
          "heading": false
        },
        {
          "term": "dhsc architecture",
          "heading": false
        },
        {
          "term": "implementing dhsc",
          "heading": false
        },
        {
          "term": "dhsc strategy",
          "heading": false
        },
        {
          "term": "chain processes",
          "heading": false
        },
        {
          "term": "chain operational",
          "heading": false
        },
        {
          "term": "digital transformation",
          "heading": false
        },
        {
          "term": "chain digitalization",
          "heading": false
        }
      ],
      "extract": "for delivery to individuals, are integral to the public health care system. Supply chain processes such as forecasting and planning, sourcing, procurement, order management, warehouse management and dispensing must operate in harmony to facilitate the flow of health products from manufacturers to the individuals who need them. Because supply chain processes overlap with health processes that take place at the",
      "extractCut": true
    },
    {
      "id": "sec-004-1-defining-a-holistic-dhsc-strategy",
      "number": "1",
      "title": "Defining a holistic DHSC strategy",
      "level": 1,
      "pageStart": 19,
      "pageEnd": 20,
      "labelStart": "9",
      "labelEnd": "10",
      "words": 216,
      "summary": {
        "text": "Chapter 1 opening on defining a holistic DHSC strategy, listing guiding principles informed by the Principles for Digital Development (national priority alignment, user-centred approach, interoperability, stakeholder engagement, reuse, scalability and sustainability), the expected outputs (vision, strategic goals, objectives and roadmap), and the need to align the DHSC strategy with national IT, health, medicines, supply chain and digital health strategies.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "dhsc strategy",
          "heading": true
        },
        {
          "term": "defining holistic",
          "heading": true
        },
        {
          "term": "dhsc strategic",
          "heading": false
        },
        {
          "term": "dhsc vision",
          "heading": false
        },
        {
          "term": "strategic roadmap",
          "heading": false
        },
        {
          "term": "strategic goals",
          "heading": false
        },
        {
          "term": "health strategy",
          "heading": false
        },
        {
          "term": "step",
          "heading": false
        }
      ],
      "extract": "DHSC strategy 2. Defining the DHSC architecture Chapter Defining a holistic DHSC strategy 3. Planning for scalable implementation and sustainable operations 4. Using the DHSC to implement traceability Identify and engage stakeholders Analyse the current state of HSCISs Define the vision and strategic goals and objectives Define a strategic roadmap and performance indicators 2 Step Step Step Step 3 4 1 The following",
      "extractCut": true
    },
    {
      "id": "sec-005-why-is-a-strategy-necessary",
      "number": null,
      "title": "Why is a strategy necessary?",
      "level": 2,
      "pageStart": 20,
      "pageEnd": 22,
      "labelStart": "10",
      "labelEnd": "12",
      "words": 761,
      "summary": {
        "text": "Chapter 1 section on why a DHSC strategy is necessary, describing the national strategies it should align with (Fig. 8), the risks of forgoing a guiding vision and strategy, such as fragmented and noninteroperable systems, inconsistent product nomenclature (Fig. 9), nonscalable systems and duplicative implementations, and introducing the four steps for developing the strategy.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "dhsc vision",
          "heading": false
        },
        {
          "term": "chain strategy",
          "heading": false
        },
        {
          "term": "chain systems",
          "heading": false
        },
        {
          "term": "product code",
          "heading": false
        },
        {
          "term": "product nomenclature",
          "heading": false
        },
        {
          "term": "central warehouse",
          "heading": false
        },
        {
          "term": "health product",
          "heading": false
        },
        {
          "term": "digital transformation",
          "heading": false
        }
      ],
      "extract": "A holistic DHSC strategy is essential to achieving comprehensive digital transformation of the health supply chain. It can offer a clear vision and direction and ensure alignment across all national digital transformation initiatives (Fig. 8) (21). Such initiatives may include the following: →national health strategy, which establishes a vision and priorities to address the most pressing health care challenges and",
      "extractCut": true
    },
    {
      "id": "sec-006-step-1-identify-and-engage-all-relevant-stakehol",
      "number": null,
      "title": "Step 1. Identify and engage all relevant stakeholders",
      "level": 2,
      "pageStart": 22,
      "pageEnd": 23,
      "labelStart": "12",
      "labelEnd": "13",
      "words": 427,
      "summary": {
        "text": "Chapter 1 Step 1 covering identifying and engaging all relevant stakeholders: inputs, tasks (identifying focal points and staff, defining a stakeholder matrix, establishing a technical working group and steering committee) and outputs, best practices such as securing senior MOH champions, and mitigations for weak engagement, unclear decision-making and excluded stakeholders, including the Annex 2 steering committee structure.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "relevant stakeholders",
          "heading": true
        },
        {
          "term": "steering committee",
          "heading": false
        },
        {
          "term": "dhsc implementation",
          "heading": false
        },
        {
          "term": "twg",
          "heading": false
        },
        {
          "term": "stakeholder matrix",
          "heading": false
        },
        {
          "term": "stakeholder organizations",
          "heading": false
        },
        {
          "term": "regulatory authority",
          "heading": false
        },
        {
          "term": "moh",
          "heading": false
        }
      ],
      "extract": "1 Step Identifying and engaging all relevant stakeholders involves recognizing everyone who has an interest or role in the DHSC implementation and actively involving them in the process. This ensures that diverse perspectives are considered, fosters collaboration and gains support for successful DHSC outcomes. INPUTS TASKS OUTPUTS » National health strategy 1. Identify focal points from all stakeholder organizations",
      "extractCut": true
    },
    {
      "id": "sec-007-step-2-analyse-the-current-state-of-hsciss",
      "number": null,
      "title": "Step 2. Analyse the current state of HSCISs",
      "level": 2,
      "pageStart": 23,
      "pageEnd": 24,
      "labelStart": "13",
      "labelEnd": "14",
      "words": 410,
      "summary": {
        "text": "Chapter 1 Step 2 covering analysis of the current state of health supply chain information systems to identify and prioritize digital transformation challenges, with inputs, tasks and outputs, a best practice on comprehensive assessment, mitigations for misaligned technical and political priorities and missing assessment inputs, and resources including the NSCA Toolkit and the Annex 3 and Annex 4 templates.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "chain assessments",
          "heading": false
        },
        {
          "term": "chain challenges",
          "heading": false
        },
        {
          "term": "political priorities",
          "heading": false
        },
        {
          "term": "chain strategy",
          "heading": false
        },
        {
          "term": "transformation priorities",
          "heading": false
        },
        {
          "term": "nsca toolkit",
          "heading": false
        },
        {
          "term": "political leaders",
          "heading": false
        },
        {
          "term": "technical priorities",
          "heading": false
        }
      ],
      "extract": "2 Step BEST PRACTICE Ð To ensure a comprehensive assessment of the current health supply chain, consider all factors that affect the health supply chain, such as stakeholders, human resource capacity, infrastructure, political priorities, technology maturity and maturity of processes (including regulatory and insurance). Potential risks Mitigation strategies Misalignment of technical and political priorities »",
      "extractCut": true
    },
    {
      "id": "sec-008-step-3-define-the-dhsc-vision-and-strategic-goal",
      "number": null,
      "title": "Step 3. Define the DHSC vision and strategic goals and objectives",
      "level": 2,
      "pageStart": 24,
      "pageEnd": 25,
      "labelStart": "14",
      "labelEnd": "15",
      "words": 332,
      "summary": {
        "text": "Chapter 1 Step 3 covering definition of the DHSC vision, strategic goals and specific, measurable strategic objectives, with inputs from national strategies, tasks from identifying solutions to defining an overarching vision over perhaps five years, best practices such as visioning workshops using human-centred design, and mitigations for decision delays caused by dependence on senior leaders.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "dhsc strategic",
          "heading": true
        },
        {
          "term": "dhsc vision",
          "heading": true
        },
        {
          "term": "strategic goals",
          "heading": true
        },
        {
          "term": "strategic objectives",
          "heading": true
        },
        {
          "term": "define",
          "heading": true
        },
        {
          "term": "reasonable timeframe",
          "heading": false
        },
        {
          "term": "strategy national",
          "heading": false
        },
        {
          "term": "implementation activities",
          "heading": false
        }
      ],
      "extract": "3 Step The DHSC vision provides a guiding beacon by summarizing the ideal future state of health supply chain digitalization and how to achieve it. Strategic goals guide the country’s actions and decisions to achieve the vision. They translate to strategic objectives that are specific, measurable, achievable, relevant and time-bound. The goals should link to the DHSC implementation activities. INPUTS TASKS OUTPUTS »",
      "extractCut": true
    },
    {
      "id": "sec-009-step-4-define-a-strategic-roadmap-and-performanc",
      "number": null,
      "title": "Step 4. Define a strategic roadmap and performance indicators",
      "level": 2,
      "pageStart": 25,
      "pageEnd": 27,
      "labelStart": "15",
      "labelEnd": "17",
      "words": 445,
      "summary": {
        "text": "Chapter 1 Step 4 covering definition of a strategic roadmap and performance indicators, a best practice of capturing baseline performance, mitigations for lack of dedicated staff, funding gaps and misaligned funding timelines, and the Chapter 1 progress check with an example vision, three strategic goals, objectives such as automating 80% of central warehouse operations, and a four-year roadmap (Fig. 10).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "strategic roadmap",
          "heading": true
        },
        {
          "term": "dhsc strategic",
          "heading": false
        },
        {
          "term": "performance indicators",
          "heading": true
        },
        {
          "term": "goals dhsc",
          "heading": false
        },
        {
          "term": "strategic objectives",
          "heading": false
        },
        {
          "term": "batch traceability",
          "heading": false
        },
        {
          "term": "central warehouse",
          "heading": false
        },
        {
          "term": "define",
          "heading": true
        }
      ],
      "extract": "4 Step A strategic roadmap for DHSC sets out timelines and milestones for achieving goals related to digitalizing the health supply chain. It serves as a guiding framework for the country, helping it stay focused on strategic objectives, allocate resources efficiently and track progress effectively. INPUTS TASKS OUTPUTS » DHSC strategic goals » DHSC strategic objectives » Timelines of other 1. Define a strategic",
      "extractCut": true
    },
    {
      "id": "sec-010-2-defining-the-dhsc-architecture",
      "number": "2",
      "title": "Defining the DHSC architecture",
      "level": 1,
      "pageStart": 27,
      "pageEnd": 28,
      "labelStart": "17",
      "labelEnd": "18",
      "words": 334,
      "summary": {
        "text": "Chapter 2 opening on defining the DHSC architecture, listing guiding principles informed by the Principles for Digital Development (stakeholder engagement, alignment with digital health and IT architectures, interoperability, reuse, scalability, inclusive approaches and open standards), the chapter's four outputs, and the role of the application architecture as a blueprint for the core DHSC systems.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "dhsc architecture",
          "heading": true
        },
        {
          "term": "health architecture",
          "heading": false
        },
        {
          "term": "chain functions",
          "heading": false
        },
        {
          "term": "defining",
          "heading": true
        },
        {
          "term": "strategic goals",
          "heading": false
        },
        {
          "term": "digital health",
          "heading": false
        },
        {
          "term": "implementation activities",
          "heading": false
        },
        {
          "term": "hsciss",
          "heading": false
        }
      ],
      "extract": "architecture Defining the DHSC architecture 3. Planning for scalable implementation and sustainable operations 4. Using the DHSC to implement traceability Assess the current state of HSCISs Define a target architecture Identify implementation activities and map them to strategic goals 2 1 Step Step Step 3 Chapter2 The following principles, informed by the Principles for Digital Development (Annex 1), can guide the",
      "extractCut": true
    },
    {
      "id": "sec-011-is-a-dhsc-architecture-necessary",
      "number": null,
      "title": "Is a DHSC architecture necessary?",
      "level": 2,
      "pageStart": 28,
      "pageEnd": 28,
      "labelStart": "18",
      "labelEnd": "18",
      "words": 310,
      "summary": {
        "text": "Chapter 2 section on whether a DHSC architecture is necessary, describing the health supply chain business processes it must support, the national- and subnational-level capabilities the architecture defines, and how it enables end-to-end visibility of the supply chain and the ability to track, trace and verify health products.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "dhsc architecture",
          "heading": true
        },
        {
          "term": "chain leaders",
          "heading": false
        },
        {
          "term": "chain functions",
          "heading": false
        },
        {
          "term": "warehouse management",
          "heading": false
        },
        {
          "term": "health products",
          "heading": false
        },
        {
          "term": "processes ensure",
          "heading": false
        },
        {
          "term": "quality assured",
          "heading": false
        },
        {
          "term": "capabilities",
          "heading": false
        }
      ],
      "extract": "The health supply chain comprises several business processes that ensure the availability of health products to individuals. Forecasting and supply planning processes ensure adequate supply to meet demand. Procurement and distribution processes ensure that medicines and health products are sourced and delivered to the right locations and are available to individuals when needed. Warehouse management processes",
      "extractCut": true
    },
    {
      "id": "sec-012-what-are-the-risks-of-forgoing-a-dhsc-architectu",
      "number": null,
      "title": "What are the risks of forgoing a DHSC architecture?",
      "level": 2,
      "pageStart": 28,
      "pageEnd": 30,
      "labelStart": "18",
      "labelEnd": "20",
      "words": 280,
      "summary": {
        "text": "Chapter 2 section on the risks of forgoing a DHSC architecture, including siloed and duplicative systems, noncompliance with global and open standards, laborious manual data aggregation and limited traceability, followed by the three steps for defining the architecture and a figure on end-to-end visibility and track and trace across global and national levels (Fig. 11).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "dhsc architecture",
          "heading": true
        },
        {
          "term": "end-to-end visibility",
          "heading": false
        },
        {
          "term": "overarching dhsc",
          "heading": false
        },
        {
          "term": "central warehouse",
          "heading": false
        },
        {
          "term": "global level",
          "heading": false
        },
        {
          "term": "trace",
          "heading": false
        },
        {
          "term": "forecasting",
          "heading": false
        },
        {
          "term": "lack",
          "heading": false
        }
      ],
      "extract": "The lack of an overarching DHSC architecture leads to risks such as those listed below: →siloed and duplicative systems that lack the ability to adapt and scale, requiring more effort and money to maintain and sustain; →lack of compliance with global and open standards, resulting in a lack of interoperability among processes, systems and data, which in turn, affects the timely availability of aggregated data for",
      "extractCut": true
    },
    {
      "id": "sec-013-step-1-assess-the-current-state-of-hsciss",
      "number": null,
      "title": "Step 1. Assess the current state of HSCISs",
      "level": 2,
      "pageStart": 30,
      "pageEnd": 32,
      "labelStart": "20",
      "labelEnd": "22",
      "words": 628,
      "summary": {
        "text": "Chapter 2 Step 1 covering assessment of the current state of HSCISs, with inputs, tasks (listing existing systems, conducting and analysing a SCISMM assessment) and outputs, mitigations for lack of funding, overlooked master data and low user adoption, and a description of the five SCISMM maturity levels from reporting-based (manual) to digital ecosystem (collaborated) (Fig. 12).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "hsciss",
          "heading": true
        },
        {
          "term": "scismm maturity",
          "heading": false
        },
        {
          "term": "current state",
          "heading": true
        },
        {
          "term": "scismm assessment",
          "heading": false
        },
        {
          "term": "conduct scismm",
          "heading": false
        },
        {
          "term": "chain functions",
          "heading": false
        },
        {
          "term": "chain systems",
          "heading": false
        },
        {
          "term": "hscis gaps",
          "heading": false
        }
      ],
      "extract": "1 Step Assessing the current state of HSCISs involves a thorough evaluation of their capabilities, utilization, technical challenges and overall system maturity. This step helps identify strengths, gaps, inefficiencies and areas for improvement in existing systems that can be duly considered while defining the architecture. INPUTS TASKS OUTPUTS » NSCA outcomes (if available) » SCISMM assessment outcomes (if",
      "extractCut": true
    },
    {
      "id": "sec-014-dhsc-architecture-framework",
      "number": null,
      "title": "DHSC architecture framework",
      "level": 2,
      "pageStart": 32,
      "pageEnd": 32,
      "labelStart": "22",
      "labelEnd": "22",
      "words": 63,
      "summary": {
        "text": "Brief Chapter 2 introduction to the DHSC architecture framework, relating DHSC components to the business domain services of the DIIG digital health enterprise architecture (Fig. 13) and noting that the framework (Fig. 14) covers foundational services, supply chain functional services, analytics, interoperability and traceability, based on TOGAF and OpenHIE principles.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "dhsc",
          "heading": true
        },
        {
          "term": "architecture",
          "heading": true
        },
        {
          "term": "framework",
          "heading": true
        }
      ],
      "extract": "The DIIG outlines the components of a digital health enterprise architecture (Fig. 13). DHSC architectural components relate to the business domain services within this architecture. Fig. 14 shows a DHSC architecture framework with components that support services such as foundational services, supply chain functional services, analytics, interoperability and traceability. This framework is based on the guiding",
      "extractCut": true
    },
    {
      "id": "sec-015-step-2-define-a-target-dhsc-architecture",
      "number": null,
      "title": "Step 2. Define a target DHSC architecture",
      "level": 2,
      "pageStart": 32,
      "pageEnd": 35,
      "labelStart": "22",
      "labelEnd": "25",
      "words": 1468,
      "summary": {
        "text": "Chapter 2 Step 2 covering definition of a target DHSC architecture, with inputs, tasks, outputs and mitigations, a best practice on capturing actual consumption at the last mile, the DIIG enterprise architecture (Fig. 13) and the DHSC architecture framework (Fig. 14), describing foundational components, the interoperability layer, HSCISs, data services, external systems and digital ecosystems such as regulatory, finance and insurance systems.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "dhsc architecture",
          "heading": true
        },
        {
          "term": "dhsc enterprise",
          "heading": false
        },
        {
          "term": "chain data",
          "heading": false
        },
        {
          "term": "interoperability layer",
          "heading": false
        },
        {
          "term": "software capabilities",
          "heading": false
        },
        {
          "term": "digital ecosystems",
          "heading": false
        },
        {
          "term": "chain processes",
          "heading": false
        },
        {
          "term": "product master",
          "heading": false
        }
      ],
      "extract": "2 Step This step involves defining a target DHSC architecture to ensure that all of the HSCISs are optimally structured and aligned with strategic goals. INPUTS TASKS OUTPUTS » Assessment of the supply chain to identify opportunities for digital transformation » List of existing HSCISs » SCISMM assessment report » HSCIS gaps that need to be addressed to achieve the DHSC strategic goals 1. Draw the current-state",
      "extractCut": true
    },
    {
      "id": "sec-016-illustrative-architectural-approaches-and-govern",
      "number": null,
      "title": "Illustrative architectural approaches and governance options",
      "level": 2,
      "pageStart": 35,
      "pageEnd": 42,
      "labelStart": "25",
      "labelEnd": "32",
      "words": 1345,
      "summary": {
        "text": "Chapter 2 section illustrating architectural approaches: maturity-based architectures for moving from SCISMM Level 3 to Level 4 and from Level 4 to Level 5, and supply-chain-design architectures with centralized and decentralized (options A and B) governance (Figs. 15–19), plus the benefits of cross-enterprise analytics services for end-to-end visibility (Fig. 20).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "supplier registry",
          "heading": false
        },
        {
          "term": "cold chain",
          "heading": false
        },
        {
          "term": "chain management",
          "heading": false
        },
        {
          "term": "warehouse management",
          "heading": false
        },
        {
          "term": "chain enterprise",
          "heading": false
        },
        {
          "term": "chain reports",
          "heading": false
        },
        {
          "term": "chain design",
          "heading": false
        },
        {
          "term": "central warehouse",
          "heading": false
        }
      ],
      "extract": "Countries often have a mixture of needs and capabilities that should be reflected in their DHSC architecture. They can adopt an architecture framework using an approach that aligns with their supply chain design and level of digital maturity. This section provides examples of architectures that are based on digital maturity and examples based on supply chain design (with different governance options). In practice,",
      "extractCut": true
    },
    {
      "id": "sec-017-step-3-identify-implementation-activities-and-ma",
      "number": null,
      "title": "Step 3. Identify implementation activities and map them to strategic goals",
      "level": 2,
      "pageStart": 42,
      "pageEnd": 44,
      "labelStart": "32",
      "labelEnd": "34",
      "words": 469,
      "summary": {
        "text": "Chapter 2 Step 3 covering translation of architectural interventions into prioritized implementation activities mapped to strategic goals and a high-level roadmap, with mitigation for activities misaligned with strategic goals, and the Chapter 2 progress check showing example outputs such as a target architecture, an implementation roadmap and DHSC outcomes like WMS rollout across 40% of facilities (Fig. 21).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "strategic goals",
          "heading": true
        },
        {
          "term": "implementation activities",
          "heading": true
        },
        {
          "term": "dhsc strategic",
          "heading": false
        },
        {
          "term": "dhsc architecture",
          "heading": false
        },
        {
          "term": "future-state dhsc",
          "heading": false
        },
        {
          "term": "interop mediator",
          "heading": false
        },
        {
          "term": "dhsc interventions",
          "heading": false
        },
        {
          "term": "hsciss future-state",
          "heading": false
        }
      ],
      "extract": "3 Step This step focuses on translating the identified DHSC architectural interventions into implementation activities. The activities will be mapped out on a timeline to prepare a roadmap for overall implementation. Potential risks Mitigation strategies Activities are not aligned with DHSC strategic goals Identify and plan implementation activities after the vision, strategy and architecture have been developed and",
      "extractCut": true
    },
    {
      "id": "sec-018-3-planning-for-scalable-implementation-and-susta",
      "number": "3",
      "title": "Planning for scalable implementation and sustainable operations",
      "level": 1,
      "pageStart": 44,
      "pageEnd": 47,
      "labelStart": "34",
      "labelEnd": "37",
      "words": 1150,
      "summary": {
        "text": "Chapter 3 opening on planning for scalable implementation and sustainable operations, with guiding principles, the expected outputs, the seven building blocks of the WHO-ITU National eHealth Strategy Toolkit (Fig. 22), a definition of governance, and Table 2 of illustrative implementation considerations covering leadership and governance, strategy and investment, legislation, workforce, standards and interoperability, services and applications, and infrastructure.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "dhsc applications",
          "heading": false
        },
        {
          "term": "sustainable operations",
          "heading": true
        },
        {
          "term": "dhsc architecture",
          "heading": false
        },
        {
          "term": "dhsc strategy",
          "heading": false
        },
        {
          "term": "scalable implementation",
          "heading": true
        },
        {
          "term": "dhsc vision",
          "heading": false
        },
        {
          "term": "interoperability mediator",
          "heading": false
        },
        {
          "term": "who-itu national",
          "heading": false
        }
      ],
      "extract": "implementation and sustainable operations Plan the implementation of each intervention Develop an operational plan for each intervention Develop a budget for each intervention Implement each intervention 2 1 Step Step Step Step 3 4 The following principles, informed by the Principles for Digital Development (Annex 1), can guide the implementation of the DHSC interventions. →Plan for sustainability from the start.",
      "extractCut": true
    },
    {
      "id": "sec-019-step-1-plan-the-implementation-of-each-dhsc-inte",
      "number": null,
      "title": "Step 1. Plan the implementation of each DHSC intervention",
      "level": 2,
      "pageStart": 47,
      "pageEnd": 48,
      "labelStart": "37",
      "labelEnd": "38",
      "words": 250,
      "summary": {
        "text": "Chapter 3 Step 1 covering planning the implementation of each DHSC intervention, with inputs, tasks and outputs, and the contents of the project charter, the project management plan (including a RACI stakeholder matrix, risk register and change management plan) and the project performance monitoring and analysis framework, referencing the Annex 6 risk register template.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "project charter",
          "heading": false
        },
        {
          "term": "dhsc",
          "heading": true
        },
        {
          "term": "project management",
          "heading": false
        },
        {
          "term": "plan",
          "heading": true
        },
        {
          "term": "project performance",
          "heading": false
        },
        {
          "term": "steering committee",
          "heading": false
        },
        {
          "term": "step",
          "heading": true
        },
        {
          "term": "schedule",
          "heading": false
        }
      ],
      "extract": "1 Step This step focuses on developing a comprehensive plan, which is essential for guiding various DHSC implementation activities. INPUTS TASKS OUTPUTS » Prioritized DHSC 1. Develop a project charter. interventions » List of DHSC 2. Develop a project management plan. 3. Establish a project governance and reporting mechanism through the steering committee and/or TWG. implementation activities 4. Define the project",
      "extractCut": true
    },
    {
      "id": "sec-020-step-2-develop-an-operational-plan-for-each-dhsc",
      "number": null,
      "title": "Step 2. Develop an operational plan for each DHSC intervention",
      "level": 2,
      "pageStart": 48,
      "pageEnd": 49,
      "labelStart": "38",
      "labelEnd": "39",
      "words": 282,
      "summary": {
        "text": "Chapter 3 Step 2 covering development of an operational plan for each DHSC intervention, with tasks such as identifying system owners and operational resources, the contents of the operations and sustainability plan (recurring costs, data backups, financial strategy) and the operational performance monitoring framework, and introducing the total cost of ownership cost components (Fig. 23).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "dhsc",
          "heading": true
        },
        {
          "term": "dhsc stakeholder",
          "heading": false
        },
        {
          "term": "operational",
          "heading": true
        },
        {
          "term": "stakeholder matrix",
          "heading": false
        },
        {
          "term": "operational costs",
          "heading": false
        },
        {
          "term": "backup power",
          "heading": false
        },
        {
          "term": "operational performance",
          "heading": false
        },
        {
          "term": "sustainability plan",
          "heading": false
        }
      ],
      "extract": "2 Step The operational plan should determine the necessary resources and the effort needed to effectively maintain and run the DHSC systems. INPUTS TASKS OUTPUTS » List of DHSC 1. Update the stakeholder matrix, if required, to establish the system owner/custodian and system users. implementation activities » DHSC stakeholder matrix 2. Identify required operational resources (such as maintenance personnel, hardware,",
      "extractCut": true
    },
    {
      "id": "sec-021-step-3-develop-a-budget-for-each-dhsc-interventi",
      "number": null,
      "title": "Step 3. Develop a budget for each DHSC intervention",
      "level": 2,
      "pageStart": 49,
      "pageEnd": 51,
      "labelStart": "39",
      "labelEnd": "41",
      "words": 645,
      "summary": {
        "text": "Chapter 3 Step 3 covering development of a budget for each DHSC intervention based on total cost of ownership across implementing, scaling and operating (Fig. 23), with tasks such as determining operational costs over a typical five to 10 years and building a budget matrix, and Table 3 listing illustrative cost drivers for management, governance, sourcing, software, hardware, integration, training, maintenance and monitoring.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "dhsc intervention",
          "heading": true
        },
        {
          "term": "cost drivers",
          "heading": false
        },
        {
          "term": "dhsc implementation",
          "heading": false
        },
        {
          "term": "end users",
          "heading": false
        },
        {
          "term": "budget matrix",
          "heading": false
        },
        {
          "term": "ongoing training",
          "heading": false
        },
        {
          "term": "illustrative cost",
          "heading": false
        },
        {
          "term": "testing users",
          "heading": false
        }
      ],
      "extract": "3 Step This step helps prepare the budget based on costs to implement as well as costs to scale and operate DHSC systems. ONGOING Management Governance Overhead IMPLEMENT SCALE OPERATE Sourcing (RFP, RFI, RFQ) Hardware and infrastructure Software Design and development Integration and interoperability Testing and training Deployment Expansion of deployment Training Hardware and infrastructure Software",
      "extractCut": true
    },
    {
      "id": "sec-022-step-4-implement-each-dhsc-intervention",
      "number": null,
      "title": "Step 4. Implement each DHSC intervention",
      "level": 2,
      "pageStart": 51,
      "pageEnd": 53,
      "labelStart": "41",
      "labelEnd": "43",
      "words": 754,
      "summary": {
        "text": "Chapter 3 Step 4 covering implementation of each DHSC intervention, with tasks from defining requirements and sourcing vendors through RFPs and RFQs to design, development, integration, testing, training and rollout, mitigations for risks such as hidden costs, capacity constraints, poor training, unreliable infrastructure, political budget dependence and budget rigidity, and the Chapter 3 progress check of outputs.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "dhsc intervention",
          "heading": true
        },
        {
          "term": "dhsc implementation",
          "heading": false
        },
        {
          "term": "dhsc application",
          "heading": false
        },
        {
          "term": "nonfunctional requirements",
          "heading": false
        },
        {
          "term": "chain facilities",
          "heading": false
        },
        {
          "term": "user acceptance",
          "heading": false
        },
        {
          "term": "integration specifications",
          "heading": false
        },
        {
          "term": "identify funding",
          "heading": false
        }
      ],
      "extract": "4 Step This step encompasses several tasks needed to implement the identified DHSC interventions, including vendor selection, system design, development, validation and training. INPUTS TASKS OUTPUTS » Prioritized DHSC interventions » List of DHSC implementation activities 1. Define functional and nonfunctional requirements for the DHSC intervention being implemented. 2. Identify the implementation partner/ vendor",
      "extractCut": true
    },
    {
      "id": "sec-023-4-using-the-dhsc-to-implement-traceability",
      "number": "4",
      "title": "Using the DHSC to implement traceability",
      "level": 1,
      "pageStart": 53,
      "pageEnd": 54,
      "labelStart": "43",
      "labelEnd": "44",
      "words": 93,
      "summary": {
        "text": "Chapter 4 opening on using the DHSC to implement traceability, explaining that the ability to track, trace and verify health products helps mitigate the risk of falsified medicines and ensure patient safety, and that the chapter focuses mainly on deploying technologies that use the DHSC architecture framework to support traceability.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "dhsc",
          "heading": true
        },
        {
          "term": "traceability",
          "heading": true
        },
        {
          "term": "dhsc architecture",
          "heading": false
        }
      ],
      "extract": "Using the DHSC to implement traceability One key benefit of the DHSC architecture is the ability to track, trace and verify health products. Traceability of health products is important to mitigate the risk of falsified medicines and ensure patient safety and quality health care. This chapter explores the use of the DHSC architecture framework to implement and institutionalize traceability, which requires efforts",
      "extractCut": true
    },
    {
      "id": "sec-024-what-is-traceability",
      "number": null,
      "title": "What is traceability?",
      "level": 2,
      "pageStart": 54,
      "pageEnd": 54,
      "labelStart": "44",
      "labelEnd": "44",
      "words": 70,
      "summary": {
        "text": "Chapter 4 section defining traceability, citing GS1's description as the ability to see the movement of health products across the supply chain, and explaining it as tracing the path of products from manufacturer to individuals, identifying ownership changes and showing products' whereabouts.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "traceability",
          "heading": true
        },
        {
          "term": "whereabouts",
          "heading": false
        },
        {
          "term": "chain",
          "heading": false
        }
      ],
      "extract": "The global standards organization GS1 describes traceability as the ability “to see the movement of health products across the supply chain” (25). Traceability means being able to trace the path of health care products from the manufacturer to individuals, identifying ownership changes at different points along the supply chain. Traceability also aids in the whereabouts of products at any given moment, including",
      "extractCut": true
    },
    {
      "id": "sec-025-why-is-traceability-important",
      "number": null,
      "title": "Why is traceability important?",
      "level": 2,
      "pageStart": 54,
      "pageEnd": 54,
      "labelStart": "44",
      "labelEnd": "44",
      "words": 200,
      "summary": {
        "text": "Chapter 4 section on why traceability is important, explaining how visibility of ownership changes helps identify falsified products, protect patient safety and manage product recalls, and noting that traceability systems are mostly based on regulatory requirements, require global harmonization and rely on global standards for interoperability.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "traceability",
          "heading": true
        },
        {
          "term": "traceability systems",
          "heading": false
        },
        {
          "term": "health products",
          "heading": false
        },
        {
          "term": "visibility",
          "heading": false
        },
        {
          "term": "health care",
          "heading": false
        },
        {
          "term": "chain",
          "heading": false
        },
        {
          "term": "global",
          "heading": false
        }
      ],
      "extract": "Tracing and tracking enhance the efficiency and integrity of the health supply chain. By providing global visibility into every change of product ownership along the supply chain, traceability helps identify falsified health products and prevents their dispensation to individuals (among other benefits, which include efficiencies in inventory management and prevention of medicine shortages), ultimately helping to",
      "extractCut": true
    },
    {
      "id": "sec-026-traceability-models",
      "number": null,
      "title": "Traceability models",
      "level": 2,
      "pageStart": 54,
      "pageEnd": 57,
      "labelStart": "44",
      "labelEnd": "47",
      "words": 958,
      "summary": {
        "text": "Chapter 4 section on traceability models, describing centralized, semi-centralized and distributed models, the essential technology components for a centralized model (foundational components, repository, interoperability layer, HSCISs and traceability analytics), track and trace through DHSC components (Fig. 24), factors such as master data quality and manufacturer marking, and an illustrative traceability service interface (Fig. 25).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "traceability",
          "heading": true
        },
        {
          "term": "traceability data",
          "heading": false
        },
        {
          "term": "traceability model",
          "heading": false
        },
        {
          "term": "traceability service",
          "heading": false
        },
        {
          "term": "data warehouse",
          "heading": false
        },
        {
          "term": "product verification",
          "heading": false
        },
        {
          "term": "central warehouse",
          "heading": false
        },
        {
          "term": "warehouse management",
          "heading": false
        }
      ],
      "extract": "The three main models for implementing traceability are the centralized, semi-centralized and distributed models. They differ mostly in how they store the data and share them with the relevant health authority and across actors in the supply chain. The centralized model involves a single database or repository for storing all traceability data. In a semi- centralized model, the traceability data are spread across",
      "extractCut": true
    },
    {
      "id": "sec-027-5-country-examples",
      "number": "5",
      "title": "Country examples",
      "level": 1,
      "pageStart": 57,
      "pageEnd": 58,
      "labelStart": "47",
      "labelEnd": "48",
      "words": 3,
      "summary": {
        "text": "Opening of Chapter 5, the country examples chapter; its extracted text carries no narrative and only names the three countries whose DHSC initiatives are presented in the following sections: Ethiopia, Malawi and Rwanda.",
        "status": "draft"
      },
      "keywords": [],
      "extract": "Ethiopia Malawi Rwanda",
      "extractCut": false
    },
    {
      "id": "sec-028-ethiopias-dhsc-initiative",
      "number": null,
      "title": "Ethiopia’s DHSC initiative",
      "level": 2,
      "pageStart": 58,
      "pageEnd": 60,
      "labelStart": "48",
      "labelEnd": "50",
      "words": 624,
      "summary": {
        "text": "Chapter 5 country example of Ethiopia's DHSC initiative, covering the 2016 Information Revolution Roadmap and the MOH eHealth Architecture, strategy and blueprint, the development process with TWGs and a change management team, current integrated systems as of March 2024 (Fig. 26), a future ERP and master data management tool (Fig. 27), key insights and the public health supply chain structure.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "ethiopia",
          "heading": true
        },
        {
          "term": "chain systems",
          "heading": false
        },
        {
          "term": "warehouse management",
          "heading": false
        },
        {
          "term": "chain information",
          "heading": false
        },
        {
          "term": "digital ecosystems",
          "heading": false
        },
        {
          "term": "erp",
          "heading": false
        },
        {
          "term": "product catalog",
          "heading": false
        },
        {
          "term": "product directory",
          "heading": false
        }
      ],
      "extract": "Status The Government of Ethiopia issued its Information Revolution Roadmap in April 2016, which recognized digital health projects as major transformational tools. Under MOH leadership, it subsequently issued an eHealth Architecture (January 2018), strategy (2020) and blueprint (August 2021). The eHealth Architecture created a foundational framework for health information systems to interact and for proper",
      "extractCut": true
    },
    {
      "id": "sec-029-malawis-dhsc-initiative",
      "number": null,
      "title": "Malawi’s DHSC initiative",
      "level": 2,
      "pageStart": 60,
      "pageEnd": 63,
      "labelStart": "50",
      "labelEnd": "53",
      "words": 716,
      "summary": {
        "text": "Chapter 5 country example of Malawi's DHSC initiative, describing the Supply Chain Systems Architecture (SCSA) developed in 2021 under the HTSS division of the MOH with USAID GHSC-PSM support and approved in September 2022, current overlapping HSCISs as of December 2023 (Fig. 28), the future-state architecture using the National Product Catalog (Figs. 29–30), insights and the supply chain structure.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "scsa",
          "heading": false
        },
        {
          "term": "chain systems",
          "heading": false
        },
        {
          "term": "supplier registry",
          "heading": false
        },
        {
          "term": "malawi",
          "heading": true
        },
        {
          "term": "warehouse management",
          "heading": false
        },
        {
          "term": "product catalog",
          "heading": false
        },
        {
          "term": "future-state architecture",
          "heading": false
        },
        {
          "term": "chain information",
          "heading": false
        }
      ],
      "extract": "Status The country’s Supply Chain Systems Architecture (SCSA) was collaboratively developed in 2021 under the leadership of the Health Technical Support Services (HTSS) division of the MOH. It was approved by the deputy minister of health in September 2022. Process The SCSA was developed with support from the USAID GHSC-PSM and was informed by a SCISMM assessment and an October 2021 workshop that was held to help",
      "extractCut": true
    },
    {
      "id": "sec-030-rwandas-dhsc-initiative",
      "number": null,
      "title": "Rwanda’s DHSC initiative",
      "level": 2,
      "pageStart": 63,
      "pageEnd": 65,
      "labelStart": "53",
      "labelEnd": "55",
      "words": 529,
      "summary": {
        "text": "Chapter 5 country example of Rwanda's DHSC initiative, describing the Digital Supply Chain Strategy and Architecture drafted in 2022 under the MOH's Chief Digital Office with USAID GHSC-PSM support, informed by a SCISMM assessment and a February 2022 stakeholder workshop, with current and future-state systems (Figs. 31–32), insights and the public health supply chain structure.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "rwanda",
          "heading": true
        },
        {
          "term": "dsc strategy",
          "heading": false
        },
        {
          "term": "digital ecosystems",
          "heading": false
        },
        {
          "term": "chain systems",
          "heading": false
        },
        {
          "term": "warehouse management",
          "heading": false
        },
        {
          "term": "erp",
          "heading": false
        },
        {
          "term": "product catalog",
          "heading": false
        },
        {
          "term": "chain information",
          "heading": false
        }
      ],
      "extract": "Status Rwanda’s Digital Supply Chain (DSC) Strategy and Architecture was collaboratively drafted in 2022 under the leadership of the MOH’s Chief Digital Office. It is currently being aligned with and incorporated into the country’s overall digital health strategy. Process The DSC Strategy and Architecture was developed with support from USAID through its GHSC-PSM project and was informed by the results of a SCISMM",
      "extractCut": true
    },
    {
      "id": "sec-031-references",
      "number": null,
      "title": "References",
      "level": 1,
      "pageStart": 65,
      "pageEnd": 66,
      "labelStart": "55",
      "labelEnd": "56",
      "words": 435,
      "summary": {
        "text": "Reference list of 26 sources cited in the handbook, including the WHO DIIG, the SMART Guidelines, the WHO Policy Paper on Traceability of Medical Products, the Global Strategy on Digital Health 2020–2025, SCISMM, OpenHIE, TOGAF, the WHO-ITU National eHealth Strategy Toolkit, the NSCA Toolkit, the IHE Pharmacy white paper, GS1 and ICMRA guidance.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "digital transformation",
          "heading": false
        },
        {
          "term": "digital square",
          "heading": false
        },
        {
          "term": "open standards",
          "heading": false
        },
        {
          "term": "digital health",
          "heading": false
        },
        {
          "term": "website",
          "heading": false
        },
        {
          "term": "open source",
          "heading": false
        },
        {
          "term": "digital age",
          "heading": false
        },
        {
          "term": "health organization",
          "heading": false
        }
      ],
      "extract": "2 All linked references were accessed on 15 October 2024. References 1. Digital implementation investment guide (DIIG): integrating digital interventions into health programmes. Geneva: World Health Organization; 2020 (https://iris.who.int/handle/10665/334306). Licence: CC BY-NC-SA 3.0 IGO. 2. Digital Health & Interoperability Working Group [website]. Digital Square; 2024",
      "extractCut": true
    },
    {
      "id": "sec-032-annex-1-principles-for-digital-development",
      "number": "Annex 1",
      "title": "Principles for digital development",
      "level": 1,
      "pageStart": 66,
      "pageEnd": 67,
      "labelStart": "56",
      "labelEnd": "57",
      "words": 198,
      "summary": {
        "text": "Annex 1 listing the Principles for Digital Development adapted from the Digital Impact Alliance, such as understanding the existing ecosystem, sharing and reusing, designing with people and for inclusion, building for sustainability, people-first data practices, open and transparent practices, anticipating harms and using evidence.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "people-first data",
          "heading": false
        },
        {
          "term": "digital",
          "heading": true
        },
        {
          "term": "data practices",
          "heading": false
        },
        {
          "term": "starts",
          "heading": false
        },
        {
          "term": "mitigate",
          "heading": false
        },
        {
          "term": "build",
          "heading": false
        },
        {
          "term": "works",
          "heading": false
        }
      ],
      "extract": "Understand the existing ecosystem Trust starts with a thorough understanding of the dynamic cultural, social and economic context in which you are operating. Share, reuse, and improve Build on what works, improve what works, and share so that others can do the same. Design with people Good design starts and ends with people that will manage, use, and ideally benefit from a given digital initiative. Design for",
      "extractCut": true
    },
    {
      "id": "sec-033-annex-2-steering-committee-example-structure",
      "number": "Annex 2",
      "title": "Steering committee example structure",
      "level": 1,
      "pageStart": 67,
      "pageEnd": 68,
      "labelStart": "57",
      "labelEnd": "58",
      "words": 80,
      "summary": {
        "text": "Annex 2 providing an example organizational structure for a DHSC steering committee, with an executive chairperson from the MOH, a secretariat and members such as the IT authority, funders, central warehouse, regulators and the private sector, and a technical working group covering data, process, technology and risk governance topics.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "steering",
          "heading": true
        },
        {
          "term": "chairperson",
          "heading": false
        },
        {
          "term": "structure",
          "heading": true
        },
        {
          "term": "committee",
          "heading": true
        }
      ],
      "extract": "The following diagram illustrates an example organizational structure of a DHSC steering committee. Executive chairperson MOH Secretariat Information technology authority Funders Central warehouse Implementing partners Others Others (academia, etc.) Regulatory Private sector Data Process Technology Risk Data needs identification Process formulation and reviews Enterprise architecture reviews Risk management Data",
      "extractCut": true
    },
    {
      "id": "sec-034-annex-3-template-for-prioritizing-dhsc-challenge",
      "number": "Annex 3",
      "title": "Template for prioritizing DHSC challenges to address",
      "level": 1,
      "pageStart": 68,
      "pageEnd": 69,
      "labelStart": "58",
      "labelEnd": "59",
      "words": 166,
      "summary": {
        "text": "Annex 3 providing a template for prioritizing DHSC challenges, scoring bottlenecks Low (1), Medium (2) or High (3) on impact, likelihood of overcoming them and stakeholder importance, with three hypothetical examples whose summed scores give a prioritized ranking.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "prioritized ranking",
          "heading": false
        },
        {
          "term": "bottleneck",
          "heading": false
        },
        {
          "term": "medium",
          "heading": false
        },
        {
          "term": "scores",
          "heading": false
        },
        {
          "term": "forecasts",
          "heading": false
        }
      ],
      "extract": "address The following table offers some considerations for ranking supply chain challenges and bottlenecks. It can be useful in guiding discussion and reaching consensus among stakeholders. The table describes three hypothetical examples of bottlenecks, which receive scores of Low (1), Medium (2) or High (3) based on responses to three questions. Adding the scores yields the prioritized ranking. Bottleneck 1. How",
      "extractCut": true
    },
    {
      "id": "sec-035-annex-4-illustrative-template-that-maps-todays-c",
      "number": "Annex 4",
      "title": "Illustrative template that maps today’s challenges to future outcomes",
      "level": 1,
      "pageStart": 69,
      "pageEnd": 70,
      "labelStart": "59",
      "labelEnd": "60",
      "words": 187,
      "summary": {
        "text": "Annex 4 providing an illustrative template that maps today's supply chain challenges, such as unavailable consumption data, stock expiries, duplicative data entry, long procurement times, stockouts and lack of trust in medicines, to future DHSC outcomes with example figures.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "duplicative data",
          "heading": false
        },
        {
          "term": "chain systems",
          "heading": false
        },
        {
          "term": "consumption data",
          "heading": false
        },
        {
          "term": "future",
          "heading": true
        },
        {
          "term": "wastages",
          "heading": false
        },
        {
          "term": "medicines",
          "heading": false
        },
        {
          "term": "today",
          "heading": true
        }
      ],
      "extract": "challenges to future outcomes This type of template can be used to map the transition from current critical challenges faced by supply chain partners and their processes to the future vision of a DHSC. Unavailability of consumption data affects availability of medicines to patients Availability of timely consumption data increases forecasting accuracy, ensuring availability of medicines 20% Error Stock expiries and",
      "extractCut": true
    },
    {
      "id": "sec-036-annex-5-template-for-listing-health-supply-chain",
      "number": "Annex 5",
      "title": "Template for listing health supply chain information systems",
      "level": 1,
      "pageStart": 70,
      "pageEnd": 71,
      "labelStart": "60",
      "labelEnd": "61",
      "words": 83,
      "summary": {
        "text": "Annex 5 providing a template for listing health supply chain information systems by supply chain function and level, from the MOH and regulatory authority to service delivery points and individuals, with example entries such as OpenLMIS, ERP, OpenClinic and the NPC mobile app marked as in progress or deployed.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "npc mobile",
          "heading": false
        },
        {
          "term": "openlmis",
          "heading": false
        },
        {
          "term": "mobile app",
          "heading": false
        },
        {
          "term": "warehouse",
          "heading": false
        }
      ],
      "extract": "information systems The following table is a template for assessing the current landscape of HSCISs and identifying systems and gaps. MOH Regulatory authority Central warehouse Branch warehouse Service delivery point Community health worker Individuals Forecasting and planning Planning system Procurement management Supplier and contract management Order management OpenLMIS OpenLMIS OpenLMIS Warehouse management ERP",
      "extractCut": true
    },
    {
      "id": "sec-037-annex-6-risk-register-template",
      "number": "Annex 6",
      "title": "Risk register template",
      "level": 1,
      "pageStart": 71,
      "pageEnd": 72,
      "labelStart": "61",
      "labelEnd": "62",
      "words": 94,
      "summary": {
        "text": "Annex 6 providing a risk register template with columns for risk title, description, priority, impact, probability, status, mitigation steps, owner and dates, illustrated by an example risk of inadequate training and its mitigations.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "mitigation steps",
          "heading": false
        },
        {
          "term": "template",
          "heading": true
        },
        {
          "term": "training",
          "heading": false
        }
      ],
      "extract": "The following table is a template for ranking risks and identifying mitigation steps. # Risk title Description Priority Impact Prob- ability Status Mitigation steps Owner Raised Reviewed Closed 001 Inadequate training IF system training is not delivered with appropriate content for the audience, THEN the adoption and use of the system may fail. Low Major Medium Mitigate » Perform a skills assessment for each user",
      "extractCut": true
    },
    {
      "id": "sec-038-annex-7-resource-matrix-for-dhsc-implementation",
      "number": "Annex 7",
      "title": "Resource matrix for DHSC implementation",
      "level": 1,
      "pageStart": 72,
      "pageEnd": 78,
      "labelStart": "62",
      "labelEnd": "68",
      "words": 1950,
      "summary": {
        "text": "Annex 7 providing a resource matrix of technical roles for DHSC implementation, such as chief technology officer, IT manager, project manager, solution architect, business analyst, developer, integration specialist, database administrator, QA/test manager, system administrator, support engineer and superuser/trainer, with phases, position types, skill sets and responsibilities, plus People that Deliver resources.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "contracted temporary",
          "heading": false
        },
        {
          "term": "leadership skills",
          "heading": false
        },
        {
          "term": "business requirements",
          "heading": false
        },
        {
          "term": "interpersonal skills",
          "heading": false
        },
        {
          "term": "problem-solving skills",
          "heading": false
        },
        {
          "term": "software tools",
          "heading": false
        },
        {
          "term": "chain software",
          "heading": false
        },
        {
          "term": "technical teams",
          "heading": false
        }
      ],
      "extract": "The table below illustrates the technical roles needed for DHSC implementation. The following resources on human resource planning for health supply chain digital transformation can also be helpful: → People that Deliver (PtD): Building human resources for supply chain management theory of change (1) → People that Deliver: Supply chain management professionalisation framework (2) and → People that Deliver: PtD",
      "extractCut": true
    }
  ],
  "checks": {
    "tocAlignment": {
      "listed_not_found": {
        "count": 0,
        "items": []
      },
      "found_not_listed": {
        "count": 3,
        "items": [
          "1 How much impact does this bottleneck have on the process?",
          "2 What is the likelihood of overcoming this bottleneck?",
          "3 Is this important to a wide range of stakeholders? Score"
        ]
      },
      "page_mismatch": {
        "count": 0,
        "items": []
      }
    },
    "figureSequenceGaps": [],
    "pageLabelConflicts": {
      "count": 0,
      "items": []
    }
  },
  "withheld": false,
  "keywords": [
    {
      "term": "dhsc architecture",
      "heading": true
    },
    {
      "term": "dhsc systems",
      "heading": false
    },
    {
      "term": "chain architecture",
      "heading": true
    },
    {
      "term": "chain digital",
      "heading": true
    },
    {
      "term": "dhsc strategic",
      "heading": true
    },
    {
      "term": "chain management",
      "heading": true
    },
    {
      "term": "dhsc vision",
      "heading": true
    },
    {
      "term": "dhsc implementation",
      "heading": true
    },
    {
      "term": "dhsc strategy",
      "heading": true
    },
    {
      "term": "dhsc goals",
      "heading": true
    },
    {
      "term": "chain data",
      "heading": false
    },
    {
      "term": "dhsc enterprise",
      "heading": false
    }
  ],
  "pageLabels": [
    {
      "physical": 1,
      "label": "A",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 2,
      "label": "B",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 3,
      "label": "i",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 4,
      "label": "ii",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 5,
      "label": "iii",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 6,
      "label": "iv",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 7,
      "label": "v",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 8,
      "label": "vi",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 9,
      "label": "vii",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 10,
      "label": "viii",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 11,
      "label": "1",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 12,
      "label": "2",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 13,
      "label": "3",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 14,
      "label": "4",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 15,
      "label": "5",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 16,
      "label": "6",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 17,
      "label": "7",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 18,
      "label": "8",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 19,
      "label": "9",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 20,
      "label": "10",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 21,
      "label": "11",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 22,
      "label": "12",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 23,
      "label": "13",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 24,
      "label": "14",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 25,
      "label": "15",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 26,
      "label": "16",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 27,
      "label": "17",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 28,
      "label": "18",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 29,
      "label": "19",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 30,
      "label": "20",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 31,
      "label": "21",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 32,
      "label": "22",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 33,
      "label": "23",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 34,
      "label": "24",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 35,
      "label": "25",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 36,
      "label": "26",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 37,
      "label": "27",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 38,
      "label": "28",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 39,
      "label": "29",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 40,
      "label": "30",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 41,
      "label": "31",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 42,
      "label": "32",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 43,
      "label": "33",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 44,
      "label": "34",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 45,
      "label": "35",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 46,
      "label": "36",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 47,
      "label": "37",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 48,
      "label": "38",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 49,
      "label": "39",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 50,
      "label": "40",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 51,
      "label": "41",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 52,
      "label": "42",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 53,
      "label": "43",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 54,
      "label": "44",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 55,
      "label": "45",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 56,
      "label": "46",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 57,
      "label": "47",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 58,
      "label": "48",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 59,
      "label": "49",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 60,
      "label": "50",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 61,
      "label": "51",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 62,
      "label": "52",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 63,
      "label": "53",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 64,
      "label": "54",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 65,
      "label": "55",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 66,
      "label": "56",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 67,
      "label": "57",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 68,
      "label": "58",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 69,
      "label": "59",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 70,
      "label": "60",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 71,
      "label": "61",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 72,
      "label": "62",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 73,
      "label": "63",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 74,
      "label": "64",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 75,
      "label": "65",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 76,
      "label": "66",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 77,
      "label": "67",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 78,
      "label": "68",
      "source": "pdf-labels",
      "confidence": 0.7
    }
  ],
  "figures": [
    {
      "kind": "figure",
      "number": "1",
      "title": "Public health supply chain partners and processes",
      "page": 11,
      "pageLabel": "1",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "2",
      "title": "Information flow across supply chain",
      "page": 12,
      "pageLabel": "2",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "3",
      "title": "Digital health supply chain",
      "page": 13,
      "pageLabel": "3",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "4",
      "title": "The stepwise approach used in this handbook",
      "page": 14,
      "pageLabel": "4",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "5",
      "title": "DIIG process for planning and implementing a digital health enterprise",
      "page": 15,
      "pageLabel": "5",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "6",
      "title": "WHO SMART Guidelines approach",
      "page": 16,
      "pageLabel": "6",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "7",
      "title": "Sample workflow for an antenatal care business, with connections to the supply chain",
      "page": 17,
      "pageLabel": "7",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "table",
      "number": "1",
      "title": "Summary of chapters 1–4 Illustrative target",
      "page": 18,
      "pageLabel": "8",
      "confidence": 0.8,
      "evidence": [
        "referenced",
        "in-sequence"
      ]
    },
    {
      "kind": "figure",
      "number": "8",
      "title": "Alignment of national strategies",
      "page": 20,
      "pageLabel": "10",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "9",
      "title": "Inconsistent use of standardized product nomenclature across the supply chain",
      "page": 21,
      "pageLabel": "11",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "10",
      "title": "Example of outputs from this chapter",
      "page": 26,
      "pageLabel": "16",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "11",
      "title": "Health supply chain end-to-end visibility and traceability",
      "page": 29,
      "pageLabel": "19",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "12",
      "title": "SCISMM maturity levels for HSCISs",
      "page": 31,
      "pageLabel": "21",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "13",
      "title": "DIIG digital health enterprise architecture framework",
      "page": 33,
      "pageLabel": "23",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "14",
      "title": "DHSC architecture framework",
      "page": 34,
      "pageLabel": "24",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "15",
      "title": "Maturity-based architecture: moving from SCISMM Level 3 to Level 4",
      "page": 36,
      "pageLabel": "26",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "16",
      "title": "Maturity-based architecture: moving from SCISMM Level 4 to Level 5",
      "page": 37,
      "pageLabel": "27",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "17",
      "title": "Architecture based on supply chain design: centralized management",
      "page": 38,
      "pageLabel": "28",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "18",
      "title": "Architecture based on supply chain design: decentralized management (option A)",
      "page": 39,
      "pageLabel": "29",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "19",
      "title": "Architecture based on supply chain design: decentralized management (option B)",
      "page": 40,
      "pageLabel": "30",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "20",
      "title": "Benefits of cross-enterprise analytics services",
      "page": 41,
      "pageLabel": "31",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "21",
      "title": "Example of outputs from this chapter",
      "page": 43,
      "pageLabel": "33",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "22",
      "title": "Building blocks of digital health and DHSC implementation",
      "page": 45,
      "pageLabel": "35",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "table",
      "number": "2",
      "title": "Illustrative implementation considerations for the DHSC",
      "page": 46,
      "pageLabel": "36",
      "confidence": 0.8,
      "evidence": [
        "referenced",
        "in-sequence"
      ]
    },
    {
      "kind": "figure",
      "number": "23",
      "title": "Cost components to determine the total cost of ownership",
      "page": 49,
      "pageLabel": "39",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "table",
      "number": "3",
      "title": "Illustrative cost drivers of DHSC implementation Cost categories",
      "page": 50,
      "pageLabel": "40",
      "confidence": 0.8,
      "evidence": [
        "referenced",
        "in-sequence"
      ]
    },
    {
      "kind": "figure",
      "number": "24",
      "title": "Achieving track and trace capabilities through DHSC architecture components",
      "page": 55,
      "pageLabel": "45",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "25",
      "title": "Illustrative example of a traceability service interface",
      "page": 56,
      "pageLabel": "46",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "26",
      "title": "Current-state supply chain systems in Ethiopia",
      "page": 59,
      "pageLabel": "49",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "27",
      "title": "Future-state supply chain systems in Ethiopia",
      "page": 59,
      "pageLabel": "49",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "28",
      "title": "Current-state supply chain systems in Malawi",
      "page": 61,
      "pageLabel": "51",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "29",
      "title": "Future-state supply chain systems in Malawi",
      "page": 61,
      "pageLabel": "51",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "30",
      "title": "Visualization of future-state architecture from Malawi’s SCSA",
      "page": 62,
      "pageLabel": "52",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "31",
      "title": "Current-state supply chain systems in Rwanda",
      "page": 64,
      "pageLabel": "54",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "32",
      "title": "Future-state supply chain systems in Rwanda",
      "page": 64,
      "pageLabel": "54",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    }
  ],
  "images": [
    {
      "id": "vfig-p011",
      "file": "figures/vfig-p011.png",
      "page": 11,
      "shows": [
        "1"
      ],
      "narratives": {
        "en": "Fig 1, 'Public health supply chain partners and processes'. Four nested circles. The outer blue circle holds forecasting and planning and traceability, with the Ministry of health, regulators, procurers, manufacturers/distributors and logistics providers on or near its rim. The orange circle holds sourcing and contract management, procurement and transportation/shipping. The purple circle holds warehouse management, order management and transportation/distribution, with central and regional warehouses on its rim. The innermost green circle holds dispensing, with community health, health facilities and individuals at the centre."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p012",
      "file": "figures/vfig-p012.png",
      "page": 12,
      "shows": [
        "2"
      ],
      "narratives": {
        "en": "Fig 2, 'Information flow across supply chain processes'. Eight rounded boxes: forecasting and planning, sourcing and contract management, order management, traceability, procurement, warehouse management, transportation and dispensing. Two-headed arrows join them, showing that information flows both ways between the processes; warehouse management is the most connected box."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p013",
      "file": "figures/vfig-p013.png",
      "page": 13,
      "shows": [
        "3"
      ],
      "narratives": {
        "en": "Fig 3, 'Digital health supply chain'. Six purple hexagons surround an icon labelled Individuals: digital ecosystem, end-to-end visibility, data and analytics, transactional systems, advanced digitization and collaborative processes. A dashed ring around them carries eleven partners as dots: Ministry of health, community health, health facilities, regional warehouses, private sector, central warehouse, regulators, logistics providers, procurers and manufacturers/distributors."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p014",
      "file": "figures/vfig-p014.png",
      "page": 14,
      "shows": [
        "4"
      ],
      "narratives": {
        "en": "Fig 4, 'The stepwise approach used in this handbook'. Four coloured chevrons in a row: 1. Defining a holistic DHSC strategy; 2. Defining the DHSC architecture; 3. Planning for scalable implementation and sustainable operations; 4. Using the DHSC to implement traceability. Chevron 1 lists four steps (identify and engage stakeholders, analyse the current state of HSCISs, define the vision and strategic goals, define a strategic roadmap and performance indicators). Chevron 2 lists three (assess the current state of HSCISs, define a target architecture, identify implementation activities and map them to strategic goals). Chevron 3 lists four (plan the implementation, develop an operational plan, develop a budget, and implement each intervention). The crop also includes the chapter list and a 'Before using this handbook' box above the figure."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p015",
      "file": "figures/vfig-p015.png",
      "page": 15,
      "shows": [
        "5"
      ],
      "narratives": {
        "en": "Fig 5, 'DIIG process for planning and implementing a digital health enterprise'. Seven numbered, colour-coded phases — from 01 assessing the current state and enabling environment to 07 implementing, maintaining and scaling — each with its steps. To the right, resource tiles are placed against the phases they serve and marked as PDF or online, including the WHO–ITU eHealth strategy toolkit, the Digital implementation investment guide, the ITU SDG digital investment framework, TOGAF, OpenHIE, the WHO SMART guidelines with digital adaptation kits, and the WHO MAPS toolkit. 'WHO handbook for health supply chain architecture (this document)' is highlighted twice: spanning phases 02 to 04, and in phase 07. Adapted from the 2020 WHO Digital Implementation Investment Guide."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p016",
      "file": "figures/vfig-p016.png",
      "page": 16,
      "shows": [
        "6"
      ],
      "narratives": {
        "en": "Fig 6, 'WHO SMART Guidelines approach'. A top band of five knowledge layers, each fed from a research and evidence base: L1 narrative (enhanced guidelines), L2 operational (digital adaptation kits), L3 machine-readable (machine-readable recommendations), L4 executable (reference software) and L5 dynamic (precision health models). A localisation bar leads down to five matching country adaptations: national policies and procedures, localized requirements, localized machine-readable code and standards, localized digital services, and dynamic applications trained for local outcomes. These feed data, evidence and impact, and an 'Evidence from digital implementations' arrow returns to the research base. Source: adapted from WHO SMART Guidelines."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p017",
      "file": "figures/vfig-p017.png",
      "page": 17,
      "shows": [
        "7"
      ],
      "narratives": {
        "en": "Fig 7, 'Sample workflow for an antenatal care business, with connections to the supply chain highlighted'. A BPMN diagram with client and health worker lanes: arrival, registration, rapid assessment, danger signs, pregnancy confirmation, quick check, profile and history, the ANC assessment group, the counselling and treatment group (10.1 to 10.9), referral, scheduling and self-care. An enlarged inset shows the tasks outlined in purple as connected to the supply chain: 9 conduct laboratory tests and imaging, 10.5 nutrition supplementation, 10.7 immunizations and 10.9 deworming and malaria counselling and prophylaxis. Source: adapted from the 2021 WHO Digital Adaptation Kit for Antenatal Care."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p020",
      "file": "figures/vfig-p020.png",
      "page": 20,
      "shows": [
        "8"
      ],
      "narratives": {
        "en": "Fig 8, 'Alignment of national strategies'. Nested arrow shapes, each ending in VISION. The health strategy contains the health supply chain strategy, which contains the medicines and health product strategy. The digital/IT strategy contains the digital health strategy. The digital health supply chain strategy sits where the two families overlap."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p021",
      "file": "figures/vfig-p021.png",
      "page": 21,
      "shows": [
        "9"
      ],
      "narratives": {
        "en": "Fig 9, 'Inconsistent use of standardized product nomenclature across the supply chain'. A dashed arrow marks the physical flow of health products from manufacturers through the central warehouse, health facilities and community health workers to patients. Below, each holds the same product under a different code: product code 123123 at the manufacturer, A1232 in mSupply, P44545 in eLMIS and AM545 on paper forms, joined by broken chain-link icons."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p026",
      "file": "figures/vfig-p026.png",
      "page": 26,
      "shows": [
        "10"
      ],
      "narratives": {
        "en": "Fig 10, 'Example of outputs from this chapter'. A table whose rows are the DHSC vision (consistent and timely access to quality medicines through a seamless, technology-enabled supply chain), three strategic goals (system-driven processes, interoperability, traceability of all health products), six strategic objectives with targets such as automating 80% of central warehouse operations, and a four-year strategic roadmap from digitalizing the central warehouse in year 1 to batch traceability in year 4."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p029",
      "file": "figures/vfig-p029.png",
      "page": 29,
      "shows": [
        "11"
      ],
      "narratives": {
        "en": "Fig 11, 'Health supply chain end-to-end visibility and traceability'. Product flows from manufacturing and shipping through customs, central warehouse receiving and inventory management, distribution, regional warehouse replenishment and health facility dispensing to individuals, with forecasting and planning, supplier and contract management, procurement and order management above. Arcs mark end-to-end visibility at country and global level, and arrows below mark track and trace at national and global level."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p031",
      "file": "figures/vfig-p031.png",
      "page": 31,
      "shows": [
        "12"
      ],
      "narratives": {
        "en": "Fig 12, 'SCISMM maturity levels for HSCISs'. Five levels of the supply chain information system maturity model, each with its characteristics and an example: level 1 reporting-based (manual, paper or stand-alone tools), level 2 transactional (siloed), level 3 advanced digitalization (integrated), level 4 end-to-end visibility (exchanged) and level 5 digital ecosystem (collaborated). Reproduced by permission from Digital Square."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p033",
      "file": "figures/vfig-p033.png",
      "page": 33,
      "shows": [
        "13"
      ],
      "narratives": {
        "en": "Fig 13, 'DIIG digital health enterprise architecture framework'. Within the enterprise, a digital health platform holds shared services (business domain and registry services such as terminology, client, facility, product and health worker registries), data sources (institution-based and population-based) and data services (analytics, dashboards, repositories), joined by an interoperability layer of enabling components. Point-of-service applications below are reused across programmes or used for one use case only; external non-health systems sit to the right; a legend marks investment types. Adapted from the 2020 WHO Digital Implementation Investment Guide."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p034",
      "file": "figures/vfig-p034.png",
      "page": 34,
      "shows": [
        "14"
      ],
      "narratives": {
        "en": "Fig 14, 'DHSC architecture framework'. Inside a frame labelled DIGITAL HEALTH SUPPLY CHAIN ENTERPRISE: SHARED SERVICES (foundational components: facility, product and supplier registries), DATA SERVICES (analytics — supply chain reports, data warehouse; traceability — track and trace, product verification) and Digital ecosystems (quality, health management information, regulatory, and finance and insurance systems). Below them, an INTEROPERABILITY LAYER of enabling components: authentication, encryption, transformation, orchestration, validation and translation. At the bottom, HEALTH SUPPLY CHAIN INFORMATION SYSTEMS (forecasting and planning, order, warehouse and cold chain management, procurement, supplier and contract management, transportation management and dispensing), beside EXTERNAL SYSTEMS (global platforms, manufacturer systems, data repositories). Callouts explain each layer — for example, that OpenHIM is a useful reference for interoperability components, and SCISMM and TSS v2 for the supply chain systems."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p036",
      "file": "figures/vfig-p036.png",
      "page": 36,
      "shows": [
        "15"
      ],
      "narratives": {
        "en": "Fig 15, 'Maturity-based architecture: moving from SCISMM Level 3 to Level 4'. The digital health supply chain enterprise has shared services (facility, product and supplier registries) and data services (supply chain reports, data warehouse, track and trace, product verification) above an interoperability layer (authentication, encryption, transformation, orchestration, validation, translation), which connects eight health supply chain information systems: forecasting and planning, order, warehouse and cold chain management, procurement, supplier and contract management, transportation management and dispensing."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p037",
      "file": "figures/vfig-p037.png",
      "page": 37,
      "shows": [
        "16"
      ],
      "narratives": {
        "en": "Fig 16, 'Maturity-based architecture: moving from SCISMM Level 4 to Level 5'. The level-4 architecture of Fig 15 with analytics and traceability data services, plus a digital ecosystem (quality, health management information, regulatory and finance systems) and external systems (global platforms, manufacturer systems, data repositories) joined through the interoperability layer."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p038",
      "file": "figures/vfig-p038.png",
      "page": 38,
      "shows": [
        "17"
      ],
      "narratives": {
        "en": "Fig 17, 'Architecture based on supply chain design: centralized management'. Shared and data services, a digital ecosystem and external systems around an interoperability layer that serves a single set of eight health supply chain information systems managed centrally."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p039",
      "file": "figures/vfig-p039.png",
      "page": 39,
      "shows": [
        "18"
      ],
      "narratives": {
        "en": "Fig 18, 'Architecture based on supply chain design: decentralized management (option A)'. The same services and interoperability layer, with the health supply chain information systems split in two: at national level forecasting and planning, procurement, supplier and contract, transportation, warehouse and cold chain management; at facility level order management, dispensing, inventory and cold chain management."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p040",
      "file": "figures/vfig-p040.png",
      "page": 40,
      "shows": [
        "19"
      ],
      "narratives": {
        "en": "Fig 19, 'Architecture based on supply chain design: decentralized management (option B)'. The DHSC architecture — shared services, data services, digital ecosystems, an interoperability layer of enabling components, and external systems — with its health supply chain information systems divided by level. At national level: forecasting and planning, procurement, supplier and contract management, transportation management, warehouse management and cold chain management. At district level: procurement, order management, inventory management and cold chain management. At facility level: dispensing."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p041",
      "file": "figures/vfig-p041.png",
      "page": 41,
      "shows": [
        "20"
      ],
      "narratives": {
        "en": "Fig 20, 'Benefits of cross-enterprise analytics services'. Along the bottom runs the physical supply chain: manufacturing, shipping, regulatory customs, central-warehouse receiving and inventory management, distribution, regional-warehouse replenishment, health-facility dispensing, and patients. Above it sit the planning processes: forecasting and planning; supplier and contract management; procurement; and order management. Dashed arrows carry 'Transactional data from systems relevant to the supply chain' up through the INTEROPERABILITY LAYER into DATA SERVICES — analytics: supply chain reports and a data warehouse. A callout lists the questions analytics services answer: optimizing inventory against consumption to minimize stockouts, whether planned supplies will arrive in time, forecast accuracy against actual consumption, on-time and in-full delivery, wastage and leakage, stock at risk of expiry and where to move it, where and how often stockouts occur, and supplier performance."
      },
      "state": "draft"
    },
    {
      "id": "img-p043-1",
      "file": "images/img-p043-1.png",
      "page": 43,
      "narratives": {
        "en": "A small thumbnail of a target health supply chain architecture diagram, shown in the 'Year 3 and 4 – Target architecture maturity to next level' cell of Fig. 21, 'Example of outputs from this chapter', in the Defining the DHSC architecture chapter. The diagram is arranged in labelled boxes: Shared services with foundational components such as Facility Registry and Product Registry; Data services with Analytics (BI reports, Data warehouse) and Traceability (Track and Trace, Product Verification); an Interoperability layer of enabling components such as Authentication, Encryption, Orchestration, Transformation, Translation and Validation; and Health supply chain systems including Forecasting and Planning, Order Management, Warehouse Management, Cost Management, Procurement, Supplier and Contract Management, Transportation Management and Dispensing. To the right, Digital ecosystem and External systems boxes list items such as Quality systems, Health management information systems, Regulatory systems, Finance and insurance systems, Global platform, Manufacturer systems and Data repositories. At this size the labels are only partly legible.",
        "fr": "Petite vignette d'un diagramme d'architecture cible de chaîne d'approvisionnement sanitaire, présentée dans la cellule « Années 3 et 4 – Faire progresser la maturité de l'architecture cible au niveau supérieur » (Year 3 and 4 – Target architecture maturity to next level) de la Fig. 21, « Exemple de résultats issus de ce chapitre » (Example of outputs from this chapter), au chapitre consacré à la définition de l'architecture de la chaîne d'approvisionnement sanitaire numérique (DHSC). Le diagramme est organisé en boîtes intitulées : Services partagés (Shared services) avec des composants fondamentaux tels que le Registre des établissements (Facility Registry) et le Registre des produits (Product Registry) ; Services de données (Data services) avec l'Analytique (Analytics : rapports décisionnels BI, entrepôt de données) et la Traçabilité (Traceability : suivi et traçabilité, vérification des produits) ; une couche d'Interopérabilité (Interoperability layer) regroupant des composants habilitants tels que l'Authentification, le Chiffrement, l'Orchestration, la Transformation, la Traduction et la Validation ; et les Systèmes de chaîne d'approvisionnement sanitaire (Health supply chain systems) comprenant la Prévision et la planification, la Gestion des commandes, la Gestion d'entrepôt, la Gestion des coûts, les Achats, la Gestion des fournisseurs et des contrats, la Gestion des transports et la Dispensation. À droite, les boîtes Écosystème numérique (Digital ecosystem) et Systèmes externes (External systems) énumèrent notamment les systèmes de qualité, les systèmes d'information de gestion sanitaire, les systèmes réglementaires, les systèmes financiers et d'assurance, la plateforme mondiale, les systèmes des fabricants et les référentiels de données. À cette échelle, les libellés ne sont que partiellement lisibles.",
        "es": "Pequeña miniatura de un diagrama de arquitectura objetivo de la cadena de suministro de salud, mostrada en la celda «Años 3 y 4 – Madurez de la arquitectura objetivo hacia el siguiente nivel» (Year 3 and 4 – Target architecture maturity to next level) de la Fig. 21, «Ejemplo de productos de este capítulo» (Example of outputs from this chapter), en el capítulo sobre la definición de la arquitectura de la cadena de suministro de salud digital (DHSC). El diagrama se organiza en recuadros etiquetados: Servicios compartidos (Shared services) con componentes fundacionales como el Registro de establecimientos (Facility Registry) y el Registro de productos (Product Registry); Servicios de datos (Data services) con Analítica (Analytics: informes de BI, almacén de datos) y Trazabilidad (Traceability: seguimiento y rastreo, verificación de productos); una capa de Interoperabilidad (Interoperability layer) de componentes habilitadores como Autenticación, Cifrado, Orquestación, Transformación, Traducción y Validación; y Sistemas de cadena de suministro de salud (Health supply chain systems) que incluyen Previsión y planificación, Gestión de pedidos, Gestión de almacenes, Gestión de costos, Adquisiciones, Gestión de proveedores y contratos, Gestión del transporte y Dispensación. A la derecha, los recuadros Ecosistema digital (Digital ecosystem) y Sistemas externos (External systems) enumeran elementos como sistemas de calidad, sistemas de información de gestión en salud, sistemas regulatorios, sistemas financieros y de seguros, plataforma mundial, sistemas de fabricantes y repositorios de datos. A este tamaño, las etiquetas solo son parcialmente legibles.",
        "ar": "صورة مصغّرة لمخطط البنية المستهدفة لسلسلة الإمداد الصحي، معروضة في خلية «السنتان 3 و4 – الارتقاء بنضج البنية المستهدفة إلى المستوى التالي» (Year 3 and 4 – Target architecture maturity to next level) من الشكل 21، «مثال على المخرجات من هذا الفصل» (Example of outputs from this chapter)، في فصل تحديد بنية سلسلة الإمداد الصحي الرقمية (DHSC). يتوزع المخطط في مربعات معنونة: الخدمات المشتركة (Shared services) وتضم مكونات تأسيسية مثل سجل المرافق (Facility Registry) وسجل المنتجات (Product Registry)؛ وخدمات البيانات (Data services) وتضم التحليلات (Analytics: تقارير ذكاء الأعمال، مستودع البيانات) وإمكانية التتبع (Traceability: التتبع والتعقب، التحقق من المنتجات)؛ وطبقة التشغيل البيني (Interoperability layer) من المكونات التمكينية مثل المصادقة، والتشفير، والتنسيق، والتحويل، والترجمة، والتحقق من الصلاحية؛ وأنظمة سلسلة الإمداد الصحي (Health supply chain systems) وتشمل التنبؤ والتخطيط، وإدارة الطلبات، وإدارة المستودعات، وإدارة التكاليف، والمشتريات، وإدارة الموردين والعقود، وإدارة النقل، والصرف. وإلى اليمين، تسرد مربعات المنظومة الرقمية (Digital ecosystem) والأنظمة الخارجية (External systems) عناصر مثل أنظمة الجودة، وأنظمة معلومات الإدارة الصحية، والأنظمة التنظيمية، والأنظمة المالية وأنظمة التأمين، والمنصة العالمية، وأنظمة المصنّعين، ومستودعات البيانات. وبهذا الحجم لا تكون التسميات مقروءة إلا جزئياً.",
        "ru": "Небольшая миниатюра схемы целевой архитектуры цепочки поставок в здравоохранении в ячейке «Годы 3 и 4 — переход зрелости целевой архитектуры на следующий уровень» (Year 3 and 4 – Target architecture maturity to next level) рис. 21 «Пример результатов этой главы» (Example of outputs from this chapter) в главе «Определение архитектуры цифровой цепочки поставок в здравоохранении (DHSC)». Схема организована в виде подписанных блоков: «Общие сервисы» (Shared services) с базовыми компонентами, такими как Реестр учреждений (Facility Registry) и Реестр продукции (Product Registry); «Сервисы данных» (Data services) с аналитикой (Analytics: BI-отчеты, хранилище данных) и прослеживаемостью (Traceability: отслеживание и контроль движения, верификация продукции); «Слой интероперабельности» (Interoperability layer) из обеспечивающих компонентов, таких как аутентификация, шифрование, оркестрация, трансформация, трансляция и валидация; и «Системы цепочки поставок в здравоохранении» (Health supply chain systems), включая прогнозирование и планирование, управление заказами, управление складом, управление затратами, закупки, управление поставщиками и контрактами, управление транспортировкой и отпуск продукции. Справа в блоках «Цифровая экосистема» (Digital ecosystem) и «Внешние системы» (External systems) перечислены системы качества, информационные системы управления здравоохранением, регуляторные системы, финансовые и страховые системы, глобальная платформа, системы производителей и репозитории данных. В таком масштабе подписи читаются лишь частично.",
        "zh": "目标卫生供应链架构图的小缩略图，显示在“定义数字卫生供应链（DHSC）架构”一章图 21“本章输出示例”（Example of outputs from this chapter）的“第 3 和第 4 年——将目标架构成熟度提升至下一级别”（Year 3 and 4 – Target architecture maturity to next level）单元格中。该图由带标签的方框组成：共享服务（Shared services），包含机构注册库（Facility Registry）和产品注册库（Product Registry）等基础组件；数据服务（Data services），包含分析（Analytics：BI 报表、数据仓库）和可追溯性（Traceability：追踪与溯源、产品验证）；互操作层（Interoperability layer），包含身份认证、加密、编排、转换、转译和校验等支撑组件；以及卫生供应链系统（Health supply chain systems），涵盖预测与规划、订单管理、仓储管理、成本管理、采购、供应商与合同管理、运输管理及配发。右侧的数字生态系统（Digital ecosystem）和外部系统（External systems）方框列出了质量系统、卫生管理信息系统、监管系统、财务与保险系统、全球平台、生产商系统和数据存储库等项。在此尺寸下，标签仅部分可辨认。"
      },
      "state": "draft"
    },
    {
      "id": "vfig-p043",
      "file": "figures/vfig-p043.png",
      "page": 43,
      "shows": [
        "21"
      ],
      "narratives": {
        "en": "Fig 21, 'Example of outputs from this chapter'. The vision, goals, objectives and roadmap of Fig 10 (greyed), with three new rows: the DHSC target architecture for years 1–2 and years 3–4, an implementation roadmap (enhance the warehouse management system and integrate it with the national product catalogue, barcode scanning, an interoperability mediator, integration of HSCISs, data models and a data warehouse, aggregated analytics), and outcomes such as WMS rolled out to 40% of facilities and the mediator deployed with 30% of integrations done."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p045",
      "file": "figures/vfig-p045.png",
      "page": 45,
      "shows": [
        "22"
      ],
      "narratives": {
        "en": "Fig 22, 'Building blocks of digital health and DHSC implementation'. Leadership and governance spans the top; below it strategy and investment; services and applications; standards and interoperability; infrastructure; legislation, policy and compliance; and workforce. Adapted from the 2012 WHO–ITU National eHealth Strategy Toolkit."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p049",
      "file": "figures/vfig-p049.png",
      "page": 49,
      "shows": [
        "23"
      ],
      "narratives": {
        "en": "Fig 23, 'Cost components to determine the total cost of ownership'. A dashed loop labelled 'Total cost of ownership' encloses four groups of cost components. IMPLEMENT: sourcing (RFP, RFI, RFQ), software, hardware and infrastructure, design and development, integration and interoperability, testing and training, and deployment. SCALE: expansion of deployment, training, and hardware and infrastructure. OPERATE: software subscriptions, maintenance (personnel, software, hardware), ongoing training, and monitoring and evaluation. ONGOING: management, governance and overhead. Adapted from the 2020 WHO Digital Implementation Investment Guide."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p055",
      "file": "figures/vfig-p055.png",
      "page": 55,
      "shows": [
        "24"
      ],
      "narratives": {
        "en": "Fig 24, 'Achieving track and trace capabilities through DHSC architecture components'. Along the bottom, the supply chain runs from regulator through central, regional and district warehouses to health facilities and patients. Each location's system — regulator systems, warehouse management, transportation management, inventory management, dispensing, and verification at the patient — exchanges data in both directions with the INTEROPERABILITY LAYER, as do the external systems (global platforms, manufacturer systems, data repositories). Above the layer, DATA SERVICES hold analytics and traceability (track and trace, product verification). A callout lists the questions traceability services answer: where a batch is now, whether supply chain integrity was maintained, who had custody on a date, where a batch was dispensed, whether the product moved through known locations, whether there were anomalies, and whether the product is genuine. A legend defines traceability data as what (product, batch and serial number), when, where and why (the transaction type)."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p056",
      "file": "figures/vfig-p056.png",
      "page": 56,
      "shows": [
        "25"
      ],
      "narratives": {
        "en": "Fig 25, 'Illustrative example of a traceability service interface'. At the top is a mock screen, 'Track and trace results for product 001001123123', batch A1001234. It shows a timeline of five verified events with their location and timestamp: verified and received at the central warehouse (11 Mar 2023); shipped from the central warehouse (5 Apr); verified and received at health facility 001 (6 Apr); verified and dispensed there (10 Apr); and a final patient-side verification of serial number 202 with GPS coordinates (10 Apr, 16:14). Below, the flow that produces it: the manufacturer, central/regional warehouse and health facilities emit ship, receive and dispense events, and handheld verify scans are made along the way. All of these feed DATA SERVICES (analytics and traceability), which answer the screen's query for the product code, batch, its serial numbers 201 to 204 and the expiry date."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p059",
      "file": "figures/vfig-p059.png",
      "page": 59,
      "shows": [
        "26",
        "27"
      ],
      "narratives": {
        "en": "Figs 26 and 27, current-state (March 2024) and future-state supply chain systems in Ethiopia. Current state: an OpenHIM interoperability layer, a master health facility registry, a national product catalogue under development and terminology services, DHIS2 and EMR, and supply chain systems including VITAS, FANOS, DAGU, eLMIS, eAPTs and eRIS, with eTrade and eCustom as external systems; a legend colours each by its state. Future state: the layered architecture with an ERP at national level, DAGU, eAPTs and mBrana at facility level, a product directory service, track and trace and product verification, and GFPVAN, manufacturers, eTrade and eCustom as external systems."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p061",
      "file": "figures/vfig-p061.png",
      "page": 61,
      "shows": [
        "28",
        "29"
      ],
      "narratives": {
        "en": "Figs 28 and 29, current-state (December 2023) and future-state supply chain systems in Malawi. Current state: OpenHIM, a master health facility registry, national product catalogue and terminology services, DHIS2, QAT and QuanTB for forecasting, OpenLMIS for orders, Navision for warehouse and procurement, eHIN for dispensing, cStock for inventory, GFPVAN outside. Future state: a supplier registry, supply chain reports, a data warehouse, track and trace and product verification are added; E-GP for procurement and contracts, a new transportation system, OpenLMIS and cStock at facility level, and parallel supply chains among external systems."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p062",
      "file": "figures/vfig-p062.png",
      "page": 62,
      "shows": [
        "30"
      ],
      "narratives": {
        "en": "Fig 30, 'Visualization of future-state architecture from Malawi's SCSA'. Layers from top: analytics and business intelligence (data warehouse, dashboards, reports, traceability, returns and recalls, verification); an OpenHIM interoperability layer; national supply chain information systems (procurement, forecasting and planning, supplier and contract, warehouse and transportation management) beside facility systems (OpenLMIS, cStock, eHIN); a second interoperability layer; and regulatory and foundational components (product item registration, product registry, facility registry, supplier registry, terminology). A global GFPVAN and manufacturers link from the left. Adapted from Malawi's 2022 Supply Chain Systems Architecture."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p064",
      "file": "figures/vfig-p064.png",
      "page": 64,
      "shows": [
        "31",
        "32"
      ],
      "narratives": {
        "en": "Figs 31 and 32, current-state (February 2022) and future-state supply chain systems in Rwanda. Current state: OpenHIM, a master health facility registry, national product catalogue and terminology services, DHIS2, QAT for forecasting, eLMIS for orders and inventory, SAGE for warehouse and procurement, EMR for dispensing. Future state: an ERP for supplier and contract, order, warehouse, inventory and procurement management, a new transportation system, QAT, EMR, a supplier registry, supply chain reports, a data warehouse, track and trace and product verification, with GPFVAN, manufacturers and BUFMAR among external systems."
      },
      "state": "draft"
    }
  ],
  "tables": [
    {
      "label": "Table 1",
      "caption": "",
      "pages": [
        7
      ],
      "columns": [
        {
          "titles": "DH&I WG"
        },
        {
          "titles": "Digital Health and Interoperability Working Group"
        }
      ],
      "rows": [
        [
          "DHSC",
          "digital health supply chain"
        ],
        [
          "DIIG",
          "Digital Implementation Investment Guide"
        ],
        [
          "eRIS",
          "Electronic Regulatory Information System"
        ],
        [
          "ERP",
          "enterprise resource planning"
        ],
        [
          "FTE",
          "full-time equivalent"
        ],
        [
          "GFPVAN",
          "Global Family Planning Visibility and Analytics Network"
        ],
        [
          "GHSC-PSM",
          "Global Health Supply Chain Program–Procurement and Supply Management"
        ],
        [
          "HSCIS",
          "health supply chain information system"
        ],
        [
          "HTSS",
          "Health Technical Support Services"
        ],
        [
          "ICT",
          "information and communications technology"
        ],
        [
          "IT",
          "information technology"
        ],
        [
          "ITU",
          "International Telecommunication Union"
        ],
        [
          "KPI",
          "key performance indicator"
        ],
        [
          "MOH",
          "ministry of health"
        ],
        [
          "NPC",
          "National Product Catalog"
        ],
        [
          "NSCA",
          "National Supply Chain Assessment"
        ],
        [
          "OpenHIE",
          "Open Health Information Exchange"
        ],
        [
          "QA",
          "quality assurance"
        ],
        [
          "RFP",
          "request for proposal"
        ],
        [
          "RFQ",
          "request for quotation"
        ],
        [
          "SCISMM",
          "Supply Chain Information System Maturity Model"
        ],
        [
          "SCSA",
          "Supply Chain Systems Architecture"
        ],
        [
          "SMART",
          "Standards-based, Machine-readable, Adaptive, Requirements-based and Testable"
        ],
        [
          "TOGAF",
          "The Open Group Architecture Framework"
        ],
        [
          "TSS",
          "Target Software Standards"
        ],
        [
          "TWG",
          "technical working group"
        ],
        [
          "USAID",
          "United States Agency for International Development"
        ],
        [
          "WHO",
          "World Health Organization"
        ],
        [
          "WMS",
          "warehouse management system"
        ]
      ],
      "narratives": {},
      "csv": "tables/table-1.csv"
    },
    {
      "label": "Table 2",
      "caption": "Fig 7. Sample workflow for an antenatal care business, with connections to the supply chain",
      "pages": [
        17
      ],
      "columns": [
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": "tneilC"
        },
        {
          "titles": "Yes Start A f r a r c iv il e it y at t S c h o e e m l f h - 1 m c o 3 a m u . r n e e i t i o y n r r W et o 1 u m 4 rn . a s n ? No End"
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        }
      ],
      "rows": [
        [
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "13. Self-care in the home or community",
          "",
          "",
          ""
        ],
        [
          "tneilC Arrive at facility Start 3. Confirm Not pregnant pregnancy ytilicaf No Refer to other sexu Pregnant htlaeH 1.Rapid 2.Danger assessment A. signs 4. and 5.Quic rekrow Registration needing First management check referral? contact? (RAM) htlaeH Yes N C.Antenatal care (ANC) referral",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "Yes 13. 14. Self-care in Woman No the home or returns? community End"
        ],
        [
          "",
          "",
          "",
          "",
          "ytilicaf htlaeH",
          "rekrow",
          "A Regis",
          "3. Confirm Not pregnant No pregnancy Refer to other sexual and reproductive health services tr . ation m as a 1 s ( n . e R a a R s A g n s a e M d m p m i ) e d e n n t t 2 r n . e e s D fe i e g a r d n n r i a s n g l g e ? r Pregnant co F n 4 i t r a . s c t t? 5 c . h Q e u c i k ck First contact w p C h r o o i o m s 6 f l t i l o l a . e e r n c y a ’ t s nd 1 1 0 0 c . . o 1 C u B n o e s u h e n a l s li v e n i l o g li u n r g, in-fa P c s h il y y it m s y 1 i o p 0 m l t . o o 2 a g m n i a c s a g l ement a c n 1 o d 0 u . n t 3 r s e e D a l t i l m e in t g ent Sche 1 N d 2 o u . ling",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "",
          "",
          "al",
          "htlaeH and reproductive First contac",
          "",
          "htlaeH",
          "",
          "counselling ANC assessment 10.6 Risk Yes C.Antenatal care (ANC) referral Not first contact an s d 7 y . m fo C p l h l t o o e w m c - k s up C ph e o y x n 8 s a d . i m u ca ct l 9 l t a . e im b C s o t a o s r g n a a i d t n o n u g r d c y t 1 a 0 n . d 4 t D re ia a g tm no e s n i t s su 1 p 0 p .5 le N m u e t n ri t t a io ti n on r c e o g d u e u n n c s t e e io r l a l n in l a g nd Immu 1 n 0 iz .7 ations pa 1 c r 0 t o n .8 u e n r In s v t e i i o m ll l i e n a n g te ce 1 c 0 o p a . u 9 r n n o d D s p e e m h l w y l a i l n o a la g r x m r i a i s a i n n d g",
          "10.4 Diagnosis and treatment 10.7 Immunizations",
          "",
          "counselling 10.6 Risk 10.5 Nutrition reduction and supplementation general counselling",
          "",
          "11. Referral Yes needed? C.ANC referral",
          "",
          "",
          "",
          ""
        ],
        [
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "10.7 Immunizations",
          "10.8 Intimate partner violence counselling",
          "10.9 Deworming and malaria counselling and prophylaxis",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "health services",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "10.Counselling, in-facility management and treatment 6. Collect 10.2 t woman’s 10.1 Behaviour Physiological 10.3 Diet profile and counselling symptoms counselling history counselling ANC assessment 10.6 Risk 8. 9.Conduct 10.4 Diagnosis 10.5 Nutrition reduction and 7.Check Conduct laboratory and treatment supplementation general symptoms physical tests and counselling and follow-up exam imaging 10.8 Intimate 10.9 Deworming 10.7 partner violence and malaria Immunizations counselling counselling and prophylaxis",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "ch",
          ""
        ],
        [
          "",
          "",
          "k",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "R ne",
          ""
        ],
        [
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "",
          "",
          "ot",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          ""
        ]
      ],
      "narratives": {},
      "csv": "tables/table-2.csv"
    },
    {
      "label": "Table 3",
      "caption": "",
      "pages": [
        22
      ],
      "columns": [
        {
          "titles": "Potential risks"
        },
        {
          "titles": "Mitigation strategies"
        }
      ],
      "rows": [
        [
          "Lack of engagement and participation from identified stakeholders",
          "» Under the leadership of the MOH, establish a steering committee and a TWG and schedule regular meetings. » Identify and enlist a DHSC sponsor (such as a senior MOH leader). » Use the steering committee structure shown in Annex 2."
        ],
        [
          "Unclear approval and decision-making process",
          "Have the TWG establish a governance process to review and approve DHSC initiatives."
        ],
        [
          "Relevant stakeholders and/or decision- makers excluded from the TWG or steering committee",
          "Determine appropriate participation in the TWG or steering committee not only by using organograms but also including all relevant public health and health supply chain partners (e.g., donor organizations, implementing partners and MOH health programme teams) in the initial meetings. Also, develop an agreed-upon list of stakeholders to be excluded from the initial meetings."
        ]
      ],
      "narratives": {},
      "csv": "tables/table-3.csv"
    },
    {
      "label": "Table 4",
      "caption": "",
      "pages": [
        23
      ],
      "columns": [
        {
          "titles": "Potential risks"
        },
        {
          "titles": "Mitigation strategies"
        }
      ],
      "rows": [
        [
          "Misalignment of technical and political priorities",
          "» Establish connections between political and technical priorities by identifying the mutual benefits of pursuing technical priorities. » Promote engagement and dialogue between technical experts and political leaders and communicate critical health supply chain challenges and their effects on the country. » Have technical experts and leaders convey the advantages of digital transformation to senior political leaders in advocacy sessions, emphasizing the alignment of technical priorities with their political goals."
        ],
        [
          "Lack of relevant inputs (e.g., NSCA Toolkit, national supply chain strategy or national digital health strategy) to inform data- driven decisions, leading to arbitrary priority setting",
          "» Conduct detailed assessments of the health supply chain and its systems using tools such as the NSCA Toolkit (22) and SCISMM (16). » Use outputs from such assessments as key inputs for the DHSC initiative."
        ]
      ],
      "narratives": {},
      "csv": "tables/table-4.csv"
    },
    {
      "label": "Table 5",
      "caption": "",
      "pages": [
        24
      ],
      "columns": [
        {
          "titles": "Potential risks"
        },
        {
          "titles": "Mitigation strategies"
        }
      ],
      "rows": [
        [
          "Dependence on senior leaders for key decisions could delay the process of approving and endorsing the strategy.",
          "» Keep the stakeholder matrix updated and implement appropriate delegation plans for decision- making if primary decision-makers are not available. » Identify the alternate focal points or decision-makers."
        ]
      ],
      "narratives": {},
      "csv": "tables/table-5.csv"
    },
    {
      "label": "Table 6",
      "caption": "",
      "pages": [
        25
      ],
      "columns": [
        {
          "titles": "Potential risks"
        },
        {
          "titles": "Mitigation strategies"
        }
      ],
      "rows": [
        [
          "No dedicated staff to develop and monitor performance indicators",
          "» Use existing operational staff to define indicators using existing resources such as the NSCA key performance indicators (KPIs) (22). » Incorporate the identified KPIs into ongoing operational processes and workflows (where feasible) to minimize manual data collection and analysis."
        ],
        [
          "Funding gaps to advance strategic goals",
          "» Adopt a phased approach to achieving the goals. Define phases that are manageable from a funding and capacity perspective. » Engage and collaborate with partners and donors to identify funding opportunities. » Temporarily reduce the scope of specific lower-priority initiatives until additional funds are available."
        ],
        [
          "Available funding does not align with the established timeline",
          "» Develop the roadmap iteratively in close collaboration with funding partners to incorporate their feedback and ensure alignment."
        ]
      ],
      "narratives": {},
      "csv": "tables/table-6.csv"
    },
    {
      "label": "Table 7",
      "caption": "Fig 10. Example of outputs from this chapter",
      "pages": [
        26
      ],
      "columns": [
        {
          "titles": "Consistent and timely access to quality medicines and medical products for the population, through seamless supply chain enabled by technologies that provide efficient tools for providers"
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        }
      ],
      "rows": [
        [
          "1. Implement system-driven processes to provide timely access to quality data",
          "",
          "2. Achieve interoperability of systems to enable effortless exchange of data",
          "",
          "3. Enable traceability of all health products to ensure patient safety",
          ""
        ],
        [
          "Automate 80% of central warehouse operations",
          "Automate receiving and dispensing in 75% of health facilities",
          "Standardize product, facility, and other master data",
          "Deploy interop layer and integrate central and regional HSCISs",
          "Deploy a data warehouse to aggregate supply chain data",
          "Enable national- level batch traceability"
        ],
        [
          "Year 1 Digitalization of central warehouse",
          "Year 2 Digitalization of health facilities",
          "Year 2 Data stan- dardization",
          "Year 3 System integrations",
          "Year 3 Data aggregation",
          "Year 4 Batch traceability"
        ]
      ],
      "narratives": {},
      "csv": "tables/table-7.csv"
    },
    {
      "label": "Table 8",
      "caption": "",
      "pages": [
        30
      ],
      "columns": [
        {
          "titles": "Potential risks"
        },
        {
          "titles": "Mitigation strategies"
        }
      ],
      "rows": [
        [
          "No partner or funding to conduct SCISMM assessments",
          "Identify needed assessment activities during the annual work planning process in order to budget for, identify and request funding from partners."
        ],
        [
          "Master data are not identified as an essential building block in the current state assessment",
          "Conduct holistic assessments of the current HSCISs using SCISMM (16) to identify gaps in tools and governance and highlight impacts on interoperability, data quality, supply chain visibility and the ability to track and trace."
        ],
        [
          "Some HSCISs are assigned too much priority for inclusion in the architecture while user adoption and efficacy are low",
          "Plan and perform assessments such as SCISMM (16) on an annual basis to analyse utilization gaps and identify ways to mitigate gaps through continuous user training and making utilization of systems the only way to perform processes."
        ]
      ],
      "narratives": {},
      "csv": "tables/table-8.csv"
    },
    {
      "label": "Table 9",
      "caption": "Fig 12. SCISMM maturity levels for HSCISs",
      "pages": [
        31
      ],
      "columns": [
        {
          "titles": "SCISMM - Maturity Levels Level 1 2 Level Level 3 Level 4 Level 5 • Collaborative processes across various Ecosystems • Visibility across all supply • Basic automation of processes • A m d a v jo a r n it c y e d of d p i r g o it c a e l s i s z e a s tion of c a a h u cr a t o o in s m s fu a a n t l e l c d s ti u o d p n a p s t l a e y n e c a x h b c a h le i a n d n b g y e • A i e n c l t l o e s s g u y r p s a t p t e e l m y d c s w h s i a u t i h c n h o s t y a h s s e t H e r m IS s a nd • ➢ M u a l s e b E a o i n . a n n n g t s g u e . r i a c - y p r l M a s e l in y y p p a t s d e o n o t r e r u r i s t m v a b p i e l n a r s n o e g s o r a e p b d n d d r a e o s m o r s h c e r d o e e d s a s n e t s t t t t a a e s h o n s l o o y d r l s - • ➢ S t s h y y r m E r s s e . o t t g a q e e u . n u m m g - a i h s R g s d i e t e t r i r a m o i a v l n n e e t s i n n s m i a t n p e c s r a t y o c i n s a o c t p e o n e s t m r a u s d l e r e e s r of • • ➢ I A c l s e n y r u a E v i t s t t e l . e t i o l g e g c o r . m a a m r c - a g l a a A s t s i t e t n u u i e o d g t p d n o w d p p m a l o y r t a o r a c k t c h e s f e l d h a o s i a s w i n n e r s e f s v u d e a n n c a c r t c o t o r i s r o o y s n s s s • ➢ I s f n u y t s E t n s i u e . m c t g g p e t . e r i p m - o a l v P t n y s i i l s s o c a i n h b n a i n o l i i i f n t n y a g o l o l p b f s e a u e r s n p a e d t p d i - l o t y o n o c n s - h e r a n e i d a n l - • ➢ S r a w e u y i p E i g n t s t . l h u o t g t a e e l m . t G a m g f - o t l a r C o o s a r t b m o r e t i y e n a u d s d t l s n e d s y s t w g u a y s r r t y s t i c a t e a t h h s e t m e y e m a g x s d s s l t c s o e f G h o b m a F r a n P s l g V e A N basis Reporting Based Transactional Advanced Digitalization End to End Visibility Digital Ecosystem (Manual) (Siloed) (Integrated) (Exchanged) (Collaborated)"
        },
        {
          "titles": ""
        }
      ],
      "rows": [
        [
          "",
          "• Collaborative processes across various Ecosystems • All supply chain systems integrated with other ecosystems such as HIS and regulatory systems • Systems integrated for automated data exchange with Global systems ➢ E.g. - Country systems integrated with global platforms such as GFPVAN"
        ],
        [
          "",
          "Digital Ecosystem (Collaborated)"
        ]
      ],
      "narratives": {},
      "csv": "tables/table-9.csv"
    },
    {
      "label": "Table 10",
      "caption": "",
      "pages": [
        32
      ],
      "columns": [
        {
          "titles": "Potential risks"
        },
        {
          "titles": "Mitigation strategies"
        }
      ],
      "rows": [
        [
          "Design of the DHSC architecture not aligning with best practices",
          "» Consult resources such as this handbook, SCISMM (16) and TSS v2 (20), along with principles such as the Principles for Digital Development (Annex 1), TOGAF (18) and the OpenHIE (17) framework, to help ensure alignment with best practices. » Engage with the practitioner community through groups such as the DHSC small working group to seek feedback on design."
        ],
        [
          "Risk of choosing technology solutions prematurely, without considering innovation trends and potential future changes, resulting in those solutions quickly becoming outdated or challenging to adapt",
          "In addition to following the outlined DHSC architecture framework, consider scalability and sustainability when selecting digital solutions for the health supply chain. A key mandate of the TWG should be oversight in this area."
        ]
      ],
      "narratives": {},
      "csv": "tables/table-10.csv"
    },
    {
      "label": "Table 11",
      "caption": "",
      "pages": [
        42
      ],
      "columns": [
        {
          "titles": "Potential risks"
        },
        {
          "titles": "Mitigation strategies"
        }
      ],
      "rows": [
        [
          "Activities are not aligned with DHSC strategic goals",
          "Identify and plan implementation activities after the vision, strategy and architecture have been developed and approved. Review any ongoing activities and adjust them to ensure alignment with DHSC goals and priorities."
        ]
      ],
      "narratives": {},
      "csv": "tables/table-11.csv"
    },
    {
      "label": "Table 12",
      "caption": "",
      "pages": [
        43
      ],
      "columns": [
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": "Fig. 21"
        }
      ],
      "rows": [
        [
          "Consistent and timely access to quality medicines and medical products for the population, through seamless supply chain enabled by technologies that provide efficient tools for providers",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "1. Implement system-driven processes to provide timely access to quality data",
          "",
          "",
          "2. Achieve interoperability of systems to enable effortless exchange of data",
          "",
          "3. Enable traceability of all health products to ensure patient safety",
          "",
          "",
          ""
        ],
        [
          "Automate 80% of central warehouse operations",
          "Automate receiving and dispensing in 75% of health facilities",
          "",
          "Standardize product, facility, and other master data",
          "Deploy interop layer and integrate central and regional HSCISs",
          "Deploy a data warehouse to aggregate supply chain data",
          "",
          "Enable national- level batch traceability",
          ""
        ],
        [
          "Year 1 Digitalization of central warehouse",
          "Year 2 Digitalization of health facilities",
          "",
          "Year 2 Data stan- dardization",
          "Year 3 System integrations",
          "Year 3 Data aggregation",
          "",
          "Year 4 Batch traceability",
          ""
        ],
        [
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "Year 1 and 2 Target architecture",
          "",
          "DIGITAL HEALTH SUPPLY SHAR S E P F u FD r Ca o p o co d p Su iml u l i En i t c e py dR t r o a R V R R nt e I e i e e Co g g g ni nE i s i s t s aS ts t t r l r r y y y DAT W A SAC a S n rDRa E eael R h y tp o t a V oi u c I r C s st e s ES TTr V ra e a Pc r ckrifo e i & cd a a u bT tc ir i l otai t n cye ILEC NAno TamYEbEp RlRio OnngP E R ABILITY AOurtchheensttircaattiioonn EVnaclirdyapttiioonn TraTnrasnfosrlamtiaotnion CHAIN ENTERPRISE e n ts HHEEAAFFooLLrrPP TTeell HH aacc aann SSssnn UUttiiiinn PPnnggggPP LL&&YY CCHHAAIINN MM SS aa YY nn SSOOaa TTrrgg EEddee MMeemmrrSS eenntt MMWWaaaannrraaeegghheeoommuusseeeenn tt MMCCaaoonnllddaagg CCeehhmmaaeeiinnnn tt PPrrooccuurreemmeenntt MMSSaaCCuunnooppaannppggttlleerriieeaammrrcc eett&& nn tt TTMMrraaaannnnssaappggooeerrmmttaaeettiinnoottnn DDiissppeennssiinngg",
          "",
          "Year 3 and 4 Target architecture maturity to next level",
          "",
          "",
          "",
          ""
        ],
        [
          "Enhance WMS Integrate WMS and National Product Catalog (NPC)",
          "Implement barcode- scanning capabilities",
          "",
          "Develop and implement the interop mediator",
          "Integrate HSCISs through the mediator",
          "Design data models and implement data warehouse",
          "",
          "Aggregate data from all HSCISs and enable analytics",
          ""
        ],
        [
          "WMS deployed and rolled out across 40% of supply chain facilities WMS-NPC integration: 100% Barcode-scanning feature: 60%",
          "",
          "",
          "Interop mediator deployed and 30% of integrations completed",
          "",
          "Implementation pending",
          "",
          "",
          ""
        ]
      ],
      "narratives": {},
      "csv": "tables/table-12.csv"
    },
    {
      "label": "Table 2",
      "caption": "Table 2 provides illustrative considerations for each building block to help ensure successful DHSC implementation.",
      "pages": [
        45
      ],
      "columns": [
        {
          "titles": "LEADERSHIP AND GOVERNANCE"
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        }
      ],
      "rows": [
        [
          "STRATEGY AND INVESTMENT",
          "SERVICES AND APPLICATIONS",
          "LEGISLATION, POLICY, AND COMPLIANCE",
          "WORKFORCE"
        ],
        [
          "",
          "STANDARDS AND INTEROPERABILITY",
          "",
          ""
        ],
        [
          "",
          "INFRASTRUCTURE",
          "",
          ""
        ]
      ],
      "narratives": {},
      "csv": "tables/table-13.csv"
    },
    {
      "label": "Table 2",
      "caption": "Table 2. Illustrative implementation considerations for the DHSC",
      "pages": [
        46
      ],
      "columns": [
        {
          "titles": ""
        },
        {
          "titles": "Factor"
        },
        {
          "titles": "Illustrative considerations"
        },
        {
          "titles": ""
        }
      ],
      "rows": [
        [
          "",
          "",
          "What is the current state?",
          "What is needed?"
        ],
        [
          "tnemnorivne gnilbanE",
          "Leadership and governance",
          "» Can any national priorities be cited that align with DHSC goals to secure support from senior leadership? » Does a dedicated department oversee health ICT, digital health and the health supply chain? » Does the country have a national digital governance framework, such as TWGs?",
          ""
        ],
        [
          "",
          "Strategy and investment",
          "» Is the DHSC strategy endorsed and agreed upon by all stakeholders? » What investments in DHSC are currently ongoing? What additional investments are planned?",
          ""
        ],
        [
          "",
          "Legislation, policy and compliance",
          "» Does any existing legislation support data sharing, data standardization and traceability of pharmaceutical products? » Are policies in place regarding data storage, usage, retention and security? » Do mechanisms exist to ensure compliance with legislation and policies?",
          ""
        ],
        [
          "",
          "Workforce",
          "» Are there individuals in supply chain operational and technical roles who have the necessary skill sets? » Are knowledge management mechanisms in place, such as ongoing training and information-sharing programmes? » Is a strategy in place for incremental capacity development and talent retention?",
          ""
        ],
        [
          "",
          "Standards and interoperability",
          "» Are standardized reusable components in use, such as facility registries, product registries and supplier registries? » Is an interoperability framework in use to guide how systems integrate and exchange data? » Is an interoperability mediator in place to support data orchestration, translation and integrations? » Are standardized protocols in use for data exchange between systems? » Have global and open standards been adopted for data management and exchange?",
          ""
        ],
        [
          "tnemnorivne TCI",
          "Services and applications",
          "» What supply chain applications in use can be enhanced and reused? » Are processes in place to maintain and update software applications? Is a framework in place to engage the private sector in software application maintenance and upgrades?",
          ""
        ],
        [
          "",
          "Infrastructure",
          "",
          ""
        ]
      ],
      "narratives": {},
      "csv": "tables/table-14.csv"
    },
    {
      "label": "Table 3",
      "caption": "Table 3. Illustrative cost drivers of DHSC implementation",
      "pages": [
        50
      ],
      "columns": [
        {
          "titles": ""
        },
        {
          "titles": "Cost categories"
        },
        {
          "titles": "Cost drivers"
        }
      ],
      "rows": [
        [
          "stsoc gniognO",
          "Management",
          ""
        ],
        [
          "",
          "Governance",
          ""
        ],
        [
          "",
          "Overhead",
          ""
        ],
        [
          "stsoc noitatnemelpmi tnorfpU",
          "Sourcing",
          ""
        ],
        [
          "",
          "Software",
          ""
        ],
        [
          "",
          "Hardware and infrastructure",
          ""
        ],
        [
          "",
          "Design and development",
          ""
        ],
        [
          "",
          "Integration and interoperability",
          ""
        ],
        [
          "",
          "Testing and training",
          ""
        ],
        [
          "",
          "Deployment",
          ""
        ],
        [
          "stsoc gnilacs tnorfpU",
          "Expansion of deployment",
          ""
        ],
        [
          "",
          "Training",
          ""
        ],
        [
          "",
          "Hardware and infrastructure",
          ""
        ],
        [
          "stsoc snoitarepO",
          "Software",
          ""
        ],
        [
          "",
          "Maintenance",
          ""
        ],
        [
          "",
          "Ongoing training",
          ""
        ],
        [
          "",
          "Monitoring and evaluation",
          ""
        ]
      ],
      "narratives": {},
      "csv": "tables/table-15.csv"
    },
    {
      "label": "Table 16",
      "caption": "",
      "pages": [
        51,
        52
      ],
      "columns": [
        {
          "titles": "Potential risks"
        },
        {
          "titles": "Mitigation strategies"
        }
      ],
      "rows": [
        [
          "» Underestimating the costs and/or overlooking hidden costs",
          "» Use the guidance provided in this section to estimate all cost elements, including operational costs, to help budget for and identify funding sources to ensure successful implementation and continuous operations."
        ],
        [
          "» Human resource capacity constraints » Not having people with the appropriate skill sets » Lack of awareness of the required skill sets",
          "» Identify the necessary roles and skill sets early on. Use multiple strategies to add capacity, such as outsourcing, recruiting and engaging part-time consultants. Budget for additional staffing needs and identify funding sources to bridge capacity gaps. Plan for a phased rollout of systems to align with the availability of funding and staffing capacity. » Use a resource matrix, such as the one in Annex 7, to plan out necessary roles and responsibilities across phases of implementation and operations."
        ],
        [
          "» Poor adoption and use of systems if training does not contain appropriate content for the level of skill sets",
          "» Perform a skills assessment for each user before completing the training plan. » Complete a training needs assessment before conducting training. » Target and adapt training to meet the needs of the training audience."
        ],
        [
          "» Lack of reliable infrastructure (such as electricity, internet connectivity and computers) as HSCISs are rolled out to downstream facilities",
          "» Determine needs across all supply chain facilities and develop a detailed budget that includes operational costs. » Adopt a phased approach to roll out systems across supply chain facilities. » Align funding and other financial resources with the planned rollout phases."
        ],
        [
          "» Inconsistent use of supply chain processes across supply levels and facilities, leading to poor data quality, interoperability, aggregation and data availability",
          "» Conduct a supply chain system and process maturity assessment (using tools such as SCISMM) to identify process gaps and inconsistencies. » Address gaps during the system design phase and ensure consistent training of staff at all supply chain levels for uniform adoption and use of the system."
        ],
        [
          "» Saturation of existing digital tools and HSCISs due to lack of acceptance of emerging technology and enhancements",
          "» Conduct regular assessments using tools such as SCISMM to identify any new or potential gaps and improvement opportunities. » Plan to enhance or upgrade existing tools in a phased manner to meet changing supply chain needs."
        ],
        [
          "» Budget dependence on political factors such as election timelines and outcomes",
          "» Budget for DHSC initiatives at the start of a government’s term. » If initiatives require time beyond political events that might affect the budget, consider options for scaling back or phasing, depending on the context."
        ],
        [
          "» Budget rigidity that creates an obstacle to accommodating unforeseen but necessary changes (due to factors related to technological advances, regulatory changes, staffing, etc.)",
          "» Ensure that budgets account for potential changes and include a buffer. » If the buffer is exceeded, seek additional funding sources before scaling back the initiative."
        ]
      ],
      "narratives": {},
      "csv": "tables/table-16.csv"
    },
    {
      "label": "Table 17",
      "caption": "",
      "pages": [
        62
      ],
      "columns": [
        {
          "titles": "Warehouse"
        },
        {
          "titles": ""
        },
        {
          "titles": "Transportation"
        }
      ],
      "rows": [
        [
          "Management (Navision)",
          "",
          "Management (New)"
        ]
      ],
      "narratives": {},
      "csv": "tables/table-17.csv"
    },
    {
      "label": "Table 18",
      "caption": "",
      "pages": [
        65
      ],
      "columns": [
        {
          "titles": "1."
        },
        {
          "titles": "Digital implementation investment guide (DIIG): integrating digital interventions into health programmes. Geneva: World Health"
        }
      ],
      "rows": [
        [
          "",
          "Organization; 2020 (https://iris.who.int/handle/10665/334306). Licence: CC BY-NC-SA 3.0 IGO."
        ],
        [
          "",
          ""
        ],
        [
          "2.",
          "Digital Health & Interoperability Working Group [website]. Digital Square; 2024 (https://wiki.digitalsquare.io/index.php/Digital_"
        ],
        [
          "",
          "Health_%26_Interoperability_Working_Group)."
        ],
        [
          "",
          ""
        ],
        [
          "3.",
          "The differences between digitization, digitalization, and digital transformation in manufacturing [website]. Yokogawa Electric"
        ],
        [
          "",
          "Corporation; 2021 (https://www.yokogawa.com/library/resources/white-papers/the-differences-between-digitization-digitalization-"
        ],
        [
          "",
          "and-digital-transformation-in-manufacturing/)."
        ],
        [
          "",
          ""
        ],
        [
          "4.",
          "Digital transformation [website]. Gartner; 2024 (https://www.gartner.com/en/information-technology/glossary/digital-"
        ],
        [
          "",
          "transformation)."
        ],
        [
          "",
          ""
        ],
        [
          "5.",
          "Standards & digital transformation: good governance in a digital age, 2021. Vienna: United Nations Industrial Development"
        ],
        [
          "",
          "Organization; 2021 (https://www.unido.org/news/standards-digital-transformation-good-governance-digital-age)."
        ],
        [
          "",
          ""
        ],
        [
          "6.",
          "Digitalization [website]. Gartner; 2024 (https://www.gartner.com/en/information-technology/glossary/digitalization)."
        ],
        [
          "",
          ""
        ],
        [
          "7.",
          "Digitization [website]. Gartner; 2024 (https://www.gartner.com/en/information-technology/glossary/digitization)."
        ],
        [
          "",
          ""
        ],
        [
          "8.",
          "Reynolds CJ, Wyatt JC. Open source, open standards, and health care information systems. J Med Internet Res. 2011;13(1):e24."
        ],
        [
          "",
          "(https://doi.org/10.2196/jmir.1521)."
        ],
        [
          "",
          ""
        ],
        [
          "9.",
          "Licenses [online database]. West Hollywood: Open Source Initiative; 2024 (https://opensource.org/licenses/)."
        ],
        [
          "",
          ""
        ],
        [
          "10.",
          "Definition of “Open Standards” [website]. International Telecommunication Union; 2005 (https://www.itu.int/en/ITU-T/ipr/Pages/"
        ],
        [
          "",
          "open.aspx)."
        ],
        [
          "",
          ""
        ],
        [
          "11.",
          "Pittman PH, Atwater JB, editors. ASCM supply chain dictionary, seventeenth edition. Chicago: Association for Supply Chain"
        ],
        [
          "",
          "Management; 2022 (https://learn.ascm.org/s/ascm-dictionary)."
        ],
        [
          "",
          ""
        ],
        [
          "12.",
          "SMART guidelines [website]. World Health Organization; 2024 (https://www.who.int/teams/digital-health-and-innovation/smart-"
        ],
        [
          "",
          "guidelines)."
        ],
        [
          "",
          ""
        ],
        [
          "13.",
          "Mehl G, Tunçalp Ö, Ratanaprayul N, Tamrat T, Barreix M, Lowrance D et al. WHO SMART guidelines: optimising country-level use"
        ],
        [
          "",
          "of guideline recommendations in the digital age. Lancet Digital Health. 2021;3(4):e213–e216. (https://doi.org/10.1016/S2589-"
        ],
        [
          "",
          "7500(21)00038-8)."
        ],
        [
          "",
          ""
        ],
        [
          "14.",
          "Policy paper on traceability of medical products. Geneva: World Health Organization; 2021 (https://iris.who.int/"
        ],
        [
          "",
          "handle/10665/340237). Licence: CC BY-NC-SA 3.0 IGO."
        ],
        [
          "",
          ""
        ],
        [
          "15.",
          "Global strategy on digital health 2020–2025. Geneva: World Health Organization; 2021 (https://iris.who.int/handle/10665/344249)."
        ],
        [
          "",
          "Licence: CC BY-NC-SA 3.0 IGO."
        ],
        [
          "",
          ""
        ],
        [
          "16.",
          "Supply chain information system maturity model (SCISMM) [website]. Digital Square; 2020 (https://lib.digitalsquare.io/"
        ],
        [
          "",
          "collections/8769db8b-cc77-45fa-b1ea-f4ce5d838fde)."
        ],
        [
          "",
          ""
        ],
        [
          "17.",
          "OpenHIE: a framework based on real-world application [website]. OpenHIE, 2024 (https://ohie.org/framework/)."
        ],
        [
          "",
          ""
        ],
        [
          "18.",
          "The TOGAF® standard, tenth edition. San Francisco: The Open Group; 2022 (https://www.opengroup.org/togaf/10thedition)."
        ],
        [
          "",
          ""
        ],
        [
          "19.",
          "National eHealth strategy toolkit. Geneva: World Health Organization and International Telecommunication Union; 2012 (https://iris."
        ],
        [
          "",
          "who.int/handle/10665/75211)."
        ],
        [
          "",
          ""
        ],
        [
          "20.",
          "Digital adaptation kit for antenatal care: operational requirements for implementing WHO recommendations in digital systems."
        ],
        [
          "",
          "Geneva: WHO; 2021 (https://iris.who.int/handle/10665/339745). Licence: CC BY-NC-SA 3.0 IGO."
        ],
        [
          "",
          ""
        ],
        [
          "21.",
          "Promoting national medicines policies [website]. World Health Organization; 2024 (https://www.who.int/activities/promoting-"
        ],
        [
          "",
          "national-medicines-policies)."
        ],
        [
          "",
          ""
        ],
        [
          "22.",
          "National supply chain assessment (NSCA) toolkit. Washington (DC): USAID Global Health Supply Chain Program; 2022 (https://www."
        ],
        [
          "",
          "ghsupplychain.org/key-initiatives/national-supply-chain-assessment-nsca-toolkit)."
        ],
        [
          "",
          ""
        ],
        [
          "23.",
          "IHE Pharmacy (PHARM) white paper: supply of products for healthcare, revision 1.1. Oak Brook (IL): Integrating the Healthcare"
        ],
        [
          "",
          "Enterprise (IHE) International; 2020 (https://www.ihe.net/uploadedFiles/Documents/Pharmacy/IHE_Pharmacy_WP_Supply.pdf)."
        ],
        [
          "",
          ""
        ],
        [
          "24.",
          "The MAPS toolkit: mHealth assessment and planning for scale. Geneva: World Health Organization; 2015 (https://iris.who.int/"
        ],
        [
          "",
          "handle/10665/185238)."
        ],
        [
          "",
          ""
        ],
        [
          "25.",
          "Healthcare traceability and GS1 standards [website]. GS1; (https://www.gs1.org/industries/healthcare/traceability)."
        ],
        [
          "",
          ""
        ],
        [
          "26.",
          "Recommendations on common technical denominators for traceability systems for medicines to allow for interoperability."
        ],
        [
          "",
          "International Coalition of Medicines Regulatory Authorities (ICMRA); 2021 (https://www.icmra.info/drupal/sites/default/"
        ],
        [
          "",
          "files/2021-08/recommendations_on_common_technical_denominators_for_T&T_systems_to_allow_for_interoperability_final.pdf)."
        ]
      ],
      "narratives": {},
      "csv": "tables/table-18.csv"
    },
    {
      "label": "Table 19",
      "caption": "",
      "pages": [
        68
      ],
      "columns": [
        {
          "titles": "Bottleneck"
        },
        {
          "titles": "1. How much impact does this bottleneck have on the process? (1–3)"
        },
        {
          "titles": "2. What is the likelihood of overcoming this bottleneck? (1–3)"
        },
        {
          "titles": "3. Is this important to a wide range of stakeholders? (1–3)"
        },
        {
          "titles": "Score"
        },
        {
          "titles": "Prioritized ranking"
        }
      ],
      "rows": [
        [
          "Example: Unavailability of timely consumption data results in inaccurate forecasts and frequent stockouts.",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "Example: Aggregating data from paper forms is burdensome and rarely done correctly.",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "Example: Inability to track and trace health products using serial numbers.",
          "",
          "",
          "",
          "",
          ""
        ]
      ],
      "narratives": {},
      "csv": "tables/table-19.csv"
    },
    {
      "label": "Table 20",
      "caption": "",
      "pages": [
        70
      ],
      "columns": [
        {
          "titles": ""
        },
        {
          "titles": "MOH"
        },
        {
          "titles": "Regulatory authority"
        },
        {
          "titles": "Central warehouse"
        },
        {
          "titles": "Branch warehouse"
        },
        {
          "titles": "Service delivery point"
        },
        {
          "titles": "Community health worker"
        },
        {
          "titles": "Individuals"
        }
      ],
      "rows": [
        [
          "Forecasting and planning",
          "Planning system",
          "",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "Procurement management",
          "",
          "",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "Supplier and contract management",
          "",
          "",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "Order management",
          "",
          "",
          "OpenLMIS",
          "OpenLMIS",
          "OpenLMIS",
          "",
          ""
        ],
        [
          "Warehouse management",
          "",
          "",
          "ERP",
          "",
          "",
          "RapidSMS",
          ""
        ],
        [
          "Transportation management",
          "",
          "",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "Dispensing",
          "",
          "",
          "",
          "",
          "OpenClinic",
          "",
          ""
        ],
        [
          "Analytics",
          "Health analytics platform",
          "",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "Track and trace",
          "",
          "",
          "",
          "",
          "",
          "",
          "NPC mobile app"
        ],
        [
          "Cold chain management",
          "",
          "",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "Foundational components",
          "NPC",
          "",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "Regulatory",
          "",
          "Registration system",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "",
          "",
          "NPC mobile app",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "",
          "",
          "",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "",
          "",
          "In progress",
          "",
          "",
          "",
          "",
          ""
        ],
        [
          "",
          "",
          "Deployed",
          "",
          "",
          "",
          "",
          ""
        ]
      ],
      "narratives": {},
      "csv": "tables/table-20.csv"
    },
    {
      "label": "Table 21",
      "caption": "",
      "pages": [
        71
      ],
      "columns": [
        {
          "titles": "#"
        },
        {
          "titles": "Risk title"
        },
        {
          "titles": "Description"
        },
        {
          "titles": "Priority"
        },
        {
          "titles": "Impact"
        },
        {
          "titles": "Prob- ability"
        },
        {
          "titles": "Status"
        },
        {
          "titles": "Mitigation steps"
        },
        {
          "titles": "Owner"
        },
        {
          "titles": "Raised"
        },
        {
          "titles": "Reviewed"
        },
        {
          "titles": "Closed"
        }
      ],
      "rows": [
        [
          "",
          "",
          "",
          "Low",
          "Major",
          "Medium",
          "",
          "",
          "",
          "",
          "",
          ""
        ]
      ],
      "narratives": {},
      "csv": "tables/table-21.csv"
    },
    {
      "label": "Table 22",
      "caption": "",
      "pages": [
        72,
        73,
        74,
        75,
        76
      ],
      "columns": [
        {
          "titles": "Role category"
        },
        {
          "titles": "Role"
        },
        {
          "titles": "Phase(s) in which it is required"
        },
        {
          "titles": ""
        },
        {
          "titles": "Position type"
        },
        {
          "titles": "Skill sets"
        },
        {
          "titles": "Responsibilities"
        }
      ],
      "rows": [
        [
          "",
          "",
          "Deployment",
          "Operation",
          "",
          "",
          ""
        ],
        [
          "Leadership",
          "Chief technology officer / chief information officer / chief digital officer",
          "",
          "",
          "Permanent",
          "» Leadership skills: ability to manage multiple IT teams and provide guidance on digital initiatives » Strategy skills: ability to perform strategic planning for IT initiatives and provide oversight to ensure that strategic objectives are met » Technology skills: knowledge of the latest technologies and trends, understanding of enterprise architecture and data management » Interpersonal skills: communication and presentation skills, relationship and team development skills",
          "» Liaise with senior technical leadership across different organizations to facilitate IT work planning and budgeting » Facilitate approvals of workplans, budgets and funding requests » Develop and implement IT policies and standards » Manage multiple IT teams, including implementation teams, infrastructure personnel and IT manager » Oversee key IT initiatives and ensure successful deployments in line with strategic objectives » Lead vendor management"
        ],
        [
          "Leadership Technical",
          "IT manager",
          "",
          "",
          "Permanent",
          "» Leadership skills: ability to manage technical teams » Strategy skills: ability to support strategic planning for IT initiatives » Technology skills: knowledge of existing technologies used in country and latest trends, understanding of data management and application support needs » Interpersonal skills: communication and presentation skills, relationship and team development skills",
          "» Liaise with senior leadership to facilitate IT work planning and budgeting » Implement IT policies and standards » Manage IT personnel » Oversee day-to-day operations of IT tools » Identify IT improvement opportunities » Liaise with IT vendors when required to facilitate troubleshooting or enhancements"
        ],
        [
          "Leadership",
          "Project manager",
          "",
          "",
          "Contracted/ temporary",
          "» Understanding of business requirements and high-level IT architectures/solutions » Project management skills such as planning, budgeting, risk management, team management and time management » Experience in various project management methodologies such as agile, waterfall and software development lifecycle » Ability to coordinate with and manage multiple stakeholders » Interpersonal skills such as communication, presentation and team development",
          "» Set project objectives and charter » Develop project plan to manage resources and timeline within the allotted budget » Provide regular status updates to team and senior leadership » Identify and assess risks and develop mitigation strategies » Coordinate efforts of all team members to meet project objectives » Monitor and manage project performance and progress"
        ],
        [
          "",
          "",
          "Deployment",
          "Operation",
          "",
          "",
          ""
        ],
        [
          "Leadership Technical",
          "Solution architect",
          "",
          "",
          "Contracted/ temporary",
          "» Knowledge of various technology options and trends, such as cloud services, software as a service and open source » Experience in software design and architecture » Knowledge of IT infrastructure » Technical leadership skills such as providing technical guidance and vision » Ability to understand business requirements and map them to technology solutions » Understanding of best practices in software development, architecture and IT deployments » Analytical and problem-solving skills",
          "» Gather business requirements to define scope and develop technology solutions and architecture to satisfy requirements » Prepare technology specifications to implement, using best-practices » Analyse existing systems and identify improvements and integration requirements » Guide technical team members in implementing technology solutions » Coordinate with various technical teams such as integration specialists, infrastructure specialists and quality assurance (QA) personnel to guide them in various aspects of IT implementation » Coordinate with senior leadership to communicate about technology options, cost impact and budget needs"
        ],
        [
          "Technical",
          "Business analyst",
          "",
          "",
          "Contracted/ temporary",
          "» Analytical and problem-solving skills » Writing and communication skills » Ability to understand and gather business requirements » Knowledge of supply chain processes » Interpersonal skills such as coordination across various teams and stakeholders",
          "» Gather and analyse business requirements and map business processes » Collaborate with technical teams to translate business needs into technical requirements » Develop use cases or user stories to convey business needs to technical teams » Coordinate with QA team to ensure that test cases for validating technical solutions are developed according to business needs » Collaborate with multiple technical and business teams » Collaborate with QA and training teams to prepare test cases and training material"
        ],
        [
          "Technical",
          "Developer/ programmer",
          "",
          "",
          "Contracted/ temporary",
          "» Knowledge of and experience with programming languages such as Java, Python and C++ » Knowledge of and experience with technology options such as relational databases, web frameworks and object-oriented development » Ability to understand business requirements and develop programs to meet those requirements » Interpersonal skills such as ability to coordinate various technical and process teams » Analytical and problem-solving skills » Experience in developing software solutions using open-source tools",
          "» Design and develop software programs that meet business requirements » Deploy the developed software across multiple environments, such as test, staging and production » Troubleshoot and fix bugs in software programs » Collaborate with QA and training teams to prepare test cases and training material"
        ],
        [
          "",
          "",
          "Deployment",
          "Operation",
          "",
          "",
          ""
        ],
        [
          "Technical",
          "Integration specialist",
          "",
          "",
          "Contracted/ temporary",
          "» Knowledge of and experience with ETL (Extract, Transform and Load) tools » Knowledge of and experience with SQL » Knowledge of and experience with service-oriented architecture » Knowledge of and experience with various data transfer protocols, schemas and formats » Knowledge of available data transformation and interoperability tools and experience with at least two tools",
          "» Design integration solutions to use interoperability features across multiple systems » Develop integration standards and protocols » Coordinate with implementation team members such as architects and programmers to develop application integrations » Maintain the developed integrations and troubleshoot issues"
        ],
        [
          "Technical",
          "Database administrator",
          "",
          "",
          "Permanent",
          "» Knowledge of various database tools » Data modelling » Database management, including performance monitoring, optimizing and tuning » Database backup and recovery » Data security",
          "» Advise on relevant database tools to use » Support database activities such as data modelling, performance monitoring, data cleansing and tuning » Monitor databases to ensure timely backup and recovery when required » Ensure security of databases and administer relevant access to appropriate users » Coordinate with teams deploying various IT tools to support database activities"
        ],
        [
          "Technical",
          "Infrastructure specialist",
          "",
          "",
          "Permanent",
          "» Proficiency with network protocols such as TCP/IP, DNS, DHCP and VPN » Knowledge of firewalls, intrusion detection/prevention systems and VPNs for secure data transmission » Proficiency with Linux, Unix and Windows Server environments for installation, configuration and maintenance » Experience with virtualization platforms such as VMware, Hyper-V and KVM » Familiarity with scripting (e.g., PowerShell, Bash) to automate system tasks » Experience with cloud infrastructure services » Ability to design, implement and manage cloud-based solutions » Experience with SAN, NAS and other storage solutions » Understanding of best practices in securing systems and networks, including patch management, malware protection and secure access controls » Familiarity with regulations such as those ensuring that infrastructure complies with legal and regulatory requirements",
          "» Identify, analyse and solve complex hardware and software issues across the infrastructure » Manage network configurations, routers, switches, firewalls and load balancers and perform troubleshooting » Define backup strategies and disaster recovery plans and ensure business continuity » Optimize systems and networks for high availability and efficiency"
        ],
        [
          "",
          "",
          "Deployment",
          "Operation",
          "",
          "",
          ""
        ],
        [
          "Leadership Technical",
          "QA/test manager",
          "",
          "",
          "Contracted/ temporary",
          "» Knowledge of software implementation methodologies, including agile and waterfall » Knowledge of and experience with automated testing tools » Experience with testing large-scale IT tools, managing test teams and troubleshooting test scenarios and technical issues » Experience with testing phases such as system testing, performance testing, user acceptance testing and integration testing » Experience with test case development, test results reporting and stakeholder management » Experience with and knowledge of defect tracking tools such as JIRA",
          "» Manage testing teams to perform test scenarios such as system testing and user acceptance testing » Develop and guide the team in developing test cases and scripts based on business requirements » Develop test management plans that include resource plan, risk management, timeline and scope » Coordinate across multiple teams such as development team and infrastructure team to manage testing of IT tools at different intervals of the implementation » Monitor testing progress and provide status reports to senior leadership"
        ],
        [
          "Technical",
          "Test analyst",
          "",
          "",
          "Contracted/ temporary",
          "» Knowledge of software implementation methodologies, including agile and waterfall » Knowledge of and experience with various automated testing tools » Experience with testing large-scale IT tools and troubleshooting test scenarios and technical issues » Experience with testing phases such as system testing, performance testing, user acceptance testing and integration testing » Experience with test case development and test scripting » Experience with and knowledge of defect tracking tools such as JIRA",
          "» Develop test cases and scripts based on business requirements » Conduct testing across different phases such as system testing, performance testing and user acceptance testing, and capture test results » Coordinate across teams such as the development team and infrastructure team to manage testing of IT tools at different intervals of the implementation"
        ],
        [
          "Technical",
          "System administrator",
          "",
          "",
          "Permanent",
          "» Experience with the system, network and database administration of IT tools » Knowledge of, experience with and certifications in various operating systems » Experience with system administrative tools such as virtualization and VMware » Experience with networking (WAN/ LAN), hardware and scripting tools (e.g., Python and Perl) » Experience with and knowledge of IT helpdesk activities such as data security and user management » Troubleshooting skills",
          "» Support installation of IT tools/ software and hardware (e.g., servers) » Monitor performance of systems and ensure uptime » Manage various servers, networks and other technology tools to maintain operations of IT applications » Monitor for technical issues and troubleshoot » Ensure data security by adding/ modifying/deleting user accounts and providing users with appropriate access to data » Apply version updates, hot fixes and any other software/ hardware revisions required for all the applicable tools"
        ],
        [
          "",
          "",
          "Deployment",
          "Operation",
          "",
          "",
          ""
        ],
        [
          "Technical",
          "Support engineer",
          "",
          "",
          "Permanent or contracted/ temporary",
          "» Knowledge of and experience with supply chain software » Knowledge of networking and hardware setup » Experience with software support activities such as troubleshooting, coordinating with users and vendors, and applying fixes » Proficiency in remote setup or virtual tools to troubleshoot technical issues » Knowledge of defect tracking tools such as JIRA",
          "» Provide day-to-day support to users of software tools to troubleshoot any issues » Monitor performance of software tools and ensure uptime » Provide regular maintenance of software tools and applying version updates, hot fixes, etc. » Capture technical issues and resolutions for status reporting"
        ],
        [
          "Technical",
          "Superuser/ trainer",
          "",
          "",
          "Permanent",
          "» Knowledge of supply chain processes and features of relevant software tools » Experience using two or more supply chain software tools » Experience training end users",
          "» Train end users on various functionalities and features in supply chain software tools » Help users with system administrative activities that can be managed by end users (e.g., password change). » Perform simple and basic configuration of systems, where applicable, to enhance or add features to software tools"
        ]
      ],
      "narratives": {},
      "csv": "tables/table-22.csv"
    }
  ],
  "coverage": [
    {
      "kind": "contents",
      "state": "found",
      "count": 39,
      "note": "contents from inferred"
    },
    {
      "kind": "sections",
      "state": "found",
      "count": 40
    },
    {
      "kind": "figures",
      "state": "found",
      "count": 30,
      "note": "1 raster, 29 vector; 35 caption(s) read off the pages"
    },
    {
      "kind": "tables",
      "state": "found",
      "count": 22
    },
    {
      "kind": "references",
      "state": "found",
      "count": 29
    },
    {
      "kind": "glossary",
      "state": "found",
      "note": "candidates in glossary/9789240101197-eng.glossary.json",
      "count": 55
    },
    {
      "kind": "footnotes",
      "state": "found",
      "count": 1,
      "note": "called from the text; also kept: 9 foot-of-page line(s) no mark calls, 10 mark(s) with no note found"
    },
    {
      "kind": "summaries",
      "state": "found",
      "count": 40
    }
  ],
  "links": {
    "repo": "WorldHealthOrganization/who-iris",
    "branch": "main",
    "dir": "library/9789240101197-eng"
  }
}
