{
  "$schema": "folio-library-entry/v1",
  "id": "9789240116191-eng",
  "blocks": [
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-front-matter",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Front matter",
      "pageStart": 1,
      "pageEnd": 5,
      "target": "../sections/sec-front-matter.md",
      "narrative": null,
      "content": "Digital transformation \nhandbook for health \nproduct catalogue \nDigital transformation \nhandbook for health \nproduct catalogue \nDigital transformation handbook for health product catalogue\nISBN 978-92-4-011619-1 (electronic version)\nISBN 978-92-4-011620-7 (print version)\n© World Health Organization 2025\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, you may copy, redistribute and adapt the work for non-co",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Front matter of the Digital transformation handbook for health product catalogue (WHO, 2025), giving the electronic and print ISBNs, the CC BY-NC-SA 3.0 IGO licence terms, suggested citation, WHO disclaimers, design credit, and a table of contents listing the acknowledgements, abbreviations, glossary, introduction, eight chapters, references and annexes.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-000",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Acknowledgements",
      "pageStart": 5,
      "pageEnd": 6,
      "target": "../sections/sec-000-acknowledgements.md",
      "narrative": null,
      "content": "Acknowledgements\nThe World Health Organization (WHO) is grateful for the \ncontributions of many individuals and organizations in \nthe development of this handbook.\nThis handbook was authored by Carl Leitner and Swaroop \nJayaprakash of the WHO Department of Digital Health and \nInnovations (DHI) and Ramy Guirguis of the United States \nAgency for International Development (USAID). The \nfollowing individuals (in alphabetical order) reviewed drafts \nof the handbook at various stages and provided feedback \nto the authors:\nVictor Adebayo (Catholic Relief Services, United States of \nAmerica [USA]), Sa",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Acknowledgements naming Carl Leitner and Swaroop Jayaprakash of the WHO Department of Digital Health and Innovations and Ramy Guirguis of USAID as authors, listing the reviewers and their organizations in alphabetical order, noting that no conflicts of interest were identified from the WHO Declaration of Interests forms, and stating that USAID funded the work, with all US inputs preceding 20 January 2025.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-001",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Abbreviations",
      "pageStart": 6,
      "pageEnd": 8,
      "target": "../sections/sec-001-abbreviations.md",
      "narrative": null,
      "content": "Abbreviations\nAEFI\nAdverse effects following immunisation\nAIDC\nAutomatic identification and data capture\nATC\nAnatomical therapeutic chemical classification system\nDAK\nDigital adaptation kit\nDH&I\nDigital health and interoperability\nDHSC\nDigital health supply chain\nDIIG\nDigital implementation investment guide\neLMIS\nElectronic logistic management information system\nFDA\nFood and Drugs Authority\nFHIR\nFast Healthcare Interoperability Resources®\nGDSN\nGlobal Data Synchronisation Network\nGTIN\nGlobal trade item number\nHL7\nHealth Level Seven®\nICD-11\nInternational classification of diseases, 11th Revision",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "List of abbreviations used in the handbook, expanding terms such as AIDC, ATC, DAK, DIIG, eLMIS, FHIR, GDSN, GTIN, IDMP, INN, NPC, NRA, PCMT, SCISMM, SMART, SOP, UMC, WHODrug, ZAMMSA and ZAMRA.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-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/9789240116191-eng/blocks/prose-sec-002",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Glossary",
      "pageStart": 8,
      "pageEnd": 10,
      "target": "../sections/sec-002-glossary.md",
      "narrative": null,
      "content": "Glossary\nData element\nA unit of data that has a specific and precise meaning.\nDigitization\nThe process of converting and organizing data from paper records into a digital format for easier \nentry, storage and retrieval. Digitization is the initial step towards digital transformation.1, 2\nDigitalization\nThe process of digitally automating and simplifying processes to streamline individual health \nprogrammes and reducing manual efforts for greater efficiency. Digitalization is the second \nstep towards digital transformation.3, 4  \nDigital transformation\nThe process of digitally optimizing and dr",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Glossary defining terms such as data element, digitization, digitalization, digital transformation, functional and non-functional requirements, generic product, interoperability, open source, open standards, organogram, registry, SMART Guidelines, trade item and user acceptance testing (UAT).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/figure-vfig-p010",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 10,
      "pageEnd": 10,
      "target": "../figures/vfig-p010.png",
      "narrative": "draft",
      "content": "Fig. 1, 'Product master data'. A health product, drawn as a boxed medicine package, is linked to PRODUCT MASTER DATA, shown as four categories with examples. General Information: product identifier, name, description, unit of measure. Classification: ICD, ATC, product characteristics/specifications. Pharmaceutical Information: dosage, strength, route of administration, doses per vial. Logistical Information: packaging, volumetrics, shelf life, storage temperature.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-003",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Introduction",
      "pageStart": 10,
      "pageEnd": 20,
      "target": "../sections/sec-003-introduction.md",
      "narrative": null,
      "content": "Health products pass through multiple supply chain \npartners and processes as they move from manufacturers to \nend-users. For transactions to be seamless, all stakeholders \nmust consistently identify health products using \nstandardized information.\nFor example, if a country’s central warehouse receives a \nshipment of vaccines with identifiers that do not match its \nstandardized data, manual reconciliation will be required. \nThis can lead to delays, errors, and distribution disruptions, \nultimately impacting health outcomes.\nUniform and standardized product information builds trust \namong suppl",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Introduction explaining product master data versus transactional data and why consistent product identification matters across supply chain partners, then situating the handbook within the Digital implementation investment guide (DIIG), WHO SMART Guidelines (layers L1 to L5) and the digital health supply chain architecture's product registry; it also outlines the chapters, how the handbook was developed, target users per chapter, and when to use it.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-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. 2, 'Importance of product master data'. Three columns. On the left, SUPPLY CHAIN PARTNERS: manufacturers, procurers, Ministry of Health / programmes, donors, shippers, regulatory authority, central/regional/district warehouses and health facilities. On the right, SUPPLY CHAIN PROCESSES: forecasting and supply planning, procurement, ordering/re-ordering, inventory management, distribution, dispensing, product recalls and finance/insurance. Arrows from both point into the central PRODUCT MASTER DATA column — general information, classification details, pharmaceutical information, logistical information and other information — which flows down through a medicine icon to Patients.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-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. 3, 'Impact of inconsistent product information'. An arrow labelled PHYSICAL FLOW OF HEALTH PRODUCTS runs across five actors: manufacturers, central warehouse, health facilities, community health workers and patients. Beneath them sit the systems each stage uses — a warehouse management system, an eLMIS and paper forms — and each holds the same product under a different code (123123, A1232, P44545, AM545). Broken-chain icons join the codes, showing that the identifiers do not link up along the chain.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-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. 4, 'Planning and implementing a digital health enterprise: phases, steps and resources'. Seven numbered phases — assessing the current state and enabling environment; establishing a shared understanding and strategic planning; defining the future state; planning the enterprise architecture; determining health content requirements; M&E and fostering data use; and implementing, maintaining and scaling — each with its steps. Resource tiles are placed against the phases they serve and marked as PDF or online, among them the DIIG, the WHO SMART guidelines with digital adaptation kits, TOGAF, OpenHIE and the WHO handbook for health supply chain architecture. The tile 'WHO handbook for health product catalogue (this document)' is highlighted in phase 07. It is the same chart as Fig. 6 of the WHO handbook for digitalizing primary health care, re-pointed to this document.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-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. 5, 'WHO SMART Guidelines Approach'. A research and evidence base feeds five knowledge layers and their products: 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). Each passes through LOCALISATION into a country-implementation adaptation: national policies and procedures, localised requirements, localised machine-readable code and standards, localised static digital services, and dynamic applications optimised for local outcomes. All feed DATA, EVIDENCE, AND IMPACT, which returns to the evidence base as EVIDENCE FROM DIGITAL IMPLEMENTATIONS.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-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. 6, 'Example of an Antenatal Care Business clinical workflow with highlighted' activities. The upper part is a swimlane process in a health facility, with Client and Health worker lanes. The client arrives at the facility, then goes through registration, rapid assessment and management, a danger-signs/referral decision, pregnancy confirmation, a first-contact decision and a quick check. These lead to collecting the woman's profile and history, then an ANC assessment (check symptoms and follow-up, conduct physical exam, conduct laboratory tests and imaging), then 10. Counselling, in-facility management and treatment, with subactivities 10.1 to 10.9, then a referral decision, scheduling, and self-care in the home or community until the woman returns. The lower part enlarges activities 6 to 10. Highlighted borders mark 9 (conduct laboratory tests and imaging), 10.5 nutrition supplementation, 10.7 immunizations and 10.9 deworming and malaria counselling and prophylaxis — the activities that involve health products.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-eng/blocks/table-002",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Fig. 6: Example of an Antenatal Care Business clinical workflow with highlighted connections to supply chain",
      "pageStart": 15,
      "pageEnd": 15,
      "target": "../tables/table-2.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-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. 7, 'Digital health supply chain architecture framework'. Top row: SHARED SERVICES, whose foundational components are facility, product (highlighted) and supplier registries; DATA SERVICES, with analytics (supply chain reports, data warehouse) and traceability (track and trace, product verification); and Digital Ecosystems (quality, health management information, regulatory, and finance and insurance systems). A middle INTEROPERABILITY LAYER of enabling components: authentication, encryption, transformation, orchestration, validation and translation. Bottom: HEALTH SUPPLY CHAIN INFORMATION SYSTEMS — forecasting and planning, order management, warehouse management, cold chain management, procurement, supplier and contract management, transportation management and dispensing — beside External systems (global platforms, manufacturer systems, data repositories).",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-eng/blocks/table-003",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 18,
      "pageEnd": 19,
      "target": "../tables/table-3.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-004",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Establishing regulatory policies to promote product master data standardization",
      "pageStart": 20,
      "pageEnd": 21,
      "target": "../sections/sec-004-01-establishing-regulatory-policies-to-promote-p.md",
      "narrative": null,
      "content": "policies to promote \nproduct master data \nstandardization\nManufacturers and distributors of health products are the \nsource of truth for product master data. Ensuring that \nmanufacturers and distributors consistently provide \nproduct master data in a standardized and uniform format \nis crucial for enabling interoperability and leveraging \nautomation through barcode scanning.\nRegulatory organizations play a key role in establishing \npolicies and legislation that mandate and enforce \nrequirements for manufacturers and distributors to supply \nstandardized product master data. This chapter outline",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Opening of Chapter 1 on establishing regulatory policies, stating that manufacturers and distributors are the source of truth for product master data and that Ministries of Health and national drug regulatory authorities should set policies and legislation mandating standardized product master data.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-005",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 1. Identify necessary regulatory policies and legislations",
      "pageStart": 21,
      "pageEnd": 22,
      "target": "../sections/sec-005-step-1-identify-necessary-regulatory-policies-an.md",
      "narrative": null,
      "content": "policies and legislations\nSTEP 1\nINPUTS\nSTEPS\nRESOURCES\nOUTPUTS\n•\t Existing \nregulatory \npolicies and \nlegislations\nAnalyse current regulations to determine \nif they clearly articulate policies for \nproduct master data standardization and \nsharing, in alignment with internationally \naccepted standards.\n•\t Master data \nguideline template\n•\t Product \nidentification and \nlabelling guidance \nand template\n•\t List of additional \nregulatory \npolicies and \nlegislations \nrequired\n•\t List of \nmodifications \nneeded for \nexisting policies \nand legislations\nDetermine whether current data \nstandardization a",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 1 Step 1 on analysing existing regulations for product master data standardization and sharing, checking compliance mechanisms, and listing needed new or modified policies, with resources such as a master data guideline template, plus mitigations for low regulatory capacity, competing priorities and unclear mandates (partner engagement and a RACI responsibility matrix).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-006",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 2. Develop the identified regulatory policies and legislations",
      "pageStart": 22,
      "pageEnd": 22,
      "target": "../sections/sec-006-step-2-develop-the-identified-regulatory-policie.md",
      "narrative": null,
      "content": "and legislations\nINPUTS\nSTEPS\nRESOURCES\nOUTPUTS\n•\t List of additional \nregulatory \npolicies and \nlegislations \nrequired\nDevelop the required policies and regulations \nsuch as master data guidelines, ensuring they \nare consistent with both current and emerging \nregulations concerning data standardization \nand AIDC.\n•\t List of \nmodifications \nneeded for \nexisting policies \nand legislations\n•\t Regulatory policies and guidelines \nmust promote efficient mechanisms for \nstakeholders such as manufacturers, \ndistributors and other suppliers to share \nthe required data. \n•\t Timelines with phased roll-o",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 1 Step 2 on drafting the identified policies and regulations, such as master data guidelines consistent with data standardization and AIDC rules, with phased roll-out timelines for manufacturers, and mitigations for lengthy, underfunded drafting through early engagement of government leaders, funding partners and private sector manufacturers and distributors.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-007",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 3. Coordinate reviews and approvals of the drafted policies",
      "pageStart": 22,
      "pageEnd": 23,
      "target": "../sections/sec-007-step-3-coordinate-reviews-and-approvals-of-the-d.md",
      "narrative": null,
      "content": "INPUTS\nSTEPS\nRESOURCES\nOUTPUTS\n•\t Master data \nrelated policies \nand legislations\nEvaluate the newly developed and the \nrevised policies and legislations led by \nthe NRA in collaboration with primary \nstakeholders like the Ministry of Health, \ncentral and regional warehouses, \nprocurement entities, manufacturers and \ndistributors and operational leaders\n•\t Approved master \ndata policies \nand legislations\nEnsure that all feedback are suitably \naddressed, and revisions are incorporated \ninto the final draft\nObtain appropriate approvals for publishing \nof the policies\nSTEP 4",
      "truncated": false,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 1 Step 3 on coordinating NRA-led review of the drafted master data policies and legislation with the Ministry of Health, warehouses, procurement entities, manufacturers, distributors and operational leaders, incorporating feedback and obtaining approval for publication.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-008",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 4. Publish and enforce the approved regulatory policies to promote product master data standardization",
      "pageStart": 23,
      "pageEnd": 24,
      "target": "../sections/sec-008-step-4-publish-and-enforce-the-approved-regulato.md",
      "narrative": null,
      "content": "to promote product master data standardization\nINPUTS\nSTEPS\nRESOURCES\nOUTPUTS\n•\t Approved \nmaster data \npolicies and \nlegislations\nPublish the approved policy document \n•\t Endorsed master \ndata policies \nand legislations \nDefine mechanisms to institutionalize \nand monitor compliance of the policies\nPublish the policy document\nPOTENTIAL RISKS\nMITIGATION\nManufacturers’ \npoor adherence \nto regulations.\n•\t Assess the situation to gauge current capabilities, investment willingness, and the required \neffort and timelines for stakeholders such as manufacturers and service providers to meet \nregulator",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 1 Step 4 covering publication and enforcement of approved regulatory policies, defining compliance monitoring mechanisms, mitigations for poor manufacturer adherence (situation assessment, phased approach, clear transition timelines, training manuals and webinars, and a global standards community network), and the Chapter 1 end-of-chapter checkpoint.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-009",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Instituting data management and governance policies",
      "pageStart": 24,
      "pageEnd": 25,
      "target": "../sections/sec-009-02-instituting-data-management-and-governance-po.md",
      "narrative": null,
      "content": "management and \ngovernance policies\nFor effective use of data in operations, analysis, and \ndecision-making, the integrity and quality of data must be \nconsistently and continuously maintained. Establishing \ndata management policies to maintain master data \nstructures, definitions, and operational procedures is \ncrucial for sustaining data integrity and quality. Data \nmanagement policies should ensure adherence to \nprinciples of privacy, security, and ethical data usage. This \nchapter outlines steps to establish comprehensive data \nmanagement policies and procedures. It is important to \nnote t",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Opening of Chapter 2 on data management and governance policies, stressing that master data structures, definitions and operational procedures must maintain data integrity and quality while respecting privacy, security and ethical data use, and noting that the steps may run concurrently.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-010",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 1. Define product master data management procedures",
      "pageStart": 25,
      "pageEnd": 27,
      "target": "../sections/sec-010-step-1-define-product-master-data-management-pro.md",
      "narrative": null,
      "content": "STEP 1\nINPUTS\nSTEPS\nRESOURCES\nOUTPUTS\n•\t Published \nmaster data \npolicies and \nlegislations \nBegin by identifying and analyzing \nthe existing challenges in master data \nmanagement and their impact on \ninteroperability across systems and \norganizations. This includes:\n•\t Reviewing current product coding \nschemes and data structures.\n•\t Assessing the number of product master \ndata sets maintained across different \nsystems and organizations.\n•\t Identifying duplications and \ninconsistencies in data, where applicable.\n•\t Evaluate the data harmonization \nneeds and the data management \nprocedures req",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 2 Step 1 on defining product master data management procedures: reviewing coding schemes, duplicate data sets and harmonization needs, and producing a data harmonization plan, procedures and governance group TOR; it details key elements including a data governance framework with data owner, custodian and steward roles, data quality, security, interoperability, lifecycle, change management and monitoring.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-011",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 2. Define coding scheme, data definitions and structures to organize and maintain product master data",
      "pageStart": 27,
      "pageEnd": 31,
      "target": "../sections/sec-011-step-2-define-coding-scheme-data-definitions-and.md",
      "narrative": null,
      "content": "to organize and maintain product master data\nINPUTS\nSTEPS\nRESOURCES\nOUTPUTS\n•\t Data \nharmonization \nactivities plan\nConduct data harmonization activities \nsuch as establishing a standardized coding \nscheme, master data definitions and \nstructures* to organize and maintain master \ndata consistently and persistently\n•\t Master data \nmanagement \nprocedures \nincluding master \ndata governance \npolicies\n•\t Data harmonization activities must \nconsider all sources of product data, \nas well as the systems, processes, and \norganizations or stakeholders that will \nutilize this data. It is essential to con",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 2 Step 2 on defining coding schemes, data definitions and structures, mapping country identifiers to HL7 FHIR, IDMP and GS1 GTINs, and distinguishing classifications (ATC/DDD, ICD), generic products, trade items and regulated trade items, with coding best practices, the WHODrug dictionary, packaging hierarchy figures (Figs 8 to 12); it also carries the Step 3 table on data sources, sharing mechanisms and data use policies.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/figure-vfig-p028",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 28,
      "pageEnd": 28,
      "target": "../figures/vfig-p028.png",
      "narrative": "draft",
      "content": "Fig. 8, 'Linkage across classifications, generic products and trade items'. Three columns: CLASSIFICATION (classes or groups of diseases, pathogens or drugs); PRODUCT (name/INN, strength, dosage form, route of administration); and TRADE ITEM (unique identifier such as a GTIN, brand name, manufacturer, country of origin, packaging details, volumetrics, shelf life). The example row traces Nervous system → Analgesics → Other analgesics and antipyretics → Anilides → Paracetamol to the product 'Paracetamol 500 mg tablet'. That product branches into two manufacturers' trade items, each with its own unique IDs and pack hierarchy: a case and inner pack of 100 from ABC Manufacturing (brand Ceta123), and a case, inner pack of 50 and each of 10 from XYZ Manufacturing (brand ParaXYZ). A bottom row gives each column's use: strategic (data aggregation and analysis), tactical (forecasting, procurement planning and aggregate visibility) and operational (inventory, distribution, tracking and tracing, pharmacovigilance and AEFI analysis).",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-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. 9, 'Relationship between generic product, trade item and regulated trade item'. Three classes are drawn as boxes listing their attributes with cardinalities. GENERIC PRODUCT has identifier 0..*, status, name (nameType, nameValue), description, classification, unitOfUse, dosageForm, strength, routeOfAdministration, manufacturer, countryOfOrigin, shelfLife, doseQuantity, attribute (type, value[x]) and associatedProduct (product, relationship, quantity). TRADE ITEM has identifier 1..*, status, tradeItemName, description, classification, manufacturer, countryOfOrigin, shelfLife, associatedGenericProduct (genericProduct, quantity), contains (tradeItem, quantity) and attribute. REGULATED TRADE ITEM has identifier, status, jurisdiction, authorisationHolder, validityPeriod, authorisedTradeItem, attribute and associatedProduct. The associations read: one generic product to zero or more trade items, and one trade item to zero or more regulated trade items.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-eng/blocks/figure-img-p030-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 30,
      "pageEnd": 30,
      "target": "../images/img-p030-1.png",
      "narrative": "draft",
      "content": "Fig. 10, 'Product packaging hierarchy' (source: GS1.org), in the section on instituting data management and governance policies. It is drawn as a staircase of four grey steps, each holding packaging illustrations. The top step, labelled PRIMARY, shows individual items such as vials, a bottle, syringes in blister packs, a blister strip and a sterile-packed instrument. The next step, SECONDARY, shows boxes and cartons holding those items; the third, SECONDARY OR TERTIARY, shows open cartons and a row of boxed packs; and the bottom step, TERTIARY, shows shipping cases and a shrink-wrapped pallet of boxes.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-eng/blocks/figure-vfig-p030",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 30,
      "pageEnd": 30,
      "target": "../figures/vfig-p030.png",
      "narrative": "draft",
      "content": "Fig. 10, 'Product packaging hierarchy', shows four stepped shelves of packaged goods labelled, top to bottom, PRIMARY (vials, syringes, blister packs), SECONDARY, SECONDARY OR TERTIARY, and TERTIARY (cases and pallets). Source: GS1.org. Fig. 11, 'Example of packaging variations across manufacturers', shows one PRODUCT, a paracetamol 500 mg tablet, procured from two manufacturers with different pack configurations: MFR A ships 1 case of 12 packs of 50 tablets each, and MFR B ships 1 case of 10 packs of 100 tablets each.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-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, 'Mapping across product packaging hierarchy using FHIR resource'. Five record boxes, each listing identifier, description, name, characteristic and association. A GENERIC PRODUCT (identifier MR001) associates to a trade item from manufacturer A (identifier 17801415202675) and to manufacturer B's tertiary pallet (18901415202906). The pallet associates to MFR B's tertiary case (08901415202908, quantity 100), which associates to MFR B's secondary inner pack (08901415202910, quantity 50) — the packaging hierarchy expressed as chained associations.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-012",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 3. Define data use policies and data sharing mechanisms to support interoperability",
      "pageStart": 31,
      "pageEnd": 32,
      "target": "../sections/sec-012-step-3-define-data-use-policies-and-data-sharing.md",
      "narrative": null,
      "content": "to support interoperability\nSTEP 3\nGENERIC PRODUCT\nidentifier MR001\ndescription\nname\n characteristic\n association\nTRADE ITEM (MFR B)\nTertiary (Pallet)\nidentifier 18901415202906\ndescription\nname\n characteristic\n association\nTRADE ITEM (MFR B)\nTertiary (Case)\nidentifier 08901415202908\ndescription\nname\n characteristic\n association\n quantity 100\nTRADE ITEM (MFR A)\nidentifier 17801415202675\ndescription\nname\n characteristic\n association\nTRADE ITEM (MFR B)\nSecondary (Inner pack)\nidentifier 08901415202910\ndescription\nname\n characteristic\n association\n quantity 50",
      "truncated": false,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Fragment of the Figure 12 example under Chapter 2 Step 3, showing a generic product (identifier MR001) mapped to trade items from two manufacturers across pallet, case and inner-pack packaging levels, with GTIN-style identifiers and quantities of 100 and 50.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-013",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 4. Institutionalise product master data governance policies and procedures.",
      "pageStart": 32,
      "pageEnd": 33,
      "target": "../sections/sec-013-step-4-institutionalise-product-master-data-gove.md",
      "narrative": null,
      "content": "policies and procedures.\nSTEP 4\nPOTENTIAL RISKS\nMITIGATION\nThe variety and volume \nof data attributes raise \nconcerns regarding privacy, \nconfidentiality, and data \nsensitivity. These concerns can \nmake data sources reluctant to \nshare information with multiple \nand diverse stakeholders.\nTo address these concerns, procedures and systems should be developed to \ncategorize data attributes based on their level of sensitivity. Access should then \nbe controlled according to these sensitivity categories, ensuring appropriate data \nprotection while enabling secure data sharing.\nINPUTS\nSTEPS\nRESOURCES",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 2 Step 4 on institutionalising product master data governance by establishing a master data governance group, possibly within existing steering committees, and promoting consistent use of procedures, coding schemes and policies across supply chain systems; it opens with a mitigation for data-sensitivity concerns through sensitivity-based access controls.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-014",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 5. Define short- and long-term strategies to source standardized product master data",
      "pageStart": 33,
      "pageEnd": 34,
      "target": "../sections/sec-014-step-5-define-short--and-long-term-strategies-to.md",
      "narrative": null,
      "content": "standardized product master data\nINPUTS\nSTEPS\nRESOURCES\nOUTPUTS\n•\t \tEndorsed \nmaster data \npolicies and \nlegislations \n(from chapter 1)\nIdentify challenges with sourcing master \ndata, such as incompleteness, data quality, \ndata availability, awareness etc.\nDefine a short and medium-term strategy to \nsource master data, while considering and \naddressing the identified challenges. \n•\t \tData sharing and \ndata use policies\n•\t \tFor example, gathering product master \ndata from procurement agencies, donors, \nand physical packages when there is no \nefficient data sharing from manufacturers.\n•\t Standar",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 2 Step 5 on short- and long-term strategies to source standardized product master data, such as gathering data from procurement agencies, donors and packaging, then formalising submission during regulatory product registration, with mitigations including awareness webinars, one-pagers and a minimal attribute set (INN, manufacturer, dosage form, strength, country of origin), and the Chapter 2 checkpoint.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-015",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Deploying appropriate technology to manage product master data",
      "pageStart": 34,
      "pageEnd": 35,
      "target": "../sections/sec-015-03-deploying-appropriate-technology-to-manage-pr.md",
      "narrative": null,
      "content": "technology to manage \nproduct master data",
      "truncated": false,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Heading-only block for Chapter 3, Deploying appropriate technology to manage product master data; the extracted text carries just the chapter title, with the chapter's introductory text and steps appearing in the following blocks.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-016",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 1. Define system requirements for the NPC tool",
      "pageStart": 35,
      "pageEnd": 36,
      "target": "../sections/sec-016-step-1-define-system-requirements-for-the-npc-to.md",
      "narrative": null,
      "content": "across various health and supply chain systems to enable \nuniform product identification. It is essential that this data \nis organized and managed consistently, with minimal \nmanual intervention, to ensure data quality and integrity.\nAdopting a suitable technology tool supports the \nongoing management of product master data while \nmaintaining consistent quality and compliance with \ndefined standards. A widely used term for such a tool \nis the NPC, which many countries implement to oversee \nproduct master data.\nThis chapter outlines the key steps that countries can \nfollow to select and impleme",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 3 introduction and Step 1, explaining that a national product catalogue (NPC) tool manages product master data consistently, and setting out how to define and approve functional and non-functional NPC system requirements using resources such as Target Software Standards v2, ISO IDMP standards and HL7 FHIR implementation guides.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-017",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 2. Identify technology options and select the appropriate tool",
      "pageStart": 36,
      "pageEnd": 36,
      "target": "../sections/sec-017-step-2-identify-technology-options-and-select-th.md",
      "narrative": null,
      "content": "INPUTS\nSTEPS\nRESOURCES\nOUTPUTS\n•\t Approved \nfunctional and \nnon-functional \nsystem \nrequirements \nfor NPC.\nConduct market research activities such \nas Request for information (RFI) to explore \ntechnology options for an appropriate tool \nfor NPC. \n•\t Assess existing digital tools, such as \nenterprise resource planning applications, \nto determine if they fulfil NPC system \nrequirements before deciding to invest \nin a new software.\nConsider the following \nopen-source options: \n•\t Selection of an \nappropriate \ntechnology tool \nfor NPC.\n•\t PCMT\n•\t PCMT demo\n•\t PCMT instance \nhosted by WHO \n(Refer t",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 3 Step 2 on identifying technology options for the NPC through market research such as a request for information, assessing existing tools like enterprise resource planning applications, considering the open-source PCMT and the WHO-hosted instance, and running RFQ or RFP processes to select the tool.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-018",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 3. Prepare a plan to implement the NPC tool and integrate with other systems to share standardized data",
      "pageStart": 36,
      "pageEnd": 37,
      "target": "../sections/sec-018-step-3-prepare-a-plan-to-implement-the-npc-tool.md",
      "narrative": null,
      "content": "with other systems to share standardized data\nINPUTS\nSTEPS\nRESOURCES\nOUTPUTS\n•\t Approved \nfunctional and \nnon-functional \nsystem \nrequirements \nfor NPC. \nDevelop a detailed implementation plan \nto design, configure and deploy the chosen \ntool for NPC. \nReview the plan with relevant stakeholders \nand initiate the implementation project.\n•\t Selection of an \nappropriate \ntechnology tool \nfor NPC.\n•\t NPC Implementation \nplan template\n•\t NPC \nimplementation \nproject plan.\nSTEP 4",
      "truncated": false,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 3 Step 3 on developing a detailed implementation plan to design, configure and deploy the chosen NPC tool, reviewing it with relevant stakeholders, and initiating the implementation project, with an NPC implementation plan template as a resource.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-019",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 4. Design, develop and deploy the NPC tool",
      "pageStart": 37,
      "pageEnd": 39,
      "target": "../sections/sec-019-step-4-design-develop-and-deploy-the-npc-tool.md",
      "narrative": null,
      "content": "INPUTS\nSTEPS\nRESOURCES\nOUTPUTS\n•\t NPC \nImplementation \nproject plan.\nDesign the system and necessary \nconfigurations to fulfil all functional \nand non-functional requirements.\n•\t Approved \nfunctional and \nnon-functional \nsystem \nrequirements \nfor NPC.\nReview the design with relevant \nstakeholders and facilitate design approvals.\nDevelop the system and required \nconfigurations of the NPC tool and build \nintegrations with other systems as required: \n•\t \tEnsure that the system accommodates \nthe master data management procedures \nincluding coding scheme, data definitions \nand structures.\n•\t Ensure",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 3 Step 4 on designing, developing, validating (system, integration, performance testing and UAT) and deploying the NPC tool with support for coding schemes and packaging hierarchies, mitigations for limited technical capacity including use of the WHO-hosted PCMT, the Chapter 3 checkpoint, and the introduction to Chapter 4 on change management.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-020",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 1. Develop a change management plan to institutionalise use of NPC",
      "pageStart": 39,
      "pageEnd": 40,
      "target": "../sections/sec-020-step-1-develop-a-change-management-plan-to-insti.md",
      "narrative": null,
      "content": "to institutionalise use of NPC\nINPUTS\nSTEPS\nRESOURCES\nOUTPUTS\n•\t Standardized \nmaster data \ncoding schemes \nand structures.\nIdentify all the systems and processes that \nneed standardized product master data.\nIdentify and define the specific changes \nneeded to institutionalize the use of \nstandardized product master data across \npeople, processes, and systems. \nThese may include:\n•\t Master data \nmanagement \nprocedures \nincluding master \ndata governance \npolicies.\n•\t \tProcess changes to ensure that \nstandardized product master data is \nuniformly referenced across all operational \nprocesses, incl",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 4 Step 1 on a change management plan to institutionalise NPC use, identifying needed changes to processes, system enhancements, data structures and data exchange triggers across forecasting, procurement, inventory, shipping and dispensing, with a best practice of using local trade item identifiers mapped to GTINs when available via a Country Trade Item Identifier attribute.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-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. 13, 'Transitional approach to adopting globally unique trade item numbers'. A national product code record — NPC01101001, Lamivudine 50 mg tablet, dosage form TA, route oral — branches into two tables of trade items mapped to it. The first holds GS1 GTINs (for example 58904093825793) for manufacturer MFR001 from IN, with child GTINs, child quantities of 100 and 10, 3000 eaches and a shelf life of 670. The second holds items from MFR002 from KE that have no GTIN yet and are identified only by country trade item identifiers (P006008, P006009), with child quantities of 120 and 30, 7200 eaches and a shelf life of 1095. So a national code can carry GTIN-identified and not-yet-GTIN-identified items side by side during the transition.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-021",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 2. Define SOPs to collect, organize and manage product master data",
      "pageStart": 40,
      "pageEnd": 42,
      "target": "../sections/sec-021-step-2-define-sops-to-collect-organize-and-manag.md",
      "narrative": null,
      "content": "National Product Code\nDescription\nDosage Form\nRoute of Administration\nGTIN\n58904093825793\n58904093825700\nCountry Trade\nItem Identifier\n58904093825793\n58904093825700\nChild GTIN\n58904093825700\n58904093825600\nChild SKU\n58904093825700\n58904093825600\nChild\nQuantity\n100\n10\nQuantity\nof Eaches\n3000\n3000\nShelf\nLife\n670\n670\nManufacturer\nMFR001\nMFR001\nCountry\nof Origin\nIN\nIN\nNPC01101001\nLamivudine 50 Mg tablet\nTA\nOral\nGTIN\nCountry Trade\nItem Identifier\nP006008\nP006009\nChild GTIN\nChild SKU\nP006009\nChild\nQuantity\n120\n30\nQuantity\nof Eaches\n7200\n7200\nShelf\nLife\n1095\n1095\nManufacturer\nMFR002\nMFR002\nCountry\nof",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 4 Step 2 on defining, validating and approving SOPs to collect, organize, add and update product master data in the NPC, plus a continuous training and advocacy plan; it opens with an example table of lamivudine trade items with GTINs and local identifiers, and lists risks such as data quality and packaging quantity conversions, ending with the Chapter 4 checkpoint.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-022",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Building capacity to sustainably manage NPC",
      "pageStart": 42,
      "pageEnd": 43,
      "target": "../sections/sec-022-05-building-capacity-to-sustainably-manage-npc.md",
      "narrative": null,
      "content": "to sustainably manage NPC",
      "truncated": false,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Heading-only block for Chapter 5, Building capacity to sustainably manage NPC; the extracted text carries just the chapter title, with the chapter's introduction and steps appearing in the following blocks.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-023",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 1. Identify human resource capacity needs to support NPC",
      "pageStart": 43,
      "pageEnd": 44,
      "target": "../sections/sec-023-step-1-identify-human-resource-capacity-needs-to.md",
      "narrative": null,
      "content": "systems depends on the availability of human resources \nwith the appropriate skill sets to operate the systems and \nexecute the processes. In addition to technical skills, the \nworkforce must also understand the purpose of improved \nsystems and processes, along with the benefits they bring \nto their daily work.\nHuman resource capacity is a critical component \nfor the successful implementation and adoption of \nglobal standards–based master data management \nsystems and processes. This chapter outlines the steps \nthat countries can follow to build human resource capacity \nto sustainably manage th",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 5 introduction and Step 1, stressing human resource capacity for global standards-based master data management, and setting out how to determine required roles such as Catalogue Manager and NPC System Administrator, define job descriptions, and develop a human resource plan covering staff turnover, cross-skilling, knowledge management and hiring needs.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-024",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 2. Onboard and assign individuals to the identified roles",
      "pageStart": 44,
      "pageEnd": 44,
      "target": "../sections/sec-024-step-2-onboard-and-assign-individuals-to-the-ide.md",
      "narrative": null,
      "content": "INPUTS\nSTEPS\nRESOURCES\nOUTPUTS\n•\t List of roles necessary to \nsupport NPC and product \nmaster data management \nprocesses.\nDevelop budgets and identify \nfunding sources to fill the \nidentified roles and future \nhuman resource needs.\n•\t Job descriptions for each role.\n•\t Human resource \nmanagement plan.\n•\t Budget for \nhuman resource \ncapacity needs.\n•\t Onboarded \nresources.\nOnce sufficient funding has \nbeen identified, recruit and train \npeople with required skillsets to \nfill the necessary roles.\nSTEP 3",
      "truncated": false,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 5 Step 2 on onboarding staff to the identified NPC roles by developing budgets and identifying funding sources for current and future human resource needs, then recruiting and training people with the required skill sets once funding is secured.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-025",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Step 3. Develop knowledge management plan to enhance skills and capacity in alignment with evolving needs",
      "pageStart": 44,
      "pageEnd": 45,
      "target": "../sections/sec-025-step-3-develop-knowledge-management-plan-to-enha.md",
      "narrative": null,
      "content": "and capacity in alignment with evolving needs\nINPUTS\nSTEPS\nRESOURCES\nOUTPUTS\n•\t List of roles necessary to support \nthe NPC and product master data \nmanagement processes.\nDevelop budgets and \nidentify funding sources \nto fill the identified \nroles and future human \nresource needs.\n•\t Job descriptions.\n•\t TOR for the Master Data \nGovernance Group.\nOnce sufficient funding \nhas been identified, \nrecruit and train people \nwith required skillsets to \nfill the necessary roles.\n•\t Master data management procedures, \nincluding master data governance \npolicies.\nDevelop strategies to \nexpand human resou",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 5 Step 3 on a knowledge management plan, including budgeting and recruitment for roles and strategies to expand capacity by engaging local vendors and implementation partners, with outputs such as an organogram and a governmental strategy for local technical capacity, and the Chapter 5 end-of-chapter checkpoint.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-026",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Leveraging WHO hosted PCMT",
      "pageStart": 45,
      "pageEnd": 48,
      "target": "../sections/sec-026-06-leveraging-who-hosted-pcmt.md",
      "narrative": null,
      "content": "WHO-hosted PCMT  \nCountries planning to implement a digital tool to manage \nproduct master data may consider using the WHO–\nhosted PCMT as an initial option. This tool can serve as a \nstarting point to manage national health product master \ndata while countries build the necessary technical \nresources and capacity to implement an in-country–\nhosted solution. Alternatively, countries may continue \nusing the WHO-hosted PCMT if it meets their \nongoing needs.\nThe WHO-hosted PCMT will be available in 2026. \nFig. 14 illustrates a conceptual model of how countries \ncan leverage the PCMT to manage the",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 6 on the WHO-hosted PCMT, to be available in 2026, as an initial or ongoing option for countries to manage national product catalogues, illustrating a global catalogue with separate country catalogues and an example access model where user groups are assigned to categories with view, edit or own permissions, plus cross-catalogue associations and copy rules.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/figure-vfig-p046",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 46,
      "pageEnd": 46,
      "target": "../figures/vfig-p046.png",
      "narrative": "draft",
      "content": "Fig. 14, 'Illustration of how countries can leverage WHO hosted PCMT'. Inside a panel labelled PRODUCT CATALOGUE MANAGEMENT TOOL, a GLOBAL CATALOGUE (global identifier, unit of use, pharmaceutical information such as dosage form, route of administration and strength, trade item information, and manufacturer, country of origin and shelf life) feeds COUNTRY CATALOGUE A and COUNTRY CATALOGUE B, each adding country identifiers and country-specific information such as registration numbers. The arrows are annotated 'Country catalogues to derive common product information from the global catalog'. Country A Users and Country B Users each work in their own catalogue, and the whole sits on WHO INFRASTRUCTURE.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-027",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Sharing product master data as a global good",
      "pageStart": 48,
      "pageEnd": 51,
      "target": "../sections/sec-027-07-sharing-product-master-data-as-a-global-good.md",
      "narrative": null,
      "content": "data as a global good\nSharing health product master data with a global \nrepository—such as the WHO Global Product Catalogue—\nholds significant value and importance as a global \ngood for several reasons:\n•\t\nAccess to accurate information: A centralized \nrepository enables health professionals and \norganizations worldwide to access accurate and \nup-to-date information on health products.\n•\t\nStandardization: A global repository aggregates \nmaster data from multiple sources for the same or \nsimilar products and facilitates the harmonization of \ndata differences to support standardization.\n•\t\nReduc",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 7 on sharing product master data with a global repository such as the WHO Global Product Catalogue, listing benefits (accurate information, standardization, reduced redundancy, crisis management, equal access and capacity building) and showing how countries using the WHO-hosted PCMT or in-country tools can share master data globally (Fig. 15).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/figure-vfig-p050",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 50,
      "pageEnd": 50,
      "target": "../figures/vfig-p050.png",
      "narrative": "draft",
      "content": "Fig. 15, 'Illustration of how countries can share data with the WHO hosted PCMT'. It extends Fig. 14. As there, the global catalogue feeds country catalogues A and B inside the PRODUCT CATALOGUE MANAGEMENT TOOL on WHO infrastructure, used by Country A and Country B users. In addition, each country catalogue returns 'Product master data' to the global catalogue, and OTHER COUNTRIES contribute PRODUCT MASTER DATA into it from above, so the global catalogue is fed by the countries as well as feeding them.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-028",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Sharing implementation experiences",
      "pageStart": 51,
      "pageEnd": 55,
      "target": "../sections/sec-028-08-sharing-implementation-experiences.md",
      "narrative": null,
      "content": "implementation \nexperiences\nCOUNTRY:\nRWANDA\nREGULATORY\nDATA\nTECHNOLOGY\nPEOPLE\nCHANGE \nMANAGEMENT\nStatus\n•\t Regulations \ngoverning the \nimplementation \nof identification \ndata capture and \ndata sharing for \ntraceability of \npharmaceutical \nproduct\n•\t Guidelines for \nidentification \nand labelling of \npharmaceutical \nproducts published in \nAug 2022\n•\t Guidelines for product \nand location master \ndata sharing published \nin Aug 2022\n•\t The National Vision \n& Strategy for \nPharmaceutical \nTraceability \nLeveraging GS1 \nGlobal Standards, \npublished in 2019\n7134 products are \nuploaded into NPC and \n261",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 8 implementation experiences from Rwanda, Zambia and Nigeria, set out by regulatory, data, technology, people and change management dimensions, covering status (e.g. 7134 Rwandan products with 2611 mapped to GTINs; 6517 Nigerian products with 794 mapped), processes, challenges, approaches adopted and lessons learnt, such as PCMT-based NPCs, catalogue managers and GTIN mapping.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/table-004",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 52,
      "pageEnd": 54,
      "target": "../tables/table-4.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-029",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "References",
      "pageStart": 55,
      "pageEnd": 56,
      "target": "../sections/sec-029-references.md",
      "narrative": null,
      "content": "References\n1.\t\nYokogawa Electric Corporation. The differences between digitization, \ndigitalization and digital transformation in manufacturing. (https://\nwww.yokogawa.com/library/resources/white-papers/the-differences-\nbetween-digitization-digitalization-and-digital-transformation-in-\nmanufacturing/, accessed 10 January 2020).\n2. \t\nGartner. Definition of Digitization. (https://www.gartner.com/en/\ninformation-technology/glossary/digitization, accessed 10 January 2020).\n3. \t\nYokogawa Electric Corporation. The differences between digitization, \ndigitalization and digital transformation in manufa",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Reference list of 17 cited sources, including Yokogawa and Gartner definitions of digitization, digitalization and digital transformation, UNIDO, WHO SMART Guidelines pages, The Lancet Digital Health, the Open Source Initiative, ITU open standards, GS1 trade items, a UAT guide, the WHO supply chain architecture handbook and the Principles for Digital Development.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/table-005",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 55,
      "pageEnd": 55,
      "target": "../tables/table-5.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240116191-eng/blocks/prose-sec-030",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Annexes",
      "pageStart": 56,
      "pageEnd": 62,
      "target": "../sections/sec-030-annexes.md",
      "narrative": null,
      "content": "Annex 1. Principles for Digital Development\nUnderstand the \nexisting ecosystem\nTrust starts with a thorough understanding of the dynamic cultural, \nsocial and economic context in which you are operating.\nShare, reuse, \nand improve\nBuild on what works, improve what works, and share so that others \ncan do the same.\nDesign with people\nGood design starts and ends with people that will manage, use, and ideally \nbenefit from a given digital initiative.\nDesign for inclusion\nConsider the full range of human diversity to maximize impact and mitigate harm.\nBuild for sustainability\nBuild for the long-ter",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Annexes listing the Principles for Digital Development (Annex 1) and, in Annex 2, additional technical and leadership roles for NPC implementation, such as project manager, solution architect, business analyst, developer, integration specialist, database administrator, infrastructure specialist, QA/test manager, test analyst, system administrator, support engineer and superuser/trainer, with their phases, position types, skill sets and responsibilities.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-14"
      }
    },
    {
      "id": "library/9789240116191-eng/blocks/table-006",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "",
      "pageStart": 57,
      "pageEnd": 61,
      "target": "../tables/table-6.csv",
      "narrative": null,
      "content": null,
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    }
  ]
}
