{
  "$schema": "folio-library-entry/v1",
  "id": "9789240101197-eng",
  "blocks": [
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-front-matter",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Front matter",
      "pageStart": 1,
      "pageEnd": 6,
      "target": "../sections/sec-front-matter.md",
      "narrative": null,
      "content": "Digital transformation \nhandbook for \nhealth supply chain \narchitecture\nDigital transformation \nhandbook for \nhealth supply chain \narchitecture\nDigital transformation handbook for health supply chain architecture \n(SMART Guidelines collection)\nISBN 978-92-4-010119-7 (electronic version)\nISBN 978-92-4-010120-3 (print version)\n© World Health Organization 2024\nSome rights reserved. This work is available under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 IGO \nlicence (CC BY-NC-SA 3.0 IGO; https://creativecommons.org/licenses/by-nc-sa/3.0/igo). \nUnder the terms of this licence, yo",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-000",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Acknowledgements",
      "pageStart": 6,
      "pageEnd": 7,
      "target": "../sections/sec-000-acknowledgements.md",
      "narrative": null,
      "content": "The World Health Organization (WHO) is grateful for the contributions of many individuals and organizations in the \ndevelopment of this handbook.\nThis handbook was authored by Carl Leitner and Swaroop Jayaprakash of the WHO Department of Digital Health and \nInnovations (DHI) and Ramy Guirguis of the United States Agency for International Development (USAID). The following \nindividuals (in alphabetical order) reviewed drafts of the handbook at various stages and provided feedback to the authors:\nKarthik Adapa (WHO Regional Office for South-East Asia), Peter Alvarez (GS1, United States of Americ",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-001",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Abbreviations and acronyms",
      "pageStart": 7,
      "pageEnd": 8,
      "target": "../sections/sec-001-abbreviations-and-acronyms.md",
      "narrative": null,
      "content": "DH&I WG\nDigital Health and Interoperability Working Group\nDHSC\ndigital health supply chain\nDIIG\nDigital Implementation Investment Guide\neRIS\nElectronic Regulatory Information System\nERP\nenterprise resource planning\nFTE\nfull-time equivalent\nGFPVAN \nGlobal Family Planning Visibility and Analytics Network\nGHSC-PSM\nGlobal Health Supply Chain Program–Procurement and Supply Management\nHSCIS\nhealth supply chain information system\nHTSS\nHealth Technical Support Services\nICT\ninformation and communications technology\nIT\ninformation technology\nITU\nInternational Telecommunication Union\nKPI\nkey performance",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/table-001",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 7,
      "pageEnd": 7,
      "target": "../tables/table-1.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-002",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Glossary",
      "pageStart": 8,
      "pageEnd": 11,
      "target": "../sections/sec-002-glossary.md",
      "narrative": null,
      "content": "deployment\nMaking a software system available for use beyond testing purposes.\ndigital health\nThe systematic application of information and communications technologies, computer science \nand data to support informed decision-making by individuals, the health workforce and health \nsystems, to strengthen resilience to disease and improve health and wellness (1, 2).\ndigital health supply \nchain intervention\nAn intervention that involves the use of digital technologies to improve the management \nand operation of health supply chains. It aims to enhance the efficiency and effectiveness of \nhealth s",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p011",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 11,
      "pageEnd": 11,
      "target": "../figures/vfig-p011.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-003",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Introduction",
      "pageStart": 11,
      "pageEnd": 19,
      "target": "../sections/sec-003-introduction.md",
      "narrative": null,
      "content": "for delivery to individuals, are integral to the public health care system. Supply chain processes such \nas forecasting and planning, sourcing, procurement, order management, warehouse management and \ndispensing must operate in harmony to facilitate the flow of health products from manufacturers to the \nindividuals who need them. \nBecause supply chain processes overlap with health \nprocesses that take place at the community and facility \nlevel, well designed digital health supply chain (DHSC) \narchitectures and information management approaches \nthat encompass the needs of all stakeholders are",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p012",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 12,
      "pageEnd": 12,
      "target": "../figures/vfig-p012.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p013",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 13,
      "pageEnd": 13,
      "target": "../figures/vfig-p013.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p014",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 14,
      "pageEnd": 14,
      "target": "../figures/vfig-p014.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p015",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 15,
      "pageEnd": 15,
      "target": "../figures/vfig-p015.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p016",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 16,
      "pageEnd": 16,
      "target": "../figures/vfig-p016.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p017",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 17,
      "pageEnd": 17,
      "target": "../figures/vfig-p017.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/table-002",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Fig 7. Sample workflow for an antenatal care business, with connections to the supply chain",
      "pageStart": 17,
      "pageEnd": 17,
      "target": "../tables/table-2.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-004",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Defining a holistic DHSC strategy",
      "pageStart": 19,
      "pageEnd": 20,
      "target": "../sections/sec-004-1-defining-a-holistic-dhsc-strategy.md",
      "narrative": null,
      "content": "DHSC strategy\n2. Defining the DHSC \narchitecture\nChapter\nDefining a holistic \nDHSC strategy\n3. Planning for scalable \nimplementation and \nsustainable operations\n4. Using the DHSC to \nimplement traceability\nIdentify and engage \nstakeholders\nAnalyse the current \nstate of HSCISs\nDefine the vision and \nstrategic goals and \nobjectives\nDefine a strategic \nroadmap and \nperformance \nindicators\n2\nStep\nStep\nStep\nStep\n3\n4\n1\nThe following principles, informed by the Principles for Digital \nDevelopment (Annex 1), can guide the development of the DHSC vision and \nstrategic goals.\n\t\n→Align with a relevant na",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p020",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 20,
      "pageEnd": 20,
      "target": "../figures/vfig-p020.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-005",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Why is a strategy necessary?",
      "pageStart": 20,
      "pageEnd": 22,
      "target": "../sections/sec-005-why-is-a-strategy-necessary.md",
      "narrative": null,
      "content": "A holistic DHSC strategy is essential to achieving \ncomprehensive digital transformation of the health supply \nchain. It can offer a clear vision and direction and ensure \nalignment across all national digital transformation \ninitiatives (Fig. 8) (21). Such initiatives may include the \nfollowing:\n\t\n→national health strategy, which establishes a vision \nand priorities to address the most pressing health \ncare challenges and improve health care for the \npopulation; \n\t\n→national medicines and health product policies, which \naim to increase access to and use of high-quality, \naffordable medicines",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p021",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 21,
      "pageEnd": 21,
      "target": "../figures/vfig-p021.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-006",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 1. Identify and engage all relevant stakeholders",
      "pageStart": 22,
      "pageEnd": 23,
      "target": "../sections/sec-006-step-1-identify-and-engage-all-relevant-stakehol.md",
      "narrative": null,
      "content": "1\nStep\nIdentifying and engaging all relevant stakeholders involves recognizing everyone who has an \ninterest or role in the DHSC implementation and actively involving them in the process. This \nensures that diverse perspectives are considered, fosters collaboration and gains support for \nsuccessful DHSC outcomes.\nINPUTS\nTASKS\nOUTPUTS\n\t» National health strategy \n1.\t Identify focal points from all stakeholder \norganizations (including the MOH, \nregulatory authority, IT authority, \ncentral and regional warehouses, health \nfacilities, implementation partners and \nfunders) whose input will be vita",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/table-003",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 22,
      "pageEnd": 22,
      "target": "../tables/table-3.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-007",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 2. Analyse the current state of HSCISs",
      "pageStart": 23,
      "pageEnd": 24,
      "target": "../sections/sec-007-step-2-analyse-the-current-state-of-hsciss.md",
      "narrative": null,
      "content": "2\nStep\nBEST PRACTICE\n\t\nÐ To ensure a comprehensive assessment of the current health supply chain, consider all factors that affect \nthe health supply chain, such as stakeholders, human resource capacity, infrastructure, political priorities, \ntechnology maturity and maturity of processes (including regulatory and insurance).\nPotential risks\nMitigation strategies\nMisalignment of technical and political \npriorities\n\t»\nEstablish connections between political and technical priorities by identifying the mutual benefits \nof pursuing technical priorities.\n\t»\nPromote engagement and dialogue between te",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/table-004",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 23,
      "pageEnd": 23,
      "target": "../tables/table-4.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-008",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 3. Define the DHSC vision and strategic goals and objectives",
      "pageStart": 24,
      "pageEnd": 25,
      "target": "../sections/sec-008-step-3-define-the-dhsc-vision-and-strategic-goal.md",
      "narrative": null,
      "content": "3\nStep\nThe DHSC vision provides a guiding beacon by summarizing the ideal future state of health \nsupply chain digitalization and how to achieve it. Strategic goals guide the country’s actions and \ndecisions to achieve the vision. They translate to strategic objectives that are specific, measurable, \nachievable, relevant and time-bound. The goals should link to the DHSC implementation activities.\nINPUTS\nTASKS\nOUTPUTS\n\t» National supply chain \nstrategy \n\t» National health strategy\n\t» National digital health \n2.\t Define realistic strategic goals that will help \nachieve the identified solutions w",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/table-005",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 24,
      "pageEnd": 24,
      "target": "../tables/table-5.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-009",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 4. Define a strategic roadmap and performance indicators",
      "pageStart": 25,
      "pageEnd": 27,
      "target": "../sections/sec-009-step-4-define-a-strategic-roadmap-and-performanc.md",
      "narrative": null,
      "content": "4\nStep\nA strategic roadmap for DHSC sets out timelines and milestones for achieving goals related to \ndigitalizing the health supply chain. It serves as a guiding framework for the country, helping it stay \nfocused on strategic objectives, allocate resources efficiently and track progress effectively.\nINPUTS\nTASKS\nOUTPUTS\n\t» DHSC strategic goals \n\t» DHSC strategic objectives\n\t» Timelines of other \n1.\t Define a strategic roadmap that outlines \nthe high-level timeline for achieving the \nstrategic goals and objectives.\n2.\t Define performance indicators for all \nstrategic objectives, to measure pr",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/table-006",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 25,
      "pageEnd": 25,
      "target": "../tables/table-6.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p026",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 26,
      "pageEnd": 26,
      "target": "../figures/vfig-p026.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/table-007",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Fig 10. Example of outputs from this chapter",
      "pageStart": 26,
      "pageEnd": 26,
      "target": "../tables/table-7.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-010",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Defining the DHSC architecture",
      "pageStart": 27,
      "pageEnd": 28,
      "target": "../sections/sec-010-2-defining-the-dhsc-architecture.md",
      "narrative": null,
      "content": "architecture\nDefining the \nDHSC architecture\n3. Planning for scalable \nimplementation and \nsustainable operations\n4. Using the DHSC to \nimplement traceability\nAssess the current \nstate of HSCISs\nDefine a target \narchitecture\nIdentify \nimplementation \nactivities and map \nthem to strategic \ngoals\n2\n1\nStep\nStep\nStep\n3\nChapter2\nThe following principles, informed by the Principles for Digital Development \n(Annex 1), can guide the development of the DHSC architecture.\n\t\n→Engage key stakeholders throughout the process to gain buy-in, \nunderstand diverse perspectives and ensure that activities meet th",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-011",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Is a DHSC architecture necessary?",
      "pageStart": 28,
      "pageEnd": 28,
      "target": "../sections/sec-011-is-a-dhsc-architecture-necessary.md",
      "narrative": null,
      "content": "The health supply chain comprises several business \nprocesses that ensure the availability of health products \nto individuals. Forecasting and supply planning processes \nensure adequate supply to meet demand. Procurement and \ndistribution processes ensure that medicines and health \nproducts are sourced and delivered to the right locations \nand are available to individuals when needed. Warehouse \nmanagement processes support receiving, storage and \nmanagement of inventory. \nHealth supply chains should be able to quickly respond to \nexceptions such as stockouts and quality issues like product \nr",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-012",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "What are the risks of forgoing a DHSC architecture?",
      "pageStart": 28,
      "pageEnd": 30,
      "target": "../sections/sec-012-what-are-the-risks-of-forgoing-a-dhsc-architectu.md",
      "narrative": null,
      "content": "The lack of an overarching DHSC architecture leads to risks \nsuch as those listed below:\n\t\n→siloed and duplicative systems that lack the ability to \nadapt and scale, requiring more effort and money to \nmaintain and sustain;\n\t\n→lack of compliance with global and open standards, \nresulting in a lack of interoperability among processes, \nsystems and data, which in turn, affects the timely \navailability of aggregated data for visibility, analysis, \nexception management, reporting and decision-\nmaking;\n\t\n→laborious manual processes for aggregating, \nreconciling and triangulating data for accurate",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p029",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 29,
      "pageEnd": 29,
      "target": "../figures/vfig-p029.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-013",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 1. Assess the current state of HSCISs",
      "pageStart": 30,
      "pageEnd": 32,
      "target": "../sections/sec-013-step-1-assess-the-current-state-of-hsciss.md",
      "narrative": null,
      "content": "1\nStep\nAssessing the current state of HSCISs involves a thorough evaluation of their capabilities, \nutilization, technical challenges and overall system maturity. This step helps identify strengths, \ngaps, inefficiencies and areas for improvement in existing systems that can be duly considered \nwhile defining the architecture.\nINPUTS\nTASKS\nOUTPUTS\n\t» NSCA outcomes (if \navailable) \n\t» SCISMM assessment \noutcomes (if available)\n\t» DHSC strategic goals and \nobjectives\n\t» National digital health \nstrategy\n\t» Landscape analysis of \nexisting hardware, current \nstate of infrastructure \n(electricity,",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/table-008",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 30,
      "pageEnd": 30,
      "target": "../tables/table-8.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p031",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 31,
      "pageEnd": 31,
      "target": "../figures/vfig-p031.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/table-009",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Fig 12. SCISMM maturity levels for HSCISs",
      "pageStart": 31,
      "pageEnd": 31,
      "target": "../tables/table-9.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-014",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "DHSC architecture framework",
      "pageStart": 32,
      "pageEnd": 32,
      "target": "../sections/sec-014-dhsc-architecture-framework.md",
      "narrative": null,
      "content": "The DIIG outlines the components of a digital health \nenterprise architecture (Fig. 13). DHSC architectural \ncomponents relate to the business domain services within \nthis architecture. \nFig. 14 shows a DHSC architecture framework with \ncomponents that support services such as foundational \nservices, supply chain functional services, analytics, \ninteroperability and traceability. This framework is based on \nthe guiding principles of TOGAF and the OpenHIE framework.",
      "truncated": false,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-015",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 2. Define a target DHSC architecture",
      "pageStart": 32,
      "pageEnd": 35,
      "target": "../sections/sec-015-step-2-define-a-target-dhsc-architecture.md",
      "narrative": null,
      "content": "2\nStep\nThis step involves defining a target DHSC architecture to ensure that all of the HSCISs are optimally \nstructured and aligned with strategic goals.\nINPUTS\nTASKS\nOUTPUTS\n\t» Assessment of the \nsupply chain to identify \nopportunities for digital \ntransformation\n\t» List of existing HSCISs\n\t» SCISMM assessment \nreport\n\t» HSCIS gaps that need to \nbe addressed to achieve \nthe DHSC strategic goals\n1.\t Draw the current-state architecture of \nthe HSCISs by mapping existing systems \nagainst the DHSC architecture framework.\n2.\t Identify gaps and necessary digital \ninterventions based on the current",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/table-010",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 32,
      "pageEnd": 32,
      "target": "../tables/table-10.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p033",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 33,
      "pageEnd": 33,
      "target": "../figures/vfig-p033.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p034",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 34,
      "pageEnd": 34,
      "target": "../figures/vfig-p034.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-016",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Illustrative architectural approaches and governance options",
      "pageStart": 35,
      "pageEnd": 42,
      "target": "../sections/sec-016-illustrative-architectural-approaches-and-govern.md",
      "narrative": null,
      "content": "Countries often have a mixture of needs and capabilities \nthat should be reflected in their DHSC architecture. They \ncan adopt an architecture framework using an approach \nthat aligns with their supply chain design and level of digital \nmaturity. This section provides examples of architectures \nthat are based on digital maturity and examples based on \nsupply chain design (with different governance options). \nIn practice, however, both factors will help determine the \nappropriate architecture framework.\nThe examples based on digital maturity use the SCISMM \nmaturity levels. Levels 1 and 2 invol",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p036",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 36,
      "pageEnd": 36,
      "target": "../figures/vfig-p036.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p037",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 37,
      "pageEnd": 37,
      "target": "../figures/vfig-p037.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p038",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 38,
      "pageEnd": 38,
      "target": "../figures/vfig-p038.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p039",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 39,
      "pageEnd": 39,
      "target": "../figures/vfig-p039.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p040",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 40,
      "pageEnd": 40,
      "target": "../figures/vfig-p040.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p041",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 41,
      "pageEnd": 41,
      "target": "../figures/vfig-p041.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-017",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 3. Identify implementation activities and map them to strategic goals",
      "pageStart": 42,
      "pageEnd": 44,
      "target": "../sections/sec-017-step-3-identify-implementation-activities-and-ma.md",
      "narrative": null,
      "content": "3\nStep\nThis step focuses on translating the identified DHSC architectural interventions into \nimplementation activities. The activities will be mapped out on a timeline to prepare a roadmap \nfor overall implementation.\nPotential risks\nMitigation strategies\nActivities are not aligned with DHSC \nstrategic goals\nIdentify and plan implementation activities after the vision, strategy and architecture have been \ndeveloped and approved. Review any ongoing activities and adjust them to ensure alignment with \nDHSC goals and priorities.\nINPUTS\nTASKS\nOUTPUTS\n\t» Current state of HSCISs \n\t» Future-state DH",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/table-011",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 42,
      "pageEnd": 42,
      "target": "../tables/table-11.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-img-p043-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 43,
      "pageEnd": 43,
      "target": "../images/img-p043-1.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p043",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 43,
      "pageEnd": 43,
      "target": "../figures/vfig-p043.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/table-012",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 43,
      "pageEnd": 43,
      "target": "../tables/table-12.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-018",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Planning for scalable implementation and sustainable operations",
      "pageStart": 44,
      "pageEnd": 47,
      "target": "../sections/sec-018-3-planning-for-scalable-implementation-and-susta.md",
      "narrative": null,
      "content": "implementation and \nsustainable operations \nPlan the \nimplementation of \neach intervention\nDevelop an operational \nplan for \neach intervention\nDevelop a budget for \neach intervention\nImplement each \nintervention\n2\n1\nStep\nStep\nStep\nStep\n3\n4\nThe following principles, informed by the Principles \nfor Digital Development (Annex 1), can guide the \nimplementation of the DHSC interventions.\n\t\n→Plan for sustainability from the start.\n\t\n→Engage local resources to build capacity.\n\t\n→Promote collaboration across implementation \npartners to align and complement efforts.\n\t\n→Develop plans grounded in the loc",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p045",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 45,
      "pageEnd": 45,
      "target": "../figures/vfig-p045.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/table-013",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 2 provides illustrative considerations for each building block to help ensure successful DHSC implementation.",
      "pageStart": 45,
      "pageEnd": 45,
      "target": "../tables/table-13.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/table-014",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 2. Illustrative implementation considerations for the DHSC",
      "pageStart": 46,
      "pageEnd": 46,
      "target": "../tables/table-14.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-019",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 1. Plan the implementation of each DHSC intervention",
      "pageStart": 47,
      "pageEnd": 48,
      "target": "../sections/sec-019-step-1-plan-the-implementation-of-each-dhsc-inte.md",
      "narrative": null,
      "content": "1\nStep\nThis step focuses on developing a comprehensive plan, which is essential for guiding various DHSC \nimplementation activities.\nINPUTS\nTASKS\nOUTPUTS\n\t» Prioritized DHSC \n1.\t Develop a project charter.\ninterventions\n\t» List of DHSC \n2.\t Develop a project management plan.\n3.\t Establish a project governance and \nreporting mechanism through the \nsteering committee and/or TWG.\nimplementation activities\n4.\t Define the project performance \nmonitoring and analysis framework.\n\t» Project charter\n\t» Project management plan\n\t» Steering committee and TWG \nterms of reference\n\t» Project performance \nmon",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-020",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 2. Develop an operational plan for each DHSC intervention",
      "pageStart": 48,
      "pageEnd": 49,
      "target": "../sections/sec-020-step-2-develop-an-operational-plan-for-each-dhsc.md",
      "narrative": null,
      "content": "2\nStep\nThe operational plan should determine the necessary resources and the effort needed to \neffectively maintain and run the DHSC systems.\nINPUTS\nTASKS\nOUTPUTS\n\t» List of DHSC \n1.\t Update the stakeholder matrix, if required, \nto establish the system owner/custodian \nand system users.\nimplementation activities\n\t» DHSC stakeholder matrix\n2.\t Identify required operational resources \n(such as maintenance personnel, \nhardware, network infrastructure and \nbackup power).\n3.\t Develop an operations and sustainability \nplan.\n4.\t Develop an operational performance \nmonitoring and evaluation framework.",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p049",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 49,
      "pageEnd": 49,
      "target": "../figures/vfig-p049.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-021",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 3. Develop a budget for each DHSC intervention",
      "pageStart": 49,
      "pageEnd": 51,
      "target": "../sections/sec-021-step-3-develop-a-budget-for-each-dhsc-interventi.md",
      "narrative": null,
      "content": "3\nStep\nThis step helps prepare the budget based on costs to implement as well as costs to scale and \noperate DHSC systems.\nONGOING\nManagement\nGovernance\nOverhead\nIMPLEMENT\nSCALE\nOPERATE\nSourcing \n(RFP, RFI, RFQ)\nHardware and \ninfrastructure\nSoftware\nDesign and \ndevelopment\nIntegration and \ninteroperability\nTesting and training\nDeployment\nExpansion of \ndeployment\nTraining\nHardware and \ninfrastructure\nSoftware (subscriptions)\nMaintenance \n(personnel, software, hardware)\nOngoing \ntraining\nMonitoring and \nevaluation\nTotal cost of ownership\nFig. \n23\nFig. 23 illustrates the costs to consider as part",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/table-015",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 3. Illustrative cost drivers of DHSC implementation",
      "pageStart": 50,
      "pageEnd": 50,
      "target": "../tables/table-15.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-022",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 4. Implement each DHSC intervention",
      "pageStart": 51,
      "pageEnd": 53,
      "target": "../sections/sec-022-step-4-implement-each-dhsc-intervention.md",
      "narrative": null,
      "content": "4\nStep\nThis step encompasses several tasks needed to implement the identified DHSC interventions, \nincluding vendor selection, system design, development, validation and training.\nINPUTS\nTASKS\nOUTPUTS\n\t» Prioritized DHSC \ninterventions\n\t» List of DHSC \nimplementation activities\n1.\t Define functional and nonfunctional \nrequirements for the DHSC intervention \nbeing implemented.\n2.\t Identify the implementation partner/\nvendor through appropriate sourcing \nmechanisms, such as requests for \nproposal (RFPs) and requests for \nquotation (RFQs).\n3.\t Develop the intervention’s solution \ndesign and integ",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/table-016",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 51,
      "pageEnd": 52,
      "target": "../tables/table-16.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-023",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Using the DHSC to implement traceability",
      "pageStart": 53,
      "pageEnd": 54,
      "target": "../sections/sec-023-4-using-the-dhsc-to-implement-traceability.md",
      "narrative": null,
      "content": "Using the DHSC to implement traceability\nOne key benefit of the DHSC architecture is the ability to track, trace and verify health products. \nTraceability of health products is important to mitigate the risk of falsified medicines and ensure patient \nsafety and quality health care. This chapter explores the use of the DHSC architecture framework \nto implement and institutionalize traceability, which requires efforts across multiple areas such as \nregulatory, human resources and processes such as procurement and customs. The chapter focuses \nmainly on deploying technologies that use the DHSC ar",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-024",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "What is traceability?",
      "pageStart": 54,
      "pageEnd": 54,
      "target": "../sections/sec-024-what-is-traceability.md",
      "narrative": null,
      "content": "The global standards organization GS1 describes traceability \nas the ability “to see the movement of health products across \nthe supply chain” (25). Traceability means being able to trace \nthe path of health care products from the manufacturer \nto individuals, identifying ownership changes at different \npoints along the supply chain. Traceability also aids in the \nwhereabouts of products at any given moment, including \ntheir intended route towards the point of dispensing.",
      "truncated": false,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-025",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Why is traceability important?",
      "pageStart": 54,
      "pageEnd": 54,
      "target": "../sections/sec-025-why-is-traceability-important.md",
      "narrative": null,
      "content": "Tracing and tracking enhance the efficiency and integrity \nof the health supply chain. By providing global visibility \ninto every change of product ownership along the supply \nchain, traceability helps identify falsified health products \nand prevents their dispensation to individuals (among other \nbenefits, which include efficiencies in inventory management \nand prevention of medicine shortages), ultimately helping to \nensure patient safety. Traceability thus plays an important \nrole in ensuring quality health care for individuals.\nTraceability also supports the ability to manage product \nreca",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-026",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Traceability models",
      "pageStart": 54,
      "pageEnd": 57,
      "target": "../sections/sec-026-traceability-models.md",
      "narrative": null,
      "content": "The three main models for implementing traceability are the \ncentralized, semi-centralized and distributed models. They \ndiffer mostly in how they store the data and share them with \nthe relevant health authority and across actors in the supply \nchain. The centralized model involves a single database \nor repository for storing all traceability data. In a semi-\ncentralized model, the traceability data are spread across \nmultiple databases or repositories. In the distributed model, \ntraceability data are maintained separately by each supply \nchain partner. \nThis handbook does not recommend a par",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p055",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 55,
      "pageEnd": 55,
      "target": "../figures/vfig-p055.png",
      "narrative": "draft",
      "content": "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).",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p056",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 56,
      "pageEnd": 56,
      "target": "../figures/vfig-p056.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-027",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Country examples",
      "pageStart": 57,
      "pageEnd": 58,
      "target": "../sections/sec-027-5-country-examples.md",
      "narrative": null,
      "content": "Ethiopia\nMalawi\nRwanda",
      "truncated": false,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-028",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Ethiopia’s DHSC initiative",
      "pageStart": 58,
      "pageEnd": 60,
      "target": "../sections/sec-028-ethiopias-dhsc-initiative.md",
      "narrative": null,
      "content": "Status \nThe Government of Ethiopia issued its Information \nRevolution Roadmap in April 2016, which recognized digital \nhealth projects as major transformational tools. Under MOH \nleadership, it subsequently issued an eHealth Architecture \n(January 2018), strategy (2020) and blueprint (August \n2021). The eHealth Architecture created a foundational \nframework for health information systems to interact and \nfor proper management of systems and coordination of \nstakeholders. Digitization of the supply chain is part of the \neHealth Architecture and aligns with the Digital Ethiopia \n2025 initiative,",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p059",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 59,
      "pageEnd": 59,
      "target": "../figures/vfig-p059.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-029",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Malawi’s DHSC initiative",
      "pageStart": 60,
      "pageEnd": 63,
      "target": "../sections/sec-029-malawis-dhsc-initiative.md",
      "narrative": null,
      "content": "Status \nThe country’s Supply Chain Systems Architecture (SCSA) was \ncollaboratively developed in 2021 under the leadership of \nthe Health Technical Support Services (HTSS) division of the \nMOH. It was approved by the deputy minister of health in \nSeptember 2022. \nProcess \nThe SCSA was developed with support from the USAID \nGHSC-PSM and was informed by a SCISMM assessment and \nan October 2021 workshop that was held to help shape \nthe vision, strategy and architecture for Malawi’s HSCISs. \nThe workshop included stakeholders such as the MOH, the \nCentral Medical Stores Trust, the Digital Health D",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p061",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 61,
      "pageEnd": 61,
      "target": "../figures/vfig-p061.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p062",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 62,
      "pageEnd": 62,
      "target": "../figures/vfig-p062.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/table-017",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 62,
      "pageEnd": 62,
      "target": "../tables/table-17.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-030",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Rwanda’s DHSC initiative",
      "pageStart": 63,
      "pageEnd": 65,
      "target": "../sections/sec-030-rwandas-dhsc-initiative.md",
      "narrative": null,
      "content": "Status \nRwanda’s Digital Supply Chain (DSC) Strategy and \nArchitecture was collaboratively drafted in 2022 under the \nleadership of the MOH’s Chief Digital Office. It is currently \nbeing aligned with and incorporated into the country’s \noverall digital health strategy. \nProcess \nThe DSC Strategy and Architecture was developed with \nsupport from USAID through its GHSC-PSM project and \nwas informed by the results of a SCISMM assessment. \nA collaborative workshop with all key stakeholders was \nconducted in February 2022 to help shape the vision, strategy \nand architecture for the country’s HSCISs",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/figure-vfig-p064",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 64,
      "pageEnd": 64,
      "target": "../figures/vfig-p064.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-031",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "References",
      "pageStart": 65,
      "pageEnd": 66,
      "target": "../sections/sec-031-references.md",
      "narrative": null,
      "content": "2\t All linked references were accessed on 15 October 2024.\nReferences\n1.\t\nDigital implementation investment guide (DIIG): integrating digital interventions into health programmes. Geneva: World Health \nOrganization; 2020 (https://iris.who.int/handle/10665/334306). Licence: CC BY-NC-SA 3.0 IGO.\n2.\t\nDigital Health & Interoperability Working Group [website]. Digital Square; 2024 (https://wiki.digitalsquare.io/index.php/Digital_\nHealth_%26_Interoperability_Working_Group).\n3. \t\nThe differences between digitization, digitalization, and digital transformation in manufacturing [website]. Yokogawa Elec",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/table-018",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 65,
      "pageEnd": 65,
      "target": "../tables/table-18.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-032",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Principles for digital development",
      "pageStart": 66,
      "pageEnd": 67,
      "target": "../sections/sec-032-annex-1-principles-for-digital-development.md",
      "narrative": null,
      "content": "Understand the existing \necosystem\nTrust starts with a thorough understanding of the dynamic \ncultural, social and economic context in which you are operating. \nShare, reuse, and improve \nBuild on what works, improve what works, and share so that \nothers can do the same.\nDesign with people\nGood design starts and ends with people that will manage, use, \nand ideally benefit from a given digital initiative.\nDesign for inclusion  \nConsider the full range of human diversity to maximize impact \nand mitigate harm. \nBuild for sustainability\nBuild for the long-term by intentionally addressing financial",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-033",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Steering committee example structure",
      "pageStart": 67,
      "pageEnd": 68,
      "target": "../sections/sec-033-annex-2-steering-committee-example-structure.md",
      "narrative": null,
      "content": "The following diagram illustrates an example organizational structure of a DHSC steering committee. \nExecutive chairperson \nMOH\nSecretariat\nInformation \ntechnology \nauthority\nFunders\nCentral \nwarehouse\nImplementing \npartners\nOthers\nOthers \n(academia, etc.)\nRegulatory\nPrivate sector\nData\nProcess\nTechnology\nRisk\nData needs \nidentification\nProcess \nformulation and \nreviews\nEnterprise \narchitecture \nreviews\nRisk \nmanagement\nData quality \nreviews \nRegulatory \ncompliance\nDigitalization \npolicies\nRisk \nidentification and \nmitigation\nData exchange \npolicies\nProcess \nimprovements\nTechnology \naudits\nRis",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-034",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Template for prioritizing DHSC challenges to address",
      "pageStart": 68,
      "pageEnd": 69,
      "target": "../sections/sec-034-annex-3-template-for-prioritizing-dhsc-challenge.md",
      "narrative": null,
      "content": "address\nThe following table offers some considerations for ranking supply chain challenges and bottlenecks. It can be useful in guiding \ndiscussion and reaching consensus among stakeholders. The table describes three hypothetical examples of bottlenecks, \nwhich receive scores of Low (1), Medium (2) or High (3) based on responses to three questions. Adding the scores yields the \nprioritized ranking.\nBottleneck \n1. How much \nimpact does this \nbottleneck have \non the process? \n(1–3) \n2. What is the \nlikelihood of \novercoming this \nbottleneck? \n(1–3) \n3. Is this \nimportant to a \nwide range of \nsta",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/table-019",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 68,
      "pageEnd": 68,
      "target": "../tables/table-19.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-035",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Illustrative template that maps today’s challenges to future outcomes",
      "pageStart": 69,
      "pageEnd": 70,
      "target": "../sections/sec-035-annex-4-illustrative-template-that-maps-todays-c.md",
      "narrative": null,
      "content": "challenges to future outcomes\nThis type of template can be used to map the transition from current critical challenges faced by supply chain partners and \ntheir processes to the future vision of a DHSC.\nUnavailability \nof \nconsumption \ndata affects \navailability of \nmedicines to \npatients\nAvailability \nof timely  \nconsumption \ndata increases \nforecasting \naccuracy, \nensuring \navailability of \nmedicines\n20% \nError\nStock expiries \nand wastages \nper month\nSeamless data \nexchange and \nmonitoring \nacross systems \nhelp optimize \ndistribution \nand minimize \nwastages\n15%\nHealth care \nworkers \nburdened",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-036",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Template for listing health supply chain information systems",
      "pageStart": 70,
      "pageEnd": 71,
      "target": "../sections/sec-036-annex-5-template-for-listing-health-supply-chain.md",
      "narrative": null,
      "content": "information systems\nThe following table is a template for assessing the current landscape of HSCISs and identifying systems and gaps.\n \nMOH\nRegulatory \nauthority\nCentral \nwarehouse\nBranch \nwarehouse\nService \ndelivery \npoint\nCommunity \nhealth \nworker\nIndividuals\nForecasting and \nplanning\nPlanning \nsystem\n \n \nProcurement \nmanagement\n \n \n \nSupplier \nand contract \nmanagement\n \n \n \nOrder \nmanagement\n \n \nOpenLMIS\nOpenLMIS\nOpenLMIS\nWarehouse \nmanagement\n \n \nERP\nRapidSMS\nTransportation \nmanagement\n \n \n \nDispensing\n \n \n \nOpenClinic\nAnalytics\nHealth analytics \nplatform\n \n \nTrack and trace\n \n \n \nNPC mobi",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/table-020",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 70,
      "pageEnd": 70,
      "target": "../tables/table-20.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-037",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Risk register template",
      "pageStart": 71,
      "pageEnd": 72,
      "target": "../sections/sec-037-annex-6-risk-register-template.md",
      "narrative": null,
      "content": "The following table is a template for ranking risks and identifying mitigation steps.\n#\nRisk title Description\nPriority\nImpact\nProb-\nability\nStatus\nMitigation \nsteps\nOwner Raised\nReviewed\nClosed\n001\nInadequate \ntraining\nIF system \ntraining is not \ndelivered with \nappropriate \ncontent for the \naudience,\nTHEN the \nadoption and \nuse of the \nsystem may fail.\nLow\nMajor\nMedium\nMitigate\n\t»\nPerform \na skills \nassessment \nfor each \nuser before \ncompleting \nthe training \nplan.\n\t»\nComplete \na training \nneeds \nassessment \nbefore \nconducting \ntraining.\n\t»\nTarget \nand adapt \ntraining to \nmeet the \nneeds of",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/table-021",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 71,
      "pageEnd": 71,
      "target": "../tables/table-21.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240101197-eng/blocks/prose-sec-038",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Resource matrix for DHSC implementation",
      "pageStart": 72,
      "pageEnd": 78,
      "target": "../sections/sec-038-annex-7-resource-matrix-for-dhsc-implementation.md",
      "narrative": null,
      "content": "The table below illustrates the technical roles needed for DHSC implementation. The following resources on human resource \nplanning for health supply chain digital transformation can also be helpful:\n\t\n→\nPeople that Deliver (PtD): Building human resources for supply chain management theory of change (1)\n\t\n→\nPeople that Deliver: Supply chain management professionalisation framework (2) and\n\t\n→\nPeople that Deliver: PtD outsourcing toolkit (3).\nRole \ncategory\nRole\nPhase(s) in which it is \nrequired \nPosition \ntype\nSkill sets\nResponsibilities\nDeployment\nOperation\nLeadership\nChief \ntechnology \noffic",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240101197-eng/blocks/table-022",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 72,
      "pageEnd": 76,
      "target": "../tables/table-22.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    }
  ]
}
