{
  "$schema": "folio-library-document/v1",
  "id": "9789240116191-eng",
  "title": "Digital transformation handbook for health product catalogue",
  "variant": "pdf",
  "pages": 62,
  "tocSource": "inferred",
  "tocMethod": "contents",
  "toc": [
    {
      "level": 1,
      "title": "Acknowledgements",
      "number": null,
      "page": 5,
      "pageLabel": "iv",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-000-acknowledgements"
    },
    {
      "level": 1,
      "title": "Abbreviations",
      "number": null,
      "page": 6,
      "pageLabel": "v",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-001-abbreviations"
    },
    {
      "level": 1,
      "title": "Glossary",
      "number": null,
      "page": 8,
      "pageLabel": "vii",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-002-glossary"
    },
    {
      "level": 1,
      "title": "Introduction",
      "number": null,
      "page": 10,
      "pageLabel": "1",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-003-introduction"
    },
    {
      "level": 1,
      "title": "Establishing regulatory policies to promote product master data standardization",
      "number": "01",
      "page": 20,
      "pageLabel": "11",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-004-01-establishing-regulatory-policies-to-promote-p"
    },
    {
      "level": 2,
      "title": "Step 1. Identify necessary regulatory policies and legislations",
      "number": null,
      "page": 21,
      "pageLabel": "12",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-005-step-1-identify-necessary-regulatory-policies-an"
    },
    {
      "level": 2,
      "title": "Step 2. Develop the identified regulatory policies and legislations",
      "number": null,
      "page": 22,
      "pageLabel": "13",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-006-step-2-develop-the-identified-regulatory-policie"
    },
    {
      "level": 2,
      "title": "Step 3. Coordinate reviews and approvals of the drafted policies",
      "number": null,
      "page": 22,
      "pageLabel": "13",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-007-step-3-coordinate-reviews-and-approvals-of-the-d"
    },
    {
      "level": 2,
      "title": "Step 4. Publish and enforce the approved regulatory policies to promote product master data standardization",
      "number": null,
      "page": 23,
      "pageLabel": "14",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-008-step-4-publish-and-enforce-the-approved-regulato"
    },
    {
      "level": 1,
      "title": "Instituting data management and governance policies",
      "number": "02",
      "page": 24,
      "pageLabel": "15",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-009-02-instituting-data-management-and-governance-po"
    },
    {
      "level": 2,
      "title": "Step 1. Define product master data management procedures",
      "number": null,
      "page": 25,
      "pageLabel": "16",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-010-step-1-define-product-master-data-management-pro"
    },
    {
      "level": 2,
      "title": "Step 2. Define coding scheme, data definitions and structures to organize and maintain product master data",
      "number": null,
      "page": 27,
      "pageLabel": "18",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-011-step-2-define-coding-scheme-data-definitions-and"
    },
    {
      "level": 2,
      "title": "Step 3. Define data use policies and data sharing mechanisms to support interoperability",
      "number": null,
      "page": 31,
      "pageLabel": "22",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-012-step-3-define-data-use-policies-and-data-sharing"
    },
    {
      "level": 2,
      "title": "Step 4. Institutionalise product master data governance policies and procedures.",
      "number": null,
      "page": 32,
      "pageLabel": "23",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-013-step-4-institutionalise-product-master-data-gove"
    },
    {
      "level": 2,
      "title": "Step 5. Define short- and long-term strategies to source standardized product master data",
      "number": null,
      "page": 33,
      "pageLabel": "24",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-014-step-5-define-short--and-long-term-strategies-to"
    },
    {
      "level": 1,
      "title": "Deploying appropriate technology to manage product master data",
      "number": "03",
      "page": 34,
      "pageLabel": "25",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-015-03-deploying-appropriate-technology-to-manage-pr"
    },
    {
      "level": 2,
      "title": "Step 1. Define system requirements for the NPC tool",
      "number": null,
      "page": 35,
      "pageLabel": "26",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-016-step-1-define-system-requirements-for-the-npc-to"
    },
    {
      "level": 2,
      "title": "Step 2. Identify technology options and select the appropriate tool",
      "number": null,
      "page": 36,
      "pageLabel": "27",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-017-step-2-identify-technology-options-and-select-th"
    },
    {
      "level": 2,
      "title": "Step 3. Prepare a plan to implement the NPC tool and integrate with other systems to share standardized data",
      "number": null,
      "page": 36,
      "pageLabel": "27",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-018-step-3-prepare-a-plan-to-implement-the-npc-tool"
    },
    {
      "level": 2,
      "title": "Step 4. Design, develop and deploy the NPC tool",
      "number": null,
      "page": 37,
      "pageLabel": "28",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-019-step-4-design-develop-and-deploy-the-npc-tool"
    },
    {
      "level": 1,
      "title": "Creating protocols for managing change",
      "number": "04",
      "page": 38,
      "pageLabel": "29",
      "confidence": 0.55,
      "evidence": [
        "contents",
        "number"
      ],
      "source": "inferred",
      "section": null
    },
    {
      "level": 2,
      "title": "Step 1. Develop a change management plan to institutionalise use of NPC",
      "number": null,
      "page": 39,
      "pageLabel": "30",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-020-step-1-develop-a-change-management-plan-to-insti"
    },
    {
      "level": 2,
      "title": "Step 2. Define SOPs to collect, organize and manage product master data",
      "number": null,
      "page": 40,
      "pageLabel": "31",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-021-step-2-define-sops-to-collect-organize-and-manag"
    },
    {
      "level": 1,
      "title": "Building capacity to sustainably manage NPC",
      "number": "05",
      "page": 42,
      "pageLabel": "33",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-022-05-building-capacity-to-sustainably-manage-npc"
    },
    {
      "level": 2,
      "title": "Step 1. Identify human resource capacity needs to support NPC",
      "number": null,
      "page": 43,
      "pageLabel": "34",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-023-step-1-identify-human-resource-capacity-needs-to"
    },
    {
      "level": 2,
      "title": "Step 2. Onboard and assign individuals to the identified roles",
      "number": null,
      "page": 44,
      "pageLabel": "35",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-024-step-2-onboard-and-assign-individuals-to-the-ide"
    },
    {
      "level": 2,
      "title": "Step 3. Develop knowledge management plan to enhance skills and capacity in alignment with evolving needs",
      "number": null,
      "page": 44,
      "pageLabel": "35",
      "confidence": 0.85,
      "evidence": [
        "step-label",
        "style"
      ],
      "source": "inferred",
      "section": "sec-025-step-3-develop-knowledge-management-plan-to-enha"
    },
    {
      "level": 1,
      "title": "Leveraging WHO hosted PCMT",
      "number": "06",
      "page": 45,
      "pageLabel": "36",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-026-06-leveraging-who-hosted-pcmt"
    },
    {
      "level": 1,
      "title": "Sharing product master data as a global good",
      "number": "07",
      "page": 48,
      "pageLabel": "39",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-027-07-sharing-product-master-data-as-a-global-good"
    },
    {
      "level": 1,
      "title": "Sharing implementation experiences",
      "number": "08",
      "page": 51,
      "pageLabel": "42",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-028-08-sharing-implementation-experiences"
    },
    {
      "level": 1,
      "title": "References",
      "number": null,
      "page": 55,
      "pageLabel": "46",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-029-references"
    },
    {
      "level": 1,
      "title": "Annexes",
      "number": null,
      "page": 56,
      "pageLabel": "47",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-030-annexes"
    }
  ],
  "sections": [
    {
      "id": "sec-front-matter",
      "number": null,
      "title": "Front matter",
      "level": 1,
      "pageStart": 1,
      "pageEnd": 5,
      "labelStart": "A",
      "labelEnd": "iv",
      "words": 596,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "product catalogue",
          "heading": false
        },
        {
          "term": "product master",
          "heading": false
        },
        {
          "term": "transformation handbook",
          "heading": false
        },
        {
          "term": "digital transformation",
          "heading": false
        },
        {
          "term": "health product",
          "heading": false
        },
        {
          "term": "master data",
          "heading": false
        },
        {
          "term": "creative commons",
          "heading": false
        },
        {
          "term": "suggested citation",
          "heading": false
        }
      ],
      "extract": "Digital transformation handbook for health product catalogue Digital transformation handbook for health product catalogue Digital transformation handbook for health product catalogue ISBN 978-92-4-011619-1 (electronic version) ISBN 978-92-4-011620-7 (print version) © World Health Organization 2025 Some rights reserved. This work is available under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 IGO",
      "extractCut": true,
      "blocks": [
        "library/9789240116191-eng/blocks/prose-sec-front-matter"
      ]
    },
    {
      "id": "sec-000-acknowledgements",
      "number": null,
      "title": "Acknowledgements",
      "level": 1,
      "pageStart": 5,
      "pageEnd": 6,
      "labelStart": "iv",
      "labelEnd": "v",
      "words": 392,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "usaid ghsc-psm",
          "heading": false
        },
        {
          "term": "ramy guirguis",
          "heading": false
        },
        {
          "term": "carl leitner",
          "heading": false
        },
        {
          "term": "usa",
          "heading": false
        },
        {
          "term": "umc",
          "heading": false
        },
        {
          "term": "united states",
          "heading": false
        },
        {
          "term": "jayaprakash",
          "heading": false
        },
        {
          "term": "swaroop",
          "heading": false
        }
      ],
      "extract": "Acknowledgements The World Health Organization (WHO) is grateful for the contributions of many individuals and organizations in the development of this handbook. This handbook was authored by Carl Leitner and Swaroop Jayaprakash of the WHO Department of Digital Health and Innovations (DHI) and Ramy Guirguis of the United States Agency for International Development (USAID). The following individuals (in alphabetical",
      "extractCut": true
    },
    {
      "id": "sec-001-abbreviations",
      "number": null,
      "title": "Abbreviations",
      "level": 1,
      "pageStart": 6,
      "pageEnd": 8,
      "labelStart": "v",
      "labelEnd": "vii",
      "words": 250,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "medicinal products",
          "heading": false
        },
        {
          "term": "product catalog",
          "heading": false
        },
        {
          "term": "regulatory authority",
          "heading": false
        },
        {
          "term": "international classification",
          "heading": false
        },
        {
          "term": "zambia medicines",
          "heading": false
        },
        {
          "term": "abbreviations",
          "heading": true
        },
        {
          "term": "umc",
          "heading": false
        },
        {
          "term": "digital health",
          "heading": false
        }
      ],
      "extract": "Abbreviations AEFI Adverse effects following immunisation AIDC Automatic identification and data capture ATC Anatomical therapeutic chemical classification system DAK Digital adaptation kit DH&I Digital health and interoperability DHSC Digital health supply chain DIIG Digital implementation investment guide eLMIS Electronic logistic management information system FDA Food and Drugs Authority FHIR Fast Healthcare",
      "extractCut": true
    },
    {
      "id": "sec-002-glossary",
      "number": null,
      "title": "Glossary",
      "level": 1,
      "pageStart": 8,
      "pageEnd": 10,
      "labelStart": "vii",
      "labelEnd": "1",
      "words": 616,
      "summary": {
        "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).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "product master",
          "heading": false
        },
        {
          "term": "generic product",
          "heading": false
        },
        {
          "term": "open-source software",
          "heading": false
        },
        {
          "term": "digital transformation",
          "heading": false
        },
        {
          "term": "product information",
          "heading": false
        },
        {
          "term": "master data",
          "heading": false
        },
        {
          "term": "digital system",
          "heading": false
        },
        {
          "term": "open standards",
          "heading": false
        }
      ],
      "extract": "Glossary Data element A unit of data that has a specific and precise meaning. Digitization The process of converting and organizing data from paper records into a digital format for easier entry, storage and retrieval. Digitization is the initial step towards digital transformation.1, 2 Digitalization The process of digitally automating and simplifying processes to streamline individual health programmes and",
      "extractCut": true
    },
    {
      "id": "sec-003-introduction",
      "number": null,
      "title": "Introduction",
      "level": 1,
      "pageStart": 10,
      "pageEnd": 20,
      "labelStart": "1",
      "labelEnd": "11",
      "words": 3128,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "product master",
          "heading": false
        },
        {
          "term": "standardized product",
          "heading": false
        },
        {
          "term": "master data",
          "heading": false
        },
        {
          "term": "product registry",
          "heading": false
        },
        {
          "term": "npc implementations",
          "heading": false
        },
        {
          "term": "chain partners",
          "heading": false
        },
        {
          "term": "health nra",
          "heading": false
        },
        {
          "term": "product code",
          "heading": false
        }
      ],
      "extract": "Health products pass through multiple supply chain partners and processes as they move from manufacturers to end-users. For transactions to be seamless, all stakeholders must consistently identify health products using standardized information. For example, if a country’s central warehouse receives a shipment of vaccines with identifiers that do not match its standardized data, manual reconciliation will be",
      "extractCut": true
    },
    {
      "id": "sec-004-01-establishing-regulatory-policies-to-promote-p",
      "number": "01",
      "title": "Establishing regulatory policies to promote product master data standardization",
      "level": 1,
      "pageStart": 20,
      "pageEnd": 21,
      "labelStart": "11",
      "labelEnd": "12",
      "words": 108,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "product master",
          "heading": true
        },
        {
          "term": "master data",
          "heading": true
        },
        {
          "term": "standardized product",
          "heading": false
        },
        {
          "term": "regulatory",
          "heading": true
        }
      ],
      "extract": "policies to promote product master data standardization Manufacturers and distributors of health products are the source of truth for product master data. Ensuring that manufacturers and distributors consistently provide product master data in a standardized and uniform format is crucial for enabling interoperability and leveraging automation through barcode scanning. Regulatory organizations play a key role in",
      "extractCut": true
    },
    {
      "id": "sec-005-step-1-identify-necessary-regulatory-policies-an",
      "number": null,
      "title": "Step 1. Identify necessary regulatory policies and legislations",
      "level": 2,
      "pageStart": 21,
      "pageEnd": 22,
      "labelStart": "12",
      "labelEnd": "13",
      "words": 200,
      "summary": {
        "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).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "regulatory policies",
          "heading": true
        },
        {
          "term": "legislations",
          "heading": true
        },
        {
          "term": "regulatory authority",
          "heading": false
        },
        {
          "term": "additional regulatory",
          "heading": false
        },
        {
          "term": "current regulations",
          "heading": false
        },
        {
          "term": "master data",
          "heading": false
        },
        {
          "term": "step",
          "heading": true
        }
      ],
      "extract": "policies and legislations STEP 1 INPUTS STEPS RESOURCES OUTPUTS • Existing regulatory policies and legislations Analyse current regulations to determine if they clearly articulate policies for product master data standardization and sharing, in alignment with internationally accepted standards. • Master data guideline template • Product identification and labelling guidance and template • List of additional",
      "extractCut": true
    },
    {
      "id": "sec-006-step-2-develop-the-identified-regulatory-policie",
      "number": null,
      "title": "Step 2. Develop the identified regulatory policies and legislations",
      "level": 2,
      "pageStart": 22,
      "pageEnd": 22,
      "labelStart": "13",
      "labelEnd": "13",
      "words": 198,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "regulatory policies",
          "heading": true
        },
        {
          "term": "legislations",
          "heading": true
        },
        {
          "term": "master data",
          "heading": false
        },
        {
          "term": "regulatory documents",
          "heading": false
        },
        {
          "term": "existing policies",
          "heading": false
        },
        {
          "term": "distributors",
          "heading": false
        },
        {
          "term": "template",
          "heading": false
        }
      ],
      "extract": "and legislations INPUTS STEPS RESOURCES OUTPUTS • List of additional regulatory policies and legislations required Develop the required policies and regulations such as master data guidelines, ensuring they are consistent with both current and emerging regulations concerning data standardization and AIDC. • List of modifications needed for existing policies and legislations • Regulatory policies and guidelines must",
      "extractCut": true
    },
    {
      "id": "sec-007-step-3-coordinate-reviews-and-approvals-of-the-d",
      "number": null,
      "title": "Step 3. Coordinate reviews and approvals of the drafted policies",
      "level": 2,
      "pageStart": 22,
      "pageEnd": 23,
      "labelStart": "13",
      "labelEnd": "14",
      "words": 79,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "policies",
          "heading": true
        },
        {
          "term": "legislations",
          "heading": false
        },
        {
          "term": "approvals",
          "heading": true
        }
      ],
      "extract": "INPUTS STEPS RESOURCES OUTPUTS • Master data related policies and legislations Evaluate the newly developed and the revised policies and legislations led by the NRA in collaboration with primary stakeholders like the Ministry of Health, central and regional warehouses, procurement entities, manufacturers and distributors and operational leaders • Approved master data policies and legislations Ensure that all",
      "extractCut": true
    },
    {
      "id": "sec-008-step-4-publish-and-enforce-the-approved-regulato",
      "number": null,
      "title": "Step 4. Publish and enforce the approved regulatory policies to promote product master data standardization",
      "level": 2,
      "pageStart": 23,
      "pageEnd": 24,
      "labelStart": "14",
      "labelEnd": "15",
      "words": 185,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "product master",
          "heading": true
        },
        {
          "term": "master data",
          "heading": true
        },
        {
          "term": "data policies",
          "heading": true
        },
        {
          "term": "publish",
          "heading": true
        },
        {
          "term": "legislations",
          "heading": false
        },
        {
          "term": "regulatory",
          "heading": true
        },
        {
          "term": "approved",
          "heading": true
        }
      ],
      "extract": "to promote product master data standardization INPUTS STEPS RESOURCES OUTPUTS • Approved master data policies and legislations Publish the approved policy document • Endorsed master data policies and legislations Define mechanisms to institutionalize and monitor compliance of the policies Publish the policy document POTENTIAL RISKS MITIGATION Manufacturers’ poor adherence to regulations. • Assess the situation to",
      "extractCut": true
    },
    {
      "id": "sec-009-02-instituting-data-management-and-governance-po",
      "number": "02",
      "title": "Instituting data management and governance policies",
      "level": 1,
      "pageStart": 24,
      "pageEnd": 25,
      "labelStart": "15",
      "labelEnd": "16",
      "words": 96,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "management policies",
          "heading": true
        },
        {
          "term": "data management",
          "heading": true
        },
        {
          "term": "integrity",
          "heading": false
        },
        {
          "term": "governance",
          "heading": true
        }
      ],
      "extract": "management and governance policies For effective use of data in operations, analysis, and decision-making, the integrity and quality of data must be consistently and continuously maintained. Establishing data management policies to maintain master data structures, definitions, and operational procedures is crucial for sustaining data integrity and quality. Data management policies should ensure adherence to",
      "extractCut": true
    },
    {
      "id": "sec-010-step-1-define-product-master-data-management-pro",
      "number": null,
      "title": "Step 1. Define product master data management procedures",
      "level": 2,
      "pageStart": 25,
      "pageEnd": 27,
      "labelStart": "16",
      "labelEnd": "18",
      "words": 588,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "product master",
          "heading": true
        },
        {
          "term": "master data",
          "heading": true
        },
        {
          "term": "data management",
          "heading": true
        },
        {
          "term": "management procedures",
          "heading": true
        },
        {
          "term": "maintain master",
          "heading": false
        },
        {
          "term": "data owner",
          "heading": false
        },
        {
          "term": "data custodian",
          "heading": false
        },
        {
          "term": "data harmonization",
          "heading": false
        }
      ],
      "extract": "STEP 1 INPUTS STEPS RESOURCES OUTPUTS • Published master data policies and legislations Begin by identifying and analyzing the existing challenges in master data management and their impact on interoperability across systems and organizations. This includes: • Reviewing current product coding schemes and data structures. • Assessing the number of product master data sets maintained across different systems and",
      "extractCut": true
    },
    {
      "id": "sec-011-step-2-define-coding-scheme-data-definitions-and",
      "number": null,
      "title": "Step 2. Define coding scheme, data definitions and structures to organize and maintain product master data",
      "level": 2,
      "pageStart": 27,
      "pageEnd": 31,
      "labelStart": "18",
      "labelEnd": "22",
      "words": 1401,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "product master",
          "heading": true
        },
        {
          "term": "product coding",
          "heading": true
        },
        {
          "term": "master data",
          "heading": true
        },
        {
          "term": "coding scheme",
          "heading": true
        },
        {
          "term": "data structures",
          "heading": true
        },
        {
          "term": "product packaging",
          "heading": false
        },
        {
          "term": "medicinal product",
          "heading": false
        },
        {
          "term": "trade item",
          "heading": false
        }
      ],
      "extract": "to organize and maintain product master data INPUTS STEPS RESOURCES OUTPUTS • Data harmonization activities plan Conduct data harmonization activities such as establishing a standardized coding scheme, master data definitions and structures* to organize and maintain master data consistently and persistently • Master data management procedures including master data governance policies • Data harmonization activities",
      "extractCut": true
    },
    {
      "id": "sec-012-step-3-define-data-use-policies-and-data-sharing",
      "number": null,
      "title": "Step 3. Define data use policies and data sharing mechanisms to support interoperability",
      "level": 2,
      "pageStart": 31,
      "pageEnd": 32,
      "labelStart": "22",
      "labelEnd": "23",
      "words": 64,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "characteristic association",
          "heading": false
        },
        {
          "term": "name characteristic",
          "heading": false
        },
        {
          "term": "trade item",
          "heading": false
        }
      ],
      "extract": "to support interoperability STEP 3 GENERIC PRODUCT identifier MR001 description name characteristic association TRADE ITEM (MFR B) Tertiary (Pallet) identifier 18901415202906 description name characteristic association TRADE ITEM (MFR B) Tertiary (Case) identifier 08901415202908 description name characteristic association quantity 100 TRADE ITEM (MFR A) identifier 17801415202675 description name characteristic",
      "extractCut": true
    },
    {
      "id": "sec-013-step-4-institutionalise-product-master-data-gove",
      "number": null,
      "title": "Step 4. Institutionalise product master data governance policies and procedures.",
      "level": 2,
      "pageStart": 32,
      "pageEnd": 33,
      "labelStart": "23",
      "labelEnd": "24",
      "words": 251,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "master data",
          "heading": true
        },
        {
          "term": "product master",
          "heading": true
        },
        {
          "term": "data governance",
          "heading": true
        },
        {
          "term": "governance policies",
          "heading": true
        },
        {
          "term": "coding schemes",
          "heading": false
        },
        {
          "term": "data structures",
          "heading": false
        },
        {
          "term": "governance group",
          "heading": false
        },
        {
          "term": "data attributes",
          "heading": false
        }
      ],
      "extract": "policies and procedures. STEP 4 POTENTIAL RISKS MITIGATION The variety and volume of data attributes raise concerns regarding privacy, confidentiality, and data sensitivity. These concerns can make data sources reluctant to share information with multiple and diverse stakeholders. To address these concerns, procedures and systems should be developed to categorize data attributes based on their level of sensitivity.",
      "extractCut": true
    },
    {
      "id": "sec-014-step-5-define-short--and-long-term-strategies-to",
      "number": null,
      "title": "Step 5. Define short- and long-term strategies to source standardized product master data",
      "level": 2,
      "pageStart": 33,
      "pageEnd": 34,
      "labelStart": "24",
      "labelEnd": "25",
      "words": 326,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "product master",
          "heading": true
        },
        {
          "term": "master data",
          "heading": true
        },
        {
          "term": "standardized master",
          "heading": true
        },
        {
          "term": "source master",
          "heading": true
        },
        {
          "term": "sourcing master",
          "heading": false
        },
        {
          "term": "data sharing",
          "heading": false
        },
        {
          "term": "data attributes",
          "heading": false
        },
        {
          "term": "data coding",
          "heading": false
        }
      ],
      "extract": "standardized product master data INPUTS STEPS RESOURCES OUTPUTS • Endorsed master data policies and legislations (from chapter 1) Identify challenges with sourcing master data, such as incompleteness, data quality, data availability, awareness etc. Define a short and medium-term strategy to source master data, while considering and addressing the identified challenges. • Data sharing and data use policies • For",
      "extractCut": true
    },
    {
      "id": "sec-015-03-deploying-appropriate-technology-to-manage-pr",
      "number": "03",
      "title": "Deploying appropriate technology to manage product master data",
      "level": 1,
      "pageStart": 34,
      "pageEnd": 35,
      "labelStart": "25",
      "labelEnd": "26",
      "words": 6,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [],
      "extract": "technology to manage product master data",
      "extractCut": false
    },
    {
      "id": "sec-016-step-1-define-system-requirements-for-the-npc-to",
      "number": null,
      "title": "Step 1. Define system requirements for the NPC tool",
      "level": 2,
      "pageStart": 35,
      "pageEnd": 36,
      "labelStart": "26",
      "labelEnd": "27",
      "words": 219,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "npc tool",
          "heading": true
        },
        {
          "term": "system requirements",
          "heading": true
        },
        {
          "term": "product master",
          "heading": false
        },
        {
          "term": "master data",
          "heading": false
        },
        {
          "term": "coding schemes",
          "heading": false
        },
        {
          "term": "data sharing",
          "heading": false
        },
        {
          "term": "technology tool",
          "heading": false
        },
        {
          "term": "data management",
          "heading": false
        }
      ],
      "extract": "across various health and supply chain systems to enable uniform product identification. It is essential that this data is organized and managed consistently, with minimal manual intervention, to ensure data quality and integrity. Adopting a suitable technology tool supports the ongoing management of product master data while maintaining consistent quality and compliance with defined standards. A widely used term",
      "extractCut": true
    },
    {
      "id": "sec-017-step-2-identify-technology-options-and-select-th",
      "number": null,
      "title": "Step 2. Identify technology options and select the appropriate tool",
      "level": 2,
      "pageStart": 36,
      "pageEnd": 36,
      "labelStart": "27",
      "labelEnd": "27",
      "words": 118,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "appropriate tool",
          "heading": true
        },
        {
          "term": "npc",
          "heading": false
        },
        {
          "term": "pcmt",
          "heading": false
        },
        {
          "term": "options",
          "heading": true
        }
      ],
      "extract": "INPUTS STEPS RESOURCES OUTPUTS • Approved functional and non-functional system requirements for NPC. Conduct market research activities such as Request for information (RFI) to explore technology options for an appropriate tool for NPC. • Assess existing digital tools, such as enterprise resource planning applications, to determine if they fulfil NPC system requirements before deciding to invest in a new software.",
      "extractCut": true
    },
    {
      "id": "sec-018-step-3-prepare-a-plan-to-implement-the-npc-tool",
      "number": null,
      "title": "Step 3. Prepare a plan to implement the NPC tool and integrate with other systems to share standardized data",
      "level": 2,
      "pageStart": 36,
      "pageEnd": 37,
      "labelStart": "27",
      "labelEnd": "28",
      "words": 67,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "npc",
          "heading": true
        },
        {
          "term": "npc implementation",
          "heading": false
        },
        {
          "term": "plan",
          "heading": true
        }
      ],
      "extract": "with other systems to share standardized data INPUTS STEPS RESOURCES OUTPUTS • Approved functional and non-functional system requirements for NPC. Develop a detailed implementation plan to design, configure and deploy the chosen tool for NPC. Review the plan with relevant stakeholders and initiate the implementation project. • Selection of an appropriate technology tool for NPC. • NPC Implementation plan template •",
      "extractCut": true
    },
    {
      "id": "sec-019-step-4-design-develop-and-deploy-the-npc-tool",
      "number": null,
      "title": "Step 4. Design, develop and deploy the NPC tool",
      "level": 2,
      "pageStart": 37,
      "pageEnd": 39,
      "labelStart": "28",
      "labelEnd": "30",
      "words": 356,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "npc tool",
          "heading": true
        },
        {
          "term": "npc system",
          "heading": false
        },
        {
          "term": "product master",
          "heading": false
        },
        {
          "term": "master data",
          "heading": false
        },
        {
          "term": "non-functional system",
          "heading": false
        },
        {
          "term": "standardized product",
          "heading": false
        },
        {
          "term": "change management",
          "heading": false
        },
        {
          "term": "system requirements",
          "heading": false
        }
      ],
      "extract": "INPUTS STEPS RESOURCES OUTPUTS • NPC Implementation project plan. Design the system and necessary configurations to fulfil all functional and non-functional requirements. • Approved functional and non-functional system requirements for NPC. Review the design with relevant stakeholders and facilitate design approvals. Develop the system and required configurations of the NPC tool and build integrations with other",
      "extractCut": true
    },
    {
      "id": "sec-020-step-1-develop-a-change-management-plan-to-insti",
      "number": null,
      "title": "Step 1. Develop a change management plan to institutionalise use of NPC",
      "level": 2,
      "pageStart": 39,
      "pageEnd": 40,
      "labelStart": "30",
      "labelEnd": "31",
      "words": 279,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "product master",
          "heading": false
        },
        {
          "term": "master data",
          "heading": false
        },
        {
          "term": "standardized product",
          "heading": false
        },
        {
          "term": "gtins",
          "heading": false
        },
        {
          "term": "npc",
          "heading": true
        },
        {
          "term": "trade item",
          "heading": false
        },
        {
          "term": "local identifier",
          "heading": false
        },
        {
          "term": "data across",
          "heading": false
        }
      ],
      "extract": "to institutionalise use of NPC INPUTS STEPS RESOURCES OUTPUTS • Standardized master data coding schemes and structures. Identify all the systems and processes that need standardized product master data. Identify and define the specific changes needed to institutionalize the use of standardized product master data across people, processes, and systems. These may include: • Master data management procedures including",
      "extractCut": true
    },
    {
      "id": "sec-021-step-2-define-sops-to-collect-organize-and-manag",
      "number": null,
      "title": "Step 2. Define SOPs to collect, organize and manage product master data",
      "level": 2,
      "pageStart": 40,
      "pageEnd": 42,
      "labelStart": "31",
      "labelEnd": "33",
      "words": 411,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "product master",
          "heading": true
        },
        {
          "term": "master data",
          "heading": true
        },
        {
          "term": "define sops",
          "heading": true
        },
        {
          "term": "child gtin",
          "heading": false
        },
        {
          "term": "standardized product",
          "heading": false
        },
        {
          "term": "packaging hierarchies",
          "heading": false
        },
        {
          "term": "data attributes",
          "heading": false
        },
        {
          "term": "mfr",
          "heading": false
        }
      ],
      "extract": "National Product Code Description Dosage Form Route of Administration GTIN 58904093825793 58904093825700 Country Trade Item Identifier 58904093825793 58904093825700 Child GTIN 58904093825700 58904093825600 Child SKU 58904093825700 58904093825600 Child Quantity 100 10 Quantity of Eaches 3000 3000 Shelf Life 670 670 Manufacturer MFR001 MFR001 Country of Origin IN IN NPC01101001 Lamivudine 50 Mg tablet TA Oral GTIN",
      "extractCut": true
    },
    {
      "id": "sec-022-05-building-capacity-to-sustainably-manage-npc",
      "number": "05",
      "title": "Building capacity to sustainably manage NPC",
      "level": 1,
      "pageStart": 42,
      "pageEnd": 43,
      "labelStart": "33",
      "labelEnd": "34",
      "words": 4,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [],
      "extract": "to sustainably manage NPC",
      "extractCut": false
    },
    {
      "id": "sec-023-step-1-identify-human-resource-capacity-needs-to",
      "number": null,
      "title": "Step 1. Identify human resource capacity needs to support NPC",
      "level": 2,
      "pageStart": 43,
      "pageEnd": 44,
      "labelStart": "34",
      "labelEnd": "35",
      "words": 263,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "npc",
          "heading": true
        },
        {
          "term": "human resource",
          "heading": true
        },
        {
          "term": "resource capacity",
          "heading": true
        },
        {
          "term": "product master",
          "heading": false
        },
        {
          "term": "master data",
          "heading": false
        },
        {
          "term": "catalogue manager",
          "heading": false
        },
        {
          "term": "resource management",
          "heading": false
        },
        {
          "term": "management processes",
          "heading": false
        }
      ],
      "extract": "systems depends on the availability of human resources with the appropriate skill sets to operate the systems and execute the processes. In addition to technical skills, the workforce must also understand the purpose of improved systems and processes, along with the benefits they bring to their daily work. Human resource capacity is a critical component for the successful implementation and adoption of global",
      "extractCut": true
    },
    {
      "id": "sec-024-step-2-onboard-and-assign-individuals-to-the-ide",
      "number": null,
      "title": "Step 2. Onboard and assign individuals to the identified roles",
      "level": 2,
      "pageStart": 44,
      "pageEnd": 44,
      "labelStart": "35",
      "labelEnd": "35",
      "words": 75,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "roles",
          "heading": true
        },
        {
          "term": "human resource",
          "heading": false
        },
        {
          "term": "fill",
          "heading": false
        }
      ],
      "extract": "INPUTS STEPS RESOURCES OUTPUTS • List of roles necessary to support NPC and product master data management processes. Develop budgets and identify funding sources to fill the identified roles and future human resource needs. • Job descriptions for each role. • Human resource management plan. • Budget for human resource capacity needs. • Onboarded resources. Once sufficient funding has been identified, recruit and",
      "extractCut": true
    },
    {
      "id": "sec-025-step-3-develop-knowledge-management-plan-to-enha",
      "number": null,
      "title": "Step 3. Develop knowledge management plan to enhance skills and capacity in alignment with evolving needs",
      "level": 2,
      "pageStart": 44,
      "pageEnd": 45,
      "labelStart": "35",
      "labelEnd": "36",
      "words": 208,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "management plan",
          "heading": true
        },
        {
          "term": "product master",
          "heading": false
        },
        {
          "term": "knowledge management",
          "heading": true
        },
        {
          "term": "master data",
          "heading": false
        },
        {
          "term": "capacity",
          "heading": true
        },
        {
          "term": "npc",
          "heading": false
        },
        {
          "term": "job descriptions",
          "heading": false
        },
        {
          "term": "management processes",
          "heading": false
        }
      ],
      "extract": "and capacity in alignment with evolving needs INPUTS STEPS RESOURCES OUTPUTS • List of roles necessary to support the NPC and product master data management processes. Develop budgets and identify funding sources to fill the identified roles and future human resource needs. • Job descriptions. • TOR for the Master Data Governance Group. Once sufficient funding has been identified, recruit and train people with",
      "extractCut": true
    },
    {
      "id": "sec-026-06-leveraging-who-hosted-pcmt",
      "number": "06",
      "title": "Leveraging WHO hosted PCMT",
      "level": 1,
      "pageStart": 45,
      "pageEnd": 48,
      "labelStart": "36",
      "labelEnd": "39",
      "words": 486,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "hosted pcmt",
          "heading": true
        },
        {
          "term": "who-hosted pcmt",
          "heading": false
        },
        {
          "term": "product catalogues",
          "heading": false
        },
        {
          "term": "catalogue country",
          "heading": false
        },
        {
          "term": "global catalogue",
          "heading": false
        },
        {
          "term": "approve reject",
          "heading": false
        },
        {
          "term": "product master",
          "heading": false
        },
        {
          "term": "product information",
          "heading": false
        }
      ],
      "extract": "WHO-hosted PCMT Countries planning to implement a digital tool to manage product master data may consider using the WHO– hosted PCMT as an initial option. This tool can serve as a starting point to manage national health product master data while countries build the necessary technical resources and capacity to implement an in-country– hosted solution. Alternatively, countries may continue using the WHO-hosted PCMT",
      "extractCut": true
    },
    {
      "id": "sec-027-07-sharing-product-master-data-as-a-global-good",
      "number": "07",
      "title": "Sharing product master data as a global good",
      "level": 1,
      "pageStart": 48,
      "pageEnd": 51,
      "labelStart": "39",
      "labelEnd": "42",
      "words": 348,
      "summary": {
        "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).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "product master",
          "heading": true
        },
        {
          "term": "master data",
          "heading": true
        },
        {
          "term": "sharing data",
          "heading": true
        },
        {
          "term": "product catalogue",
          "heading": false
        },
        {
          "term": "global catalogue",
          "heading": false
        },
        {
          "term": "catalogue country",
          "heading": false
        },
        {
          "term": "global repository",
          "heading": false
        },
        {
          "term": "product information",
          "heading": false
        }
      ],
      "extract": "data as a global good Sharing health product master data with a global repository—such as the WHO Global Product Catalogue— holds significant value and importance as a global good for several reasons: • Access to accurate information: A centralized repository enables health professionals and organizations worldwide to access accurate and up-to-date information on health products. • Standardization: A global",
      "extractCut": true
    },
    {
      "id": "sec-028-08-sharing-implementation-experiences",
      "number": "08",
      "title": "Sharing implementation experiences",
      "level": 1,
      "pageStart": 51,
      "pageEnd": 55,
      "labelStart": "42",
      "labelEnd": "46",
      "words": 1478,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "gtins designate",
          "heading": false
        },
        {
          "term": "npc quantity",
          "heading": false
        },
        {
          "term": "npc configured",
          "heading": false
        },
        {
          "term": "gtins issued",
          "heading": false
        },
        {
          "term": "npc data",
          "heading": false
        },
        {
          "term": "catalog manager",
          "heading": false
        },
        {
          "term": "integrate npc",
          "heading": false
        },
        {
          "term": "npc hosted",
          "heading": false
        }
      ],
      "extract": "implementation experiences COUNTRY: RWANDA REGULATORY DATA TECHNOLOGY PEOPLE CHANGE MANAGEMENT Status • Regulations governing the implementation of identification data capture and data sharing for traceability of pharmaceutical product • Guidelines for identification and labelling of pharmaceutical products published in Aug 2022 • Guidelines for product and location master data sharing published in Aug 2022 • The",
      "extractCut": true
    },
    {
      "id": "sec-029-references",
      "number": null,
      "title": "References",
      "level": 1,
      "pageStart": 55,
      "pageEnd": 56,
      "labelStart": "46",
      "labelEnd": "47",
      "words": 286,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "accessed january",
          "heading": false
        },
        {
          "term": "yokogawa electric",
          "heading": false
        },
        {
          "term": "electric corporation",
          "heading": false
        },
        {
          "term": "digital transformation",
          "heading": false
        },
        {
          "term": "com library",
          "heading": false
        },
        {
          "term": "smart guidelines",
          "heading": false
        },
        {
          "term": "digitization",
          "heading": false
        },
        {
          "term": "library resources",
          "heading": false
        }
      ],
      "extract": "References 1. Yokogawa Electric Corporation. The differences between digitization, digitalization and digital transformation in manufacturing. (https:// www.yokogawa.com/library/resources/white-papers/the-differences- between-digitization-digitalization-and-digital-transformation-in- manufacturing/, accessed 10 January 2020). 2. Gartner. Definition of Digitization. (https://www.gartner.com/en/",
      "extractCut": true
    },
    {
      "id": "sec-030-annexes",
      "number": null,
      "title": "Annexes",
      "level": 1,
      "pageStart": 56,
      "pageEnd": 62,
      "labelStart": "47",
      "labelEnd": "53",
      "words": 1957,
      "summary": {
        "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.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "contracted temporary",
          "heading": false
        },
        {
          "term": "business requirements",
          "heading": false
        },
        {
          "term": "scripting tools",
          "heading": false
        },
        {
          "term": "temporary knowledge",
          "heading": false
        },
        {
          "term": "permanent experience",
          "heading": false
        },
        {
          "term": "vmware experience",
          "heading": false
        },
        {
          "term": "software tools",
          "heading": false
        },
        {
          "term": "troubleshooting skills",
          "heading": false
        }
      ],
      "extract": "Annex 1. Principles for Digital Development Understand the existing ecosystem Trust starts with a thorough understanding of the dynamic cultural, social and economic context in which you are operating. Share, reuse, and improve Build on what works, improve what works, and share so that others can do the same. Design with people Good design starts and ends with people that will manage, use, and ideally benefit from a",
      "extractCut": true
    }
  ],
  "checks": {
    "tocAlignment": {
      "listed_not_found": {
        "count": 1,
        "items": [
          "Creating protocols for managing change"
        ]
      },
      "found_not_listed": {
        "count": 0,
        "items": []
      },
      "page_mismatch": {
        "count": 0,
        "items": []
      }
    },
    "figureSequenceGaps": [],
    "pageLabelConflicts": {
      "count": 0,
      "items": []
    }
  },
  "withheld": false,
  "keywords": [
    {
      "term": "product master",
      "heading": true
    },
    {
      "term": "master data",
      "heading": true
    },
    {
      "term": "standardized master",
      "heading": true
    },
    {
      "term": "outputs master",
      "heading": false
    },
    {
      "term": "define master",
      "heading": true
    },
    {
      "term": "structures master",
      "heading": true
    },
    {
      "term": "source master",
      "heading": true
    },
    {
      "term": "npc data",
      "heading": true
    },
    {
      "term": "approved master",
      "heading": true
    },
    {
      "term": "maintain master",
      "heading": true
    },
    {
      "term": "sourcing master",
      "heading": false
    },
    {
      "term": "location master",
      "heading": false
    }
  ],
  "pageLabels": [
    {
      "physical": 1,
      "label": "A",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 2,
      "label": "i",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 3,
      "label": "ii",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 4,
      "label": "iii",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 5,
      "label": "iv",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 6,
      "label": "v",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 7,
      "label": "vi",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 8,
      "label": "vii",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 9,
      "label": "viii",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 10,
      "label": "1",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 11,
      "label": "2",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 12,
      "label": "3",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 13,
      "label": "4",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 14,
      "label": "5",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 15,
      "label": "6",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 16,
      "label": "7",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 17,
      "label": "8",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 18,
      "label": "9",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 19,
      "label": "10",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 20,
      "label": "11",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 21,
      "label": "12",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 22,
      "label": "13",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 23,
      "label": "14",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 24,
      "label": "15",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 25,
      "label": "16",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 26,
      "label": "17",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 27,
      "label": "18",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 28,
      "label": "19",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 29,
      "label": "20",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 30,
      "label": "21",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 31,
      "label": "22",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 32,
      "label": "23",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 33,
      "label": "24",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 34,
      "label": "25",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 35,
      "label": "26",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 36,
      "label": "27",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 37,
      "label": "28",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 38,
      "label": "29",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 39,
      "label": "30",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 40,
      "label": "31",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 41,
      "label": "32",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 42,
      "label": "33",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 43,
      "label": "34",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 44,
      "label": "35",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 45,
      "label": "36",
      "source": "pdf-labels",
      "confidence": 1
    },
    {
      "physical": 46,
      "label": "37",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 47,
      "label": "38",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 48,
      "label": "39",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 49,
      "label": "40",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 50,
      "label": "41",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 51,
      "label": "42",
      "source": "pdf-labels",
      "confidence": 1
    },
    {
      "physical": 52,
      "label": "43",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 53,
      "label": "44",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 54,
      "label": "45",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 55,
      "label": "46",
      "source": "pdf-labels",
      "confidence": 1
    },
    {
      "physical": 56,
      "label": "47",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 57,
      "label": "48",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 58,
      "label": "49",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 59,
      "label": "50",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 60,
      "label": "51",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 61,
      "label": "52",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 62,
      "label": "53",
      "source": "pdf-labels",
      "confidence": 0.7
    }
  ],
  "figures": [
    {
      "kind": "figure",
      "number": "1",
      "title": "Product master data",
      "page": 10,
      "pageLabel": "1",
      "confidence": 0.7,
      "evidence": [
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "2",
      "title": "Importance of product master data",
      "page": 11,
      "pageLabel": "2",
      "confidence": 0.7,
      "evidence": [
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "3",
      "title": "Impact of inconsistent product information",
      "page": 12,
      "pageLabel": "3",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "4",
      "title": "Planning and implementing a digital health enterprise: phases, steps and resources",
      "page": 13,
      "pageLabel": "4",
      "confidence": 0.7,
      "evidence": [
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "5",
      "title": "WHO SMART Guidelines Approach",
      "page": 14,
      "pageLabel": "5",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "6",
      "title": "Example of an Antenatal Care Business clinical workflow with highlighted connections to supply chain",
      "page": 15,
      "pageLabel": "6",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "7",
      "title": "Digital health supply chain architecture framework",
      "page": 16,
      "pageLabel": "7",
      "confidence": 0.7,
      "evidence": [
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "8",
      "title": "Linkage across classifications, generic products and trade items",
      "page": 28,
      "pageLabel": "19",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "9",
      "title": "Relationship between generic product, trade item and regulated trade item",
      "page": 29,
      "pageLabel": "20",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "10",
      "title": "Product packaging hierarchy",
      "page": 30,
      "pageLabel": "21",
      "confidence": 0.7,
      "evidence": [
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "11",
      "title": "Example of packaging variations across manufacturers",
      "page": 30,
      "pageLabel": "21",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "12",
      "title": "Mapping across product packaging hierarchy using FHIR resource",
      "page": 31,
      "pageLabel": "22",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "13",
      "title": "Transitional approach to adopting globally unique trade item numbers",
      "page": 40,
      "pageLabel": "31",
      "confidence": 0.7,
      "evidence": [
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "14",
      "title": "Illustration of how countries can leverage WHO hosted PCMT",
      "page": 46,
      "pageLabel": "37",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "15",
      "title": "Illustration of how countries can share data with the WHO hosted PCMT",
      "page": 50,
      "pageLabel": "41",
      "confidence": 0.7,
      "evidence": [
        "in-sequence",
        "graphic"
      ]
    }
  ],
  "images": [
    {
      "id": "vfig-p010",
      "file": "figures/vfig-p010.png",
      "page": 10,
      "shows": [
        "1"
      ],
      "narratives": {
        "en": "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."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p011",
      "file": "figures/vfig-p011.png",
      "page": 11,
      "shows": [
        "2"
      ],
      "narratives": {
        "en": "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."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p012",
      "file": "figures/vfig-p012.png",
      "page": 12,
      "shows": [
        "3"
      ],
      "narratives": {
        "en": "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."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p013",
      "file": "figures/vfig-p013.png",
      "page": 13,
      "shows": [
        "4"
      ],
      "narratives": {
        "en": "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."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p014",
      "file": "figures/vfig-p014.png",
      "page": 14,
      "shows": [
        "5"
      ],
      "narratives": {
        "en": "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."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p015",
      "file": "figures/vfig-p015.png",
      "page": 15,
      "shows": [
        "6"
      ],
      "narratives": {
        "en": "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."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p016",
      "file": "figures/vfig-p016.png",
      "page": 16,
      "shows": [
        "7"
      ],
      "narratives": {
        "en": "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)."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p028",
      "file": "figures/vfig-p028.png",
      "page": 28,
      "shows": [
        "8"
      ],
      "narratives": {
        "en": "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)."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p029",
      "file": "figures/vfig-p029.png",
      "page": 29,
      "shows": [
        "9"
      ],
      "narratives": {
        "en": "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."
      },
      "state": "draft"
    },
    {
      "id": "img-p030-1",
      "file": "images/img-p030-1.png",
      "page": 30,
      "narratives": {
        "en": "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.",
        "fr": "Fig. 10, « Hiérarchie des emballages de produits » (Product packaging hierarchy, source : GS1.org), dans la section consacrée à l'instauration de politiques de gestion et de gouvernance des données. Elle est représentée sous la forme d'un escalier à quatre marches grises portant chacune des illustrations d'emballages. La marche supérieure, intitulée PRIMAIRE (PRIMARY), montre des articles individuels tels que des flacons, une bouteille, des seringues sous blister, une plaquette thermoformée et un instrument sous emballage stérile. La marche suivante, SECONDAIRE (SECONDARY), montre des boîtes et des cartons contenant ces articles ; la troisième, SECONDAIRE OU TERTIAIRE (SECONDARY OR TERTIARY), montre des cartons ouverts et une rangée de boîtes conditionnées ; et la marche inférieure, TERTIAIRE (TERTIARY), montre des caisses d'expédition et une palette de boîtes filmée.",
        "es": "Fig. 10, «Jerarquía de embalaje de productos» (Product packaging hierarchy, fuente: GS1.org), en la sección sobre el establecimiento de políticas de gestión y gobernanza de datos. Está dibujada como una escalera de cuatro peldaños grises, cada uno con ilustraciones de envases y embalajes. El peldaño superior, etiquetado PRIMARIO (PRIMARY), muestra artículos individuales como viales, un frasco, jeringas en blísteres, una tira blíster y un instrumento en envase estéril. El siguiente peldaño, SECUNDARIO (SECONDARY), muestra cajas y estuches que contienen esos artículos; el tercero, SECUNDARIO O TERCIARIO (SECONDARY OR TERTIARY), muestra cajas abiertas y una fila de paquetes en cajas; y el peldaño inferior, TERCIARIO (TERTIARY), muestra cajas de envío y un palé de cajas envuelto en película retráctil.",
        "ar": "الشكل 10، «التسلسل الهرمي لتغليف المنتجات» (Product packaging hierarchy، المصدر: GS1.org)، في القسم الخاص بإرساء سياسات إدارة البيانات وحوكمتها. وقد رُسم على هيئة سلّم مكوّن من أربع درجات رمادية تحمل كل منها رسوماً توضيحية للتغليف. وتُظهر الدرجة العليا، المعنونة «الأولي» (PRIMARY)، مفردات فردية مثل القوارير، وزجاجة، ومحاقن في عبوات نفطية (بليستر)، وشريط بليستر، وأداة في غلاف معقم. وتُظهر الدرجة التالية، «الثانوي» (SECONDARY)، عُلباً وكراتين تحتوي على تلك المفردات؛ وتُظهر الدرجة الثالثة، «الثانوي أو الثالثي» (SECONDARY OR TERTIARY)، كراتين مفتوحة وصفاً من العبوات المعلبة؛ أما الدرجة السفلى، «الثالثي» (TERTIARY)، فتُظهر صناديق شحن ومنصة نقالة (طبلية) من الصناديق المغلفة بغشاء انكماشي.",
        "ru": "Рис. 10, «Иерархия упаковки продукции» (Product packaging hierarchy, источник: GS1.org), в разделе о внедрении политик управления данными и руководства ими. Диаграмма изображена в виде лестницы из четырех серых ступеней, на каждой из которых показаны иллюстрации упаковки. На верхней ступени с подписью ПЕРВИЧНАЯ (PRIMARY) показаны отдельные изделия: флаконы, бутылочка, шприцы в блистерных упаковках, блистерная пластина и стерильно упакованный инструмент. На следующей ступени — ВТОРИЧНАЯ (SECONDARY) — показаны коробки и пачки, содержащие эти изделия; на третьей — ВТОРИЧНАЯ ИЛИ ТРЕТИЧНАЯ (SECONDARY OR TERTIARY) — открытые картонные коробки и ряд упакованных коробок; а на нижней ступени — ТРЕТИЧНАЯ (TERTIARY) — транспортные ящики и обтянутый термоусадочной пленкой поддон с коробками.",
        "zh": "图 10，“产品包装层级”（Product packaging hierarchy，来源：GS1.org），位于建立数据管理与治理政策章节中。该图绘制为四级灰色阶梯，每级阶梯上展示相应的包装插图。最上一级标为“一级包装”（PRIMARY），展示西林瓶、药瓶、泡罩包装注射器、泡罩板和无菌包装器械等单件物品；下一级“二级包装”（SECONDARY）展示装有这些物品的药盒与纸盒；第三级“二级或三级包装”（SECONDARY OR TERTIARY）展示打开的纸箱和一排盒装包装；最下一级“三级包装”（TERTIARY）展示运输箱和缠绕收缩膜的托盘箱。"
      },
      "state": "draft"
    },
    {
      "id": "vfig-p030",
      "file": "figures/vfig-p030.png",
      "page": 30,
      "shows": [
        "10",
        "11"
      ],
      "narratives": {
        "en": "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."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p031",
      "file": "figures/vfig-p031.png",
      "page": 31,
      "shows": [
        "12"
      ],
      "narratives": {
        "en": "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."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p040",
      "file": "figures/vfig-p040.png",
      "page": 40,
      "shows": [
        "13"
      ],
      "narratives": {
        "en": "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."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p046",
      "file": "figures/vfig-p046.png",
      "page": 46,
      "shows": [
        "14"
      ],
      "narratives": {
        "en": "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."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p050",
      "file": "figures/vfig-p050.png",
      "page": 50,
      "shows": [
        "15"
      ],
      "narratives": {
        "en": "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."
      },
      "state": "draft"
    }
  ],
  "tables": [
    {
      "label": "Table 1",
      "caption": "",
      "pages": [
        7
      ],
      "columns": [
        {
          "titles": "PCMT"
        },
        {
          "titles": "Product catalog m"
        }
      ],
      "rows": [
        [
          "",
          ""
        ],
        [
          "RFP",
          "Request for propo"
        ],
        [
          "",
          ""
        ],
        [
          "RFQ",
          "Request for quote"
        ],
        [
          "",
          ""
        ],
        [
          "RMS",
          "Rwanda Medical S"
        ],
        [
          "",
          ""
        ],
        [
          "SCISMM",
          "Supply chain info"
        ],
        [
          "",
          ""
        ],
        [
          "SMART",
          "Standards-based,"
        ],
        [
          "",
          ""
        ],
        [
          "SOP",
          "Standard operatin"
        ],
        [
          "",
          ""
        ],
        [
          "SWG",
          "Small working gro"
        ],
        [
          "",
          ""
        ],
        [
          "TOR",
          "Terms of referenc"
        ],
        [
          "",
          ""
        ],
        [
          "TSS",
          "Target Software S"
        ],
        [
          "",
          ""
        ],
        [
          "UAT",
          "User acceptance t"
        ],
        [
          "",
          ""
        ],
        [
          "UMC",
          "Uppsala Monitori"
        ],
        [
          "",
          ""
        ],
        [
          "USAID",
          "United States Age"
        ],
        [
          "",
          ""
        ],
        [
          "USAID GHSC-PSM",
          "USAID Global Hea"
        ],
        [
          "",
          ""
        ],
        [
          "WHO",
          "World Health Org"
        ],
        [
          "",
          ""
        ],
        [
          "WHODrug",
          "International refe"
        ],
        [
          "",
          "foundation, UMC"
        ],
        [
          "",
          ""
        ],
        [
          "WMS",
          "Warehouse mana"
        ],
        [
          "",
          ""
        ],
        [
          "ZAMMSA",
          "Zambia Medicines"
        ],
        [
          "",
          ""
        ],
        [
          "ZAMRA",
          "Zambia Medicines"
        ],
        [
          "",
          ""
        ],
        [
          "vi",
          ""
        ]
      ],
      "narratives": {},
      "csv": "tables/table-1.csv"
    },
    {
      "label": "Table 2",
      "caption": "Fig. 6: Example of an Antenatal Care Business clinical workflow with highlighted connections to supply chain",
      "pages": [
        15
      ],
      "columns": [
        {
          "titles": "ytilicaf htlaeH"
        },
        {
          "titles": "tneilC"
        },
        {
          "titles": "Yes Start A f r a r c iv il e it y at t S c h o e e m l f h - 1 m c o 3 a m u . r n e e i t i o y n r r W et o 1 u m 4 rn . a s n ? No End"
        }
      ],
      "rows": [
        [
          "",
          "rekrow htlaeH",
          "3. Confirm Not pregnant No pregnancy Refer to other sexual and reproductive health services Regis A tr . ation m as a 1 s ( n . e R a a R s A g n s a e M d m p m i ) e d e n n t t 2 r n . e e s D fe i e g a r d n n r i a s n g l g e ? r Pregnant co F n 4 i t r a . s c t t? 5 c . h Q e u c i k ck First contact w p C h r o o i o s m 6 f l t i l o l a . e e r n c y a t ’s nd 1 1 0 0 c . . o 1 C u B n o e s u h e n a l s li v e n i l o g li u n r g, in-fa P c c s h i o l y y i u t m s y 1 n i o p 0 m s l t . e o o 2 a l g m l n in i a c s g a g l ement a c n 1 o d 0 u . n t 3 r s e e D a l t i l m e in t g ent Sche 1 N d 2 o u . ling Yes C.Antenatal care (ANC) referral Not first contact an s d 7 y . m fo C p l h l t o o e w m c - k s up ANC C p h e o a y x n s 8 s a d s . i m e u ca s c s t l ment 9 l t a . e im b C s o t a o s r g n a a i d t n o n u g r d c y t 1 a 0 n . d 4 t D re ia a g tm no e s n i t s su 1 p 0 p .5 le N m u e t n ri t t a io ti n on r c e 1 o g d 0 u e u . n 6 n c s t e R e io r l i a l n s in l k a g nd n R e e e 1 f d e 1 e r . r d a ? l Ye C s .ANC referral Immu 1 n 0 iz .7 ations pa 1 c r 0 t o n .8 u e n r In s v t e i i o m ll l i e n a n g te ce 1 c 0 o p a . u 9 r n n o d D s p e e m h l w y l a i l n o a la g r x m r i a i s a i n n d g"
        ]
      ],
      "narratives": {},
      "csv": "tables/table-2.csv"
    },
    {
      "label": "Table 3",
      "caption": "",
      "pages": [
        18,
        19
      ],
      "columns": [
        {
          "titles": "HANDBOOK CHAPTERS"
        },
        {
          "titles": "ILLUSTRATIVE TARGET ORGANIZATIONS"
        },
        {
          "titles": "ILLUSTRATIVE TARGET USER TEAMS AND ROLES"
        },
        {
          "titles": "PURPOSE OF THE CHAPTER"
        }
      ],
      "rows": [
        [
          "HANDBOOK CHAPTERS",
          "ILLUSTRATIVE TARGET ORGANIZATIONS",
          "ILLUSTRATIVE TARGET USER TEAMS & ROLES",
          "PURPOSE OF THE CHAPTER"
        ]
      ],
      "narratives": {},
      "csv": "tables/table-3.csv"
    },
    {
      "label": "Table 4",
      "caption": "",
      "pages": [
        52,
        53,
        54
      ],
      "columns": [
        {
          "titles": "COUNTRY: RWANDA"
        },
        {
          "titles": "REGULATORY"
        },
        {
          "titles": "DATA"
        },
        {
          "titles": "TECHNOLOGY"
        },
        {
          "titles": "PEOPLE"
        },
        {
          "titles": "CHANGE MANAGEMENT"
        }
      ],
      "rows": [
        [
          "COUNTRY: ZAMBIA",
          "REGULATORY",
          "DATA",
          "TECHNOLOGY",
          "PEOPLE",
          "CHANGE MANAGEMENT"
        ],
        [
          "COUNTRY: NIGERIA",
          "REGULATORY",
          "DATA",
          "TECHNOLOGY",
          "PEOPLE",
          "CHANGE MANAGEMENT"
        ]
      ],
      "narratives": {},
      "csv": "tables/table-4.csv"
    },
    {
      "label": "Table 5",
      "caption": "",
      "pages": [
        55
      ],
      "columns": [
        {
          "titles": "1."
        },
        {
          "titles": "Yokogawa Electric Corporation. The differences between digitization,"
        },
        {
          "titles": "9."
        },
        {
          "titles": "The Lancet Digital Health. WHO SMART guidelines: optimising country-"
        }
      ],
      "rows": [
        [
          "",
          "digitalization and digital transformation in manufacturing. (https://",
          "",
          "level use of guideline recommendations in the digital age. (https://"
        ],
        [
          "",
          "www.yokogawa.com/library/resources/white-papers/the-differences-",
          "",
          "www.thelancet.com/journals/landig/article/PIIS2589-7500(21)00123-6/"
        ],
        [
          "",
          "between-digitization-digitalization-and-digital-transformation-in-",
          "",
          "fulltext, accessed 10 January 2020)."
        ],
        [
          "",
          "manufacturing/, accessed 10 January 2020).",
          "",
          ""
        ],
        [
          "",
          "",
          "10.",
          "National Library of Medicine (NIH). Open Source software in health care"
        ],
        [
          "2.",
          "Gartner. Definition of Digitization. (https://www.gartner.com/en/",
          "",
          "(https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3221346/, accessed 10"
        ],
        [
          "",
          "information-technology/glossary/digitization, accessed 10 January 2020).",
          "",
          "January 2020)."
        ],
        [
          "",
          "",
          "",
          ""
        ],
        [
          "3.",
          "Yokogawa Electric Corporation. The differences between digitization,",
          "11.",
          "Open Source Initiative. Approved Licenses. (https://opensource.org/"
        ],
        [
          "",
          "digitalization and digital transformation in manufacturing. (https://",
          "",
          "licenses/, accessed 10 January 2020)."
        ],
        [
          "",
          "www.yokogawa.com/library/resources/white-papers/the-differences-",
          "",
          ""
        ],
        [
          "",
          "between-digitization-digitalization-and-digital-transformation-in-",
          "12.",
          "International Telecommunication Union (ITU). Open standards. (https:/"
        ],
        [
          "",
          "manufacturing/, accessed 10 January 2020).",
          "",
          "www.itu.int/en/ITU-T/ipr/Pages/open.aspx, accessed 10 January 2020)."
        ],
        [
          "",
          "",
          "",
          ""
        ],
        [
          "",
          "",
          "",
          ""
        ],
        [
          "",
          "",
          "",
          ""
        ],
        [
          "4.",
          "Gartner. Definition of Digitalization. (https://www.gartner.com/en/",
          "13.",
          "GS1. What is a trade item? (https://www.gs1.org/standards/id-keys/gtin"
        ],
        [
          "",
          "information-technology/glossary/digitalization, accessed 10",
          "",
          "accessed 10 January 2020)."
        ],
        [
          "",
          "",
          "",
          ""
        ],
        [
          "",
          "January 2020).",
          "14.",
          "Cimperman R. UAT defined: a guide to practical user acceptance"
        ],
        [
          "",
          "",
          "",
          ""
        ],
        [
          "5.",
          "Yokogawa Electric Corporation. The differences between digitization,",
          "",
          "testing. Pearson Education/Addison-Wesley Professional; 2006. Preview"
        ],
        [
          "",
          "digitalization and digital transformation in manufacturing. (https://",
          "",
          "available at: https://books.google.co.uk/books?id=spr3965oVlkC,"
        ],
        [
          "",
          "www.yokogawa.com/library/resources/white-papers/the-differences-",
          "",
          "accessed 10 January 2020."
        ],
        [
          "",
          "",
          "",
          ""
        ],
        [
          "",
          "between-digitization-digitalization-and-digital-transformation-in-",
          "15.",
          "SMART Guidelines (who.int): WHO SMART Guidelines. (https://www.who"
        ],
        [
          "",
          "manufacturing/, accessed 10 January 2020).",
          "",
          "int/teams/digital-health-and-innovation/smart-guidelines, accessed 10"
        ],
        [
          "",
          "",
          "",
          ""
        ],
        [
          "6.",
          "Gartner. Digital Transformation Definition. (https://www.gartner.com/",
          "",
          "January 2020)."
        ],
        [
          "",
          "",
          "",
          ""
        ],
        [
          "",
          "en/information-technology/glossary/digital-transformation, accessed",
          "16.",
          "Digital transformation handbook for health supply chain architecture"
        ],
        [
          "",
          "10 January 2020).",
          "",
          "(who.int): World Health Organization. https://www.who.int/"
        ],
        [
          "",
          "",
          "",
          ""
        ],
        [
          "7.",
          "United Nations Industrial Development Organization (UNIDO).",
          "",
          "publications/i/item/9789240101197, accessed 15 June 2024."
        ],
        [
          "",
          "",
          "",
          ""
        ],
        [
          "",
          "Standards and Digital Transformation. (https://www.unido.org/",
          "17.",
          "Principles for Digital Development [website]. New York, NY: United"
        ],
        [
          "",
          "sites/default/files/files/2021-11/Standards%20and%20Digital%20",
          "",
          "Nations Foundation. (https://digitalprinciples.org, accessed 10 January"
        ],
        [
          "",
          "Transformation_Complete_2021.pdf, accessed 10 January 2020).",
          "",
          "2020). Licence: https://creativecommons.org/licenses/by-sa/4.0/."
        ],
        [
          "",
          "",
          "",
          ""
        ],
        [
          "8.",
          "SMART Guidelines (who.int): WHO SMART Guidelines. (https://www.who.",
          "",
          ""
        ],
        [
          "",
          "int/initiatives/smart-guidelines, accessed 10 January 2020).",
          "",
          ""
        ]
      ],
      "narratives": {},
      "csv": "tables/table-5.csv"
    },
    {
      "label": "Table 6",
      "caption": "",
      "pages": [
        57,
        58,
        59,
        60,
        61
      ],
      "columns": [
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": "PHASE(S) IN WHICH IT IS REQUIRED"
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        },
        {
          "titles": ""
        }
      ],
      "rows": [
        [
          "ROLE CATEGORY",
          "ROLES",
          "DEPLOYMENT",
          "OPERATION",
          "POSITION TYPE",
          "SKILL SET",
          "RESPONSIBILITIES"
        ],
        [
          "ROLE CATEGORY",
          "ROLES",
          "DEPLOYMENT",
          "OPERATION",
          "POSITION TYPE",
          "SKILL SET",
          "RESPONSIBILITIES"
        ],
        [
          "ROLE CATEGORY",
          "ROLES",
          "DEPLOYMENT",
          "OPERATION",
          "POSITION TYPE",
          "SKILL SET",
          "RESPONSIBILITIES"
        ],
        [
          "ROLE CATEGORY",
          "ROLES",
          "DEPLOYMENT",
          "OPERATION",
          "POSITION TYPE",
          "SKILL SET",
          "RESPONSIBILITIES"
        ],
        [
          "ROLE CATEGORY",
          "ROLES",
          "DEPLOYMENT",
          "OPERATION",
          "POSITION TYPE",
          "SKILL SET",
          "RESPONSIBILITIES"
        ]
      ],
      "narratives": {},
      "csv": "tables/table-6.csv"
    }
  ],
  "coverage": [
    {
      "kind": "contents",
      "state": "found",
      "count": 32,
      "note": "contents from inferred"
    },
    {
      "kind": "sections",
      "state": "found",
      "count": 32
    },
    {
      "kind": "figures",
      "state": "found",
      "count": 15,
      "note": "1 raster, 14 vector; 15 caption(s) read off the pages"
    },
    {
      "kind": "tables",
      "state": "found",
      "count": 6
    },
    {
      "kind": "references",
      "state": "found",
      "count": 17
    },
    {
      "kind": "glossary",
      "state": "found",
      "note": "candidates in glossary/9789240116191-eng.glossary.json",
      "count": 58
    },
    {
      "kind": "footnotes",
      "state": "partial",
      "note": "no footnote linked to a mark; 9 foot-of-page line(s) no mark calls, 8 mark(s) with no note found, kept for a reader to judge"
    },
    {
      "kind": "summaries",
      "state": "found",
      "count": 32
    }
  ],
  "links": {
    "repo": "litlfred/who-iris",
    "branch": "main",
    "dir": "library/9789240116191-eng"
  }
}
