{
  "$schema": "folio-library-entry/v1",
  "id": "9789240120747-eng",
  "blocks": [
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-front-matter",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Front matter",
      "pageStart": 1,
      "pageEnd": 6,
      "target": "../sections/sec-front-matter.md",
      "narrative": null,
      "content": "# Digital transformation handbook for reporting substandard and falsified medical products\n\nISBN 978-92-4-012074-7 (electronic version)\nISBN 978-92-4-012075-4 (print version)\n\n© World Health Organization 2026\n\nSome rights reserved. This work is available under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 IGO licence (CC BY-NC-SA 3.0 IGO; https://creativecommons.org/licenses/by-nc-sa/3.0/igo).\n\nUnder the terms of this licence, you may copy, redistribute and adapt the work for non-commercial purposes, provided the work is appropriately cited, as indicated below. In any use of th",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Front matter of the Digital transformation handbook for reporting substandard and falsified medical products (ISBN 978-92-4-012074-7 electronic, 978-92-4-012075-4 print; © WHO 2026, CC BY-NC-SA 3.0 IGO), including suggested citation, CIP data, licensing terms, general disclaimers, and the table of contents.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-000",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Acknowledgements",
      "pageStart": 7,
      "pageEnd": 7,
      "target": "../sections/sec-000-acknowledgements.md",
      "narrative": null,
      "content": "# Acknowledgements\n\nThe World Health Organization (WHO) gratefully acknowledges the contributions of many individuals and organizations to the development of this document. This handbook was authored by Swaroop Jayaprakash and Natschja Nash-Mendez (Department of Digital Health and Innovations, WHO headquarters) and Rutendo Kuwana and Leticia Megias (Department of Regulation and Prequalification, WHO headquarters) in collaboration with Christian Moretti Anfossi (United Health Futures [UHF], Switzerland).\n\nWHO extends its sincere thanks to the following individuals who wrote, reviewed or provide",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Acknowledges the handbook's authors (Swaroop Jayaprakash, Natschja Nash-Mendez, Rutendo Kuwana, Leticia Megias, Christian Moretti Anfossi), technical reviewers and contributors (WHO headquarters, United Health Futures, independent experts), national regulatory authorities in Chile (ISP) and South Africa (SAHPRA), and funding from the Gates Foundation and the UK Fleming Fund.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-001",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Abbreviations and acronyms",
      "pageStart": 8,
      "pageEnd": 8,
      "target": "../sections/sec-001-abbreviations-and-acronyms.md",
      "narrative": null,
      "content": "# Abbreviations and acronyms\n\n| Abbreviation | Definition |\n| --- | --- |\n| BPMN | Business Process Model and Notation |\n| DIIG | Digital implementation investment guide (WHO) |\n| FHIR | Fast Healthcare Interoperability Resources® |\n| GSMS | Global Surveillance and Monitoring System (WHO) |\n| HL7 | Health Level Seven® |\n| ICT | information and communication technology |\n| ID | identity/identification/identifier |\n| ITU | International Telecommunication Union |\n| LMICs | low- and middle-income countries |\n| M&E | monitoring and evaluation |\n| NMRA | national medicines regulatory authority |\n| P",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Structured table of 19 abbreviations and acronyms used across the handbook, including BPMN, DIIG, FHIR, GSMS, HL7, ICT, ID, ITU, LMICs, M&E, NMRA, PMS, RACI, Rb-PMS, SaaS, SMART, UAT, UHF, and WHO.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-002",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Glossary",
      "pageStart": 9,
      "pageEnd": 11,
      "target": "../sections/sec-002-glossary.md",
      "narrative": null,
      "content": "# Glossary\n\n| Term | Definition |\n| --- | --- |\n| Active pharmacovigilance | Proactive measures that are taken to detect adverse events (1). |\n| Adverse drug reactions | Harmful, unintended reactions to medicines that occur at doses normally used for treatment (2). |\n| Business process | A set of related activities or tasks performed together to achieve the objectives of the health programme area, such as registration, counselling and referrals (3). |\n| Data element | A unit of data that has a specific and precise meaning (4). |\n| Digitization | The process of converting and organizing data fr",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Structured glossary defining 35 key terms used in the handbook, including active and passive pharmacovigilance, adverse drug reactions, business process, data element, digitization, digitalization, digital transformation, enabling environment, enterprise architecture, falsified and substandard medical products, functional and non-functional requirements, interoperability, Member State Mechanism (MSM), polypharmacy, post-market surveillance (PMS), registry, SMART Guidelines, trade item, unregistered product, user acceptance testing (UAT), and workflow.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-003",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Introduction",
      "pageStart": 13,
      "pageEnd": 13,
      "target": "../sections/sec-003-introduction.md",
      "narrative": null,
      "content": "# Introduction\n\nSubstandard and falsified medical products pose a multilayered threat to the stability of health systems. They endanger health, through either therapeutic failure or adverse effects, and they undermine public trust in health care. They also risk jeopardizing global efforts working to suppress antimicrobial resistance, threatening the long-term efficacy of key life-saving medicines. Further to their impacts on health, substandard and falsified medical products have adverse socioeconomic consequences and increase poverty by damaging individual productivity, income and social mobi",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Introduces the public health, antimicrobial resistance, and socioeconomic threats posed by substandard and falsified medical products, states the agreed WHO/Member State definitions, explains how supply chain complexity and procurement pressures increase risk in LMICs, and highlights the role of risk-based post-market surveillance (Rb-PMS) and NMRAs.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-004",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Reporting of substandard and falsified medical products",
      "pageStart": 13,
      "pageEnd": 14,
      "target": "../sections/sec-004-reporting-of-substandard-and-falsified-medical-p.md",
      "narrative": null,
      "content": "## Reporting of substandard and falsified medical products\n\nReporting suspected substandard and falsified medical products allows NMRAs to investigate them more thoroughly than the reporter. When a case of a substandard and falsified medical product is confirmed, relevant authorities can quickly remove the product from the supply chain and market, impose sanctions and address system weaknesses. In the long term, this should improve product quality and reduce the chances of substandard and falsified medical products entering the market (27).\n\nIn addition to reducing prevalence at a national lev",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Explains how reporting suspected substandard and falsified medical products enables NMRA investigation, market removal, and global surveillance via the WHO Global Surveillance and Monitoring System (GSMS), notes the frontline role and under-reporting of health care professionals, and motivates transitioning from paper-based reporting to standards-based digital solutions such as smartphone applications piloted in Indonesia and the United Republic of Tanzania.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-005",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Who this handbook is for",
      "pageStart": 14,
      "pageEnd": 15,
      "target": "../sections/sec-005-who-this-handbook-is-for.md",
      "narrative": null,
      "content": "## Who this handbook is for\n\nThis handbook has been developed for countries, organizations and teams seeking to plan and implement digital solutions for reporting substandard and falsified medical products by health care professionals and aims to provide guidance to the various target audiences across the different implementation phases and areas, as outlined in Table 1.\n\n**Table 1. Intended audience for the handbook**\n\n| Handbook section – phases | Illustrative target organizations | Illustrative target user teams and roles | Purpose of the section |\n| --- | --- | --- | --- |\n| 1. Assess the",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Defines the target audience for the handbook and presents Table 1 mapping each of the seven handbook chapters/phases to illustrative target organizations, target user teams and roles, and section purpose.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-006",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "How to use this handbook",
      "pageStart": 15,
      "pageEnd": 18,
      "target": "../sections/sec-006-how-to-use-this-handbook.md",
      "narrative": null,
      "content": "## How to use this handbook\n\nThis handbook provides guidance to countries on how to adopt digital solutions for reporting of substandard and falsified medical products. It outlines various steps to ensure a comprehensive approach that aligns with existing digital health guidance and other intersecting strategies and architectures.\n\nThis handbook can be a useful resource in the following scenarios:\n\n- When moving from a paper-only based reporting system to a digital reporting system.\n- When moving to a unified digital solution and approach, e.g. when there are some groups of health care profess",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Outlines four implementation scenarios for using the handbook, prerequisites around national digital health and supply chain strategies, alignment with the WHO Digital implementation investment guide (DIIG) across seven enterprise phases (Fig. 1), and alignment with WHO SMART Guidelines knowledge layers L1–L5 (Fig. 2).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-007",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "How this handbook was developed",
      "pageStart": 18,
      "pageEnd": 18,
      "target": "../sections/sec-007-how-this-handbook-was-developed.md",
      "narrative": null,
      "content": "## How this handbook was developed\n\nThis handbook draws on the knowledge of health care professionals and NMRAs globally and has collated the lessons learned from their experiences. It builds on insights from a pilot phase, benchmarking exercises with national authorities, consultations with Member States on substandard and falsified medical product reporting barriers, public feedback on a drafted version of the handbook and the latest round of consultations for this final product. Practical examples and templates were also informed by real-world implementation of substandard and falsified med",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Describes the development of the handbook through global consultations with health care professionals, NMRAs, and Member States, pilot implementations in Indonesia and the United Republic of Tanzania, and alignment with the Principles for Digital Development, DIIG, and the WHO/ITU National eHealth strategy toolkit.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-008",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Assess the current state and enabling environment",
      "pageStart": 19,
      "pageEnd": 20,
      "target": "../sections/sec-008-1-assess-the-current-state-and-enabling-environm.md",
      "narrative": null,
      "content": "# 1. Assess the current state and enabling environment\n\nA comprehensive assessment of the current state and the enabling environment is necessary before implementing a digital reporting system for substandard and falsified medical products. This chapter outlines the areas that should be analysed and the factors to consider. The inputs needed to inform this step and the anticipated outputs of this phase are listed below.\n\n| Inputs | Outputs | Resources (see page 50) |\n| --- | --- | --- |\n| • National health strategy, digital health strategy and architecture blueprint<br>• National health, data",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 1 opener outlining the inputs, outputs (situational analysis report and stakeholder matrix), and reference resources required to assess the current state and enabling environment before implementing a digital reporting system.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-009",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Analyse key stakeholders",
      "pageStart": 20,
      "pageEnd": 21,
      "target": "../sections/sec-009-11-analyse-key-stakeholders.md",
      "narrative": null,
      "content": "## 1.1 Analyse key stakeholders\n\nTo implement an effective digital substandard and falsified reporting solution, it is essential to identify and analyse stakeholders. Stakeholders include government officials, health care providers, funding organizations, the medical product industry, technology vendors and implementers, civil society and other partners. The analysis should outline their roles in substandard and falsified medical products, pharmacovigilance and digital health. It should help mobilize support and engage key players by examining responsibilities, information flows and power dyna",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Guides stakeholder identification and analysis across government, health care providers, funders, industry, implementers, and civil society, and presents Table 2 with sample stakeholder analysis questions across six dimensions (roles and responsibilities, information flows, influence and power, interests and expectations, engagement and collaboration, and capacity and resources).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-010",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Assess the digital readiness",
      "pageStart": 20,
      "pageEnd": 23,
      "target": "../sections/sec-010-12-assess-the-digital-readiness.md",
      "narrative": null,
      "content": "## 1.2 Assess the digital readiness\n\nDifferent levels of preparedness for deploying digital technologies will influence the design, implementation and adoption of reporting apps. As one of the first steps, a digital readiness assessment should be conducted to ensure solutions are tailored to the existing infrastructure, capacity and context. The outputs from the assessment should inform the necessary resources, enabling environment, budget and funding support for planning, implementation and operationalization of the substandard and falsified reporting system.\n\nThe following areas should be re",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Outlines the six areas of a country digital readiness assessment (national digital health strategy, enabling policy and regulatory environment, governance framework, human resources, technology infrastructure, and security and privacy protection) and presents Table 3 on assessing network coverage, hardware/software availability, infrastructure, security, privacy, and data ownership.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-011",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Assess current substandard and falsified reporting practices",
      "pageStart": 22,
      "pageEnd": 25,
      "target": "../sections/sec-011-13-assess-current-substandard-and-falsified-repo.md",
      "narrative": null,
      "content": "## 1.3 Assess current substandard and falsified reporting practices\n\n**Current practices.** Conduct an analysis of current practices, challenges and barriers faced in reporting substandard and falsified medical products. The outputs of the analysis should be used to develop optimal business processes and workflows within the application. It is important to examine substandard and falsified reporting procedures and their challenges, alongside pharmacovigilance procedures to identify potential opportunities for synergy. The integration of these processes can enhance their mutual effectiveness in",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Provides guidance on evaluating current substandard and falsified reporting practices, data collection forms, digital tools, and reporting barriers, presenting Table 4 (assessing pharmacovigilance and SF reporting practices and data usage), Table 5 (common challenges and barriers across seven categories with potential solutions, including anonymous reporting considerations), and the Chapter 1 checklist.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-012",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Establish a shared understanding and governance framework",
      "pageStart": 26,
      "pageEnd": 27,
      "target": "../sections/sec-012-2-establish-a-shared-understanding-and-governanc.md",
      "narrative": null,
      "content": "# 2. Establish a shared understanding and governance framework\n\nImplementing digital reporting systems requires more than just technology. It calls for a clear, strategic and participatory approach that aligns regulatory policy, governance and leadership. This section explores how countries can establish a shared understanding of the challenges and opportunities surrounding substandard and falsified medical products and create a strategic plan to ensure sustainable, effective adoption of digital health tools.\n\n| Inputs | Outputs | Resources (see page 50) |\n| --- | --- | --- |\n| • Current state",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 2 opener summarizing the inputs, outputs (new/amended regulatory policies, governance structures, and strategic goals), and resources for establishing a shared understanding and governance framework.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-013",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Review regulatory policies for substandard and falsified medical products reporting",
      "pageStart": 27,
      "pageEnd": 27,
      "target": "../sections/sec-013-21-review-regulatory-policies-for-substandard-an.md",
      "narrative": null,
      "content": "## 2.1 Review regulatory policies for substandard and falsified medical products reporting\n\nThe regulatory framework is the backbone for any substandard and falsified medical products reporting system, shaping data flow, privacy, liability and enforcement mechanisms. Before implementing a digital reporting system, countries should evaluate existing regulatory policies, identify gaps and determine whether new regulations or legislative amendments are necessary to support the implementation, operationalization and adoption.\n\n- **Pharmacovigilance and quality surveillance integration.** Substanda",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Guides the review of national regulatory frameworks supporting digital reporting of substandard and falsified medical products, covering pharmacovigilance and quality surveillance integration, mandatory and voluntary reporting obligations, and enforcement mechanisms.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-014",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Align policy with stakeholders",
      "pageStart": 28,
      "pageEnd": 28,
      "target": "../sections/sec-014-22-align-policy-with-stakeholders.md",
      "narrative": null,
      "content": "## 2.2 Align policy with stakeholders\n\nTackling substandard and falsified medical products requires more than a single institution. Effective policy depends on multisectoral collaboration across:\n\n- **Law enforcement and customs.** Align policies to enable swift data sharing with customs officers and law enforcement, who often spearhead investigations and border control.\n- **Health financing and procurement agencies.** Support policy coordination with procurement bodies and insurance systems to detect falsified products within supply chains or reimbursement claims.\n- **Innovation and ICT minis",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Describes multisectoral policy alignment across law enforcement and customs, health financing and procurement agencies, innovation and ICT ministries, and regional and global regulatory authorities.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-015",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Establish governance and leadership",
      "pageStart": 28,
      "pageEnd": 28,
      "target": "../sections/sec-015-23-establish-governance-and-leadership.md",
      "narrative": null,
      "content": "## 2.3 Establish governance and leadership\n\nEstablish a robust governance structure for coordinating the multiple stakeholders involved in substandard and falsified medical product reporting. Define clear roles and responsibilities to avoid duplication of effort, enhance transparency and create a stable platform for decision-making.\n\nA governance structure often includes:\n\n- **National steering committee.** Led by the ministry of health or NMRA, this committee provides strategic oversight, ensures alignment with national health goals and mobilizes resources. The national steering committee dri",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Defines a three-tier governance structure (national steering committee, technical working group, and advisory council) and key leadership roles (ministry of health/NMRA, project champion, and digital health coordinator/project manager).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-016",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Set the strategic goals",
      "pageStart": 28,
      "pageEnd": 29,
      "target": "../sections/sec-016-24-set-the-strategic-goals.md",
      "narrative": null,
      "content": "## 2.4 Set the strategic goals\n\nDefine strategic goals for the substandard and falsified reporting application so that it is built to appropriately address prioritized needs. These goals should be:\n\n- **Specific.** For instance, reduce the average detection-to-notification time for suspected substandard and falsified medical products from 14 days to 2 days.\n- **Measurable.** Use indicators like the number of detected substandard and falsified incidents, time to regulatory action, or user engagement metrics in the digital reporting platform.\n- **Achievable.** Align goals with available resource",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Explains how to set SMART (Specific, Measurable, Achievable, Relevant, Time-bound) strategic goals for the substandard and falsified medical product reporting application.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-017",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Analyse and mitigate risk",
      "pageStart": 29,
      "pageEnd": 29,
      "target": "../sections/sec-017-25-analyse-and-mitigate-risk.md",
      "narrative": null,
      "content": "## 2.5 Analyse and mitigate risk\n\nDigital transformations often face multiple risks – technical, financial or political. Conduct a risk analysis early in the strategic planning process to allow for appropriate mitigation measures to be put in place. Examples of risk include:\n\n- **Technical risks.** System failures, cybersecurity threats, interoperability challenges.\n- **Financial risks.** Funding shortfalls, changes in donor priorities or excessive long-term maintenance costs.\n- **Political and stakeholder risks.** Shifting government priorities, lack of stakeholder cooperation or data ownersh",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Categorizes technical, financial, and political/stakeholder risks in digital transformation, references the risk management template in Annex 7, and concludes Chapter 2 with the end-of-chapter checklist.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-018",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Define the future state",
      "pageStart": 30,
      "pageEnd": 31,
      "target": "../sections/sec-018-3-define-the-future-state.md",
      "narrative": null,
      "content": "# 3. Define the future state\n\nBuilding upon the previous sections, this section delves into the critical aspects of defining the future state for the reporting solution. In transitioning from identifying and establishing governance structures and regulatory policies, it becomes essential to strategically map out the envisioned state of digital transformation in substandard and falsified medical product reporting. This section provides guidance on defining the future state by creating an investment roadmap and aligning the solution with an enterprise architecture considering various technologic",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 3 opener detailing the inputs, outputs (digital investment roadmap and new or revised digital health enterprise architecture), and resources for defining the future state of the reporting solution.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-019",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Develop a digital investment roadmap",
      "pageStart": 31,
      "pageEnd": 32,
      "target": "../sections/sec-019-31-develop-a-digital-investment-roadmap.md",
      "narrative": null,
      "content": "## 3.1 Develop a digital investment roadmap\n\nTo ensure the successful implementation and sustainability of the substandard and falsified reporting solution, develop a structured investment roadmap detailing priorities across short-, medium- and long-term horizons, focusing on foundational infrastructure, functional enhancements and the integration of advanced technologies. The investment roadmap will help guarantee that the reporting solution remains effective, sustainable, scalable and adaptable to future health needs.\n\nThe investment roadmap for the substandard and falsified reporting soluti",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Guides the development of a phased digital investment roadmap across short-term (1–2 years), medium-term (3–5 years), and long-term (5+ years) horizons, accompanied by Table 6 mapping 22 system attributes across five categories to short-, medium-, and long-term priorities.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-020",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Link to the enterprise architecture",
      "pageStart": 33,
      "pageEnd": 34,
      "target": "../sections/sec-020-32-link-to-the-enterprise-architecture.md",
      "narrative": null,
      "content": "## 3.2 Link to the enterprise architecture\n\nThe DIIG provides an enterprise architecture framework for digital health interventions (Fig. 3).\n\n> “A digital health enterprise architecture, if available in the country, outlines current and planned business processes, data, systems and technologies and provides an overview of the standards, information exchange and interoperability profiles that can be optimized across the enterprise. A clearly established enterprise architecture describing how different processes, data, systems and technologies function together is crucial for guiding interopera",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Explains how to situate the substandard and falsified reporting application as a point-of-service application within the DIIG digital health enterprise architecture framework (Fig. 3), emphasizing open standards and interoperability (TOGAF, HL7 FHIR), cybersecurity and data protection, and the Chapter 3 checklist.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-021",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Determine the requirements",
      "pageStart": 35,
      "pageEnd": 36,
      "target": "../sections/sec-021-4-determine-the-requirements.md",
      "narrative": null,
      "content": "# 4. Determine the requirements\n\nIt is essential to thoroughly understand how users will engage with the system, the processes they will execute, and the data they will handle within the application before proceeding with the development and implementation of the digital reporting system. This section provides an overview of the key considerations for developing comprehensive requirements that will facilitate successful user adoption of the application.\n\n| Inputs | Outputs | Resources (see page 50) |\n| --- | --- | --- |\n| • National health strategy, digital health strategy and health policies",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 4 opener listing the inputs, documentation outputs (user personas, user scenarios, as-is and to-be business processes, data dictionary, decision logic algorithms, functional and non-functional requirements, and indicators), and resources for determining system requirements.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-022",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Identify user personas",
      "pageStart": 37,
      "pageEnd": 38,
      "target": "../sections/sec-022-41-identify-user-personas.md",
      "narrative": null,
      "content": "## 4.1 Identify user personas\n\nIdentify key user personas and related user personas. A user persona is a generic depiction of a relevant stakeholder or end user who would be interacting with the reporting system. Personas help identify the wants, needs and constraints of the end users. User personas can be based on real individuals or a fictional character that represents a combination of real individuals and stories. The closer the personas are to reality, the more likely the system will meet real needs. See Annex 2 for a user persona template.\n\nThe reporting system is primarily utilized by s",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Defines user personas for skilled health care professionals and related individuals, presenting Table 7 (examples of key user personas: Doctor, Nurse, Community health worker, Laboratory technician, and Pharmacist with descriptions, alternative titles, and ISCO codes) and Table 8 (related user persona: Individual).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-023",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Define user scenarios",
      "pageStart": 37,
      "pageEnd": 40,
      "target": "../sections/sec-023-42-define-user-scenarios.md",
      "narrative": null,
      "content": "## 4.2 Define user scenarios\n\nDefine clear user scenarios for each identified persona (see Table 9). These scenarios help translate roles into specific, practical use cases, ensuring that solutions are tailored to local workflows, digital readiness and user capacities. A good user scenario should describe the context, the user’s objective, the challenges they face and how the tool addresses them. This approach supports more intuitive design, targeted training and successful adoption – leading to better data quality and programme outcomes.\n\n**Table 9. Typical user scenario for health care profe",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Explains how user scenarios translate personas into practical use cases and presents Table 9 detailing typical end-to-end reporting scenarios (discovery, initial action, accessing reporting app, completing the report, submitting the report, and follow-up/feedback) across nine health care professions.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-024",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Develop business processes and workflows",
      "pageStart": 41,
      "pageEnd": 42,
      "target": "../sections/sec-024-43-develop-business-processes-and-workflows.md",
      "narrative": null,
      "content": "## 4.3 Develop business processes and workflows\n\nA business process is a set of related activities or tasks performed together to achieve specific objectives, such as reporting substandard and falsified medical products in this case (35). Workflows are a visual representation of the progression of activities (tasks, interactions, decision points) that are performed within the business process (35). The activities in a workflow include those that are manual and machine automated.\n\nA business process matrix (see Table 10 for example) is useful for:\n\n- taking stock of the business processes that",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Describes how to inventory business processes and map as-is and to-be workflows using BPMN 2.0 conventions, presenting Table 10 (business process matrix example SF-REP-001 for suspect product detection and reporting by a pharmacist) and Fig. 4 (example BPMN workflow for reporting substandard and falsified medical products).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-025",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Outline data requirements",
      "pageStart": 42,
      "pageEnd": 43,
      "target": "../sections/sec-025-44-outline-data-requirements.md",
      "narrative": null,
      "content": "## 4.4 Outline data requirements\n\nA data dictionary is a repository of information about the data elements such as description, data type and other characteristics. A data dictionary will be a useful input to designing the solution and facilitating understanding across multiple stakeholders. Data dictionaries should utilize terminology standards (e.g. International Classification of Diseases [ICD-11], SNOMED-GPS) and syntactic interoperability standards (e.g. HL7 FHIR). These standards ensure consistent and high-quality data exchange across various digital systems, regardless of the time, heal",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Explains the role of a standards-based data dictionary (ICD-11, SNOMED-GPS, HL7 FHIR) and presents Table 11 defining 10 illustrative data elements (SFR.A1.DE1 to SFR.A1.DE10) for activity SFR.A1 (Report substandard or falsified product).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-026",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Gather requirements",
      "pageStart": 42,
      "pageEnd": 47,
      "target": "../sections/sec-026-45-gather-requirements.md",
      "narrative": null,
      "content": "## 4.5 Gather requirements\n\nFunctional and non-functional requirements outline what the reporting application needs to do and how it should perform. These requirements guide developers and stakeholders in designing, developing and deploying the application. They define the application's purpose, features, functionality and behaviour.\n\nIllustrative functional and non-functional requirements are provided in Tables 12 and 13 as a starting point. This can be adapted and expanded to meet the needs of the country and the specific context.\n\n**Table 12. Sample list of functional requirements**\n\n| Requ",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Presents illustrative functional and non-functional requirements for the reporting application in Table 12 (7 user-story functional requirements under SFR.FXNREQ.001–002) and Table 13 (97 non-functional requirements across security, system requirements, scalability, usability, configuration, interoperability, hardware/connectivity, and delivery), followed by the Chapter 4 checklist.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-027",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Plan the implementation",
      "pageStart": 48,
      "pageEnd": 50,
      "target": "../sections/sec-027-5-plan-the-implementation.md",
      "narrative": null,
      "content": "# 5. Plan the implementation\n\nOnce you have defined the future state and the requirements for the substandard and falsified reporting application, the next step is to implement the system. This chapter provides guidance on planning the implementation, including the creation of a detailed budget.\n\n| Inputs | Outputs | Resources (see page 50) |\n| --- | --- | --- |\n| • Requirements documentation<br>• Digital investment roadmap for the substandard and falsified reporting solution<br>• Digital health enterprise architecture<br>• Current state analysis report<br>• Stakeholder matrix | • Project mana",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 5 covering implementation planning and budgeting, including the chapter opener (inputs, outputs, resources), Table 14 (steps across implementation planning, budget development, and execution), evaluation of deployment and software options, Table 15 (advantages, considerations, and challenges of five software options), and the Chapter 5 checklist.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-028",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Monitor, evaluate and scale",
      "pageStart": 51,
      "pageEnd": 52,
      "target": "../sections/sec-028-6-monitor-evaluate-and-scale.md",
      "narrative": null,
      "content": "# 6. Monitor, evaluate and scale\n\n| Inputs | Outputs | Resources (see page 50) |\n| --- | --- | --- |\n| • Historical and/or baseline data and analysis on substandard and falsified reporting<br>• Project management plan<br>• Stakeholder matrix | • M&E plan<br>• Operations and sustainability planp | • Digital implementation investment guide (DIIG)<br>• Monitoring and evaluating digital health interventions: a practical guide to conducting research and assessment<br>• Digital transformation handbook for primary health care: optimizing person-centred point of service systems |",
      "truncated": false,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 6 opener outlining the inputs, outputs (M&E plan and operations and sustainability plan), and reference resources for monitoring, evaluating, and scaling the reporting application.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-029",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Develop a monitoring and evaluation plan",
      "pageStart": 52,
      "pageEnd": 56,
      "target": "../sections/sec-029-61-develop-a-monitoring-and-evaluation-plan.md",
      "narrative": null,
      "content": "## 6.1 Develop a monitoring and evaluation plan\n\nTo define the goals of M&E activities and create a detailed plan, it is important to understand the distinctions and connections between monitoring and evaluation. As explained in WHO’s *Monitoring and evaluating digital health interventions: a practical guide to conducting research and assessment* (8), monitoring focuses on measuring properties that are intrinsic (inward) to the digital intervention; evaluation concentrates instead on metrics that are extrinsic (outward) to the intervention. Ideally, the intention is to demonstrate attribution,",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Distinguishes intrinsic monitoring from extrinsic evaluation across the digital health maturity life cycle (Fig. 5 and Fig. 6), and provides Table 16 (sample evaluation questions across usability, efficacy, effectiveness, and cost), Table 17 (six steps in developing a comprehensive M&E plan), and Table 18 (reference measures across quality, fidelity, stability, functionality, and investment).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-030",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Develop an operations and continuous improvement plan",
      "pageStart": 57,
      "pageEnd": 57,
      "target": "../sections/sec-030-62-develop-an-operations-and-continuous-improvem.md",
      "narrative": null,
      "content": "## 6.2 Develop an operations and continuous improvement plan\n\nDevelop an operations plan to sustain the ongoing operations and continuous improvement of the reporting application, ensuring its reliability and efficiency. The operations plan addresses strategies to scale the application, including expanding the user base and adding new features; as well as the maintenance and update strategy to support continued usage by existing users. By implementing a comprehensive operations and sustainability plan, stakeholders can manage resources effectively, maintain robust performance, accommodate grow",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Guides the development of an operations, continuous improvement, and sustainability plan covering stakeholder ownership, infrastructure and maintenance resources, recurring knowledge management and training, financial planning, backups and redundancy, and change management, concluding with the Chapter 6 checklist.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-031",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Share implementation experiences",
      "pageStart": 58,
      "pageEnd": 59,
      "target": "../sections/sec-031-7-share-implementation-experiences.md",
      "narrative": null,
      "content": "# 7. Share implementation experiences\n\n## Case study: Indonesia and and the United Republic of Tanzania\n\nA smartphone app was developed and piloted in Indonesia and the United Republic of Tanzania to help health care professionals report a suspected substandard and falsified medical product to the NMRA. The pilot study focused on providing a reporting app that was easy, simple to use, reliable and fast.\n\n| Step | Process |\n| --- | --- |\n| 1 | Health care professionals answered two multiple choice questions detailing if a product is suspected substandard and falsified and if there has beeen an",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Chapter 7 presenting the WHO-coordinated pilot case study in Indonesia and the United Republic of Tanzania (36 reports of 27 medical products), including the 4-step reporting workflow, offline and multilingual app functions, and a structured evaluation table of successes and areas requiring improvement across application/reporting and feasibility.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-032",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "References",
      "pageStart": 60,
      "pageEnd": 61,
      "target": "../sections/sec-032-references.md",
      "narrative": null,
      "content": "# References\n\n1. A practical handbook on the pharmacovigilance of antimalarial medicines. Geneva: World Health Organization; 2007 (https://iris.who.int/handle/10665/43914).\n2. Briefing note: safety of medicines – adverse drug reactions. Geneva: World Health Organization; 2018 (https://www.who.int/docs/default-source/medicines/safety-of-medicines--adverse-drug-reactions-jun18.pdf?sfvrsn=4fcaf40_2).\n3. Digital implementation investment guide (DIIG): integrating digital interventions into health programmes. Geneva: World Health Organization; 2020 (https://apps.who.int/iris/handle/10665/334306). L",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Lists the 37 numbered bibliographic references cited throughout the handbook, with footnote 1 noting that all references were accessed on 23 April 2026.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-033",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Resources",
      "pageStart": 62,
      "pageEnd": 62,
      "target": "../sections/sec-033-resources.md",
      "narrative": null,
      "content": "# Resources\n\n- Addressing future cybersecurity threats in digital health: report of the technical consultation, Geneva, Switzerland, 12-14 December 2023. Geneva: World Health Organization; 2024 (https://iris.who.int/handle/10665/379097). Licence: CC BY-NC-SA 3.0 IGO.\n- Cybersecurity and privacy maturity assessment and strengthening for digital health information systems. Copenhagen: World Health Organization Regional Office for Europe; 2025 (https://iris.who.int/handle/10665/380838). Licence: CC BY-NC-SA 3.0 IGO.\n- Digital adaptation kits [website]. Geneva: World Health Organization; 2025 (htt",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Lists 17 key WHO, ITU, UNICEF, MEASURE Evaluation, HL7 FHIR, and Open Group reference resources and toolkits supporting digital health transformation and substandard and falsified medical product reporting.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-034",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Annexes",
      "pageStart": 63,
      "pageEnd": 63,
      "target": "../sections/sec-034-annexes.md",
      "narrative": null,
      "content": "# Annexes\n\nThis section contains Annexes 1–7 supporting the implementation of digital solutions for reporting substandard and falsified medical products:\n\n- **Annex 1.** Principles for Digital Development\n- **Annex 2.** User persona template\n- **Annex 3.** Business Process Model and Notation (BPMN) symbols\n- **Annex 4.** Stakeholder RACI matrix\n- **Annex 5.** Template for assessing current software applications\n- **Annex 6.** Barriers to reporting\n- **Annex 7.** Risk management template",
      "truncated": false,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Part divider introducing Annexes 1–7 of the handbook.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-035",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Principles for Digital Development",
      "pageStart": 64,
      "pageEnd": 64,
      "target": "../sections/sec-035-annex-1-principles-for-digital-development.md",
      "narrative": null,
      "content": "## Annex 1. Principles for Digital Development\n\n| Principle | Description |\n| --- | --- |\n| **Understand the existing ecosystem** | Trust starts with a thorough understanding of the dynamic cultural, social and economic context in which you are operating. |\n| **Share, reuse and improve** | Build on what works, improve what works and share so that others can do the same. |\n| **Design with people** | Good design starts and ends with people that will manage, use and ideally benefit from a given digital initiative. |\n| **Design for inclusion** | Consider the full range of human diversity to maximi",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Annex 1 presenting the nine Principles for Digital Development (Understand the existing ecosystem; Share, reuse and improve; Design with people; Design for inclusion; Build for sustainability; Establish people-first data practices; Create open and transparent practices; Anticipate and mitigate harms; Use evidence to improve outcomes) and their definitions.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-036",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "User persona template",
      "pageStart": 65,
      "pageEnd": 65,
      "target": "../sections/sec-036-annex-2-user-persona-template.md",
      "narrative": null,
      "content": "## Annex 2. User persona template\n\nA user persona template/worksheet that summarizes each and every type of end user (e.g. pharmacists, doctors, nurses, dentists, midwives, paramedics, laboratory technicians, public health workers, veterinarians and pharmacy technicians) should be completed.\n\n| Section | Prompts and sample entries |\n| --- | --- |\n| **Persona occupation (e.g. nurse)** | — |\n| **Demographics** | • Gender<br>• Age<br>• Community of origin<br>• Language(s) used<br>• Education level |\n| **Expected roles and responsibilities** | • Daily<br>• Weekly<br>• Monthly |\n| **Behaviour patte",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Annex 2 providing a structured user persona template and worksheet covering persona occupation, demographics, expected daily/weekly/monthly roles and responsibilities, behaviour patterns, context description, challenges/pain points, and definition of success.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-037",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Business Process Model and Notation (BPMN) symbols",
      "pageStart": 66,
      "pageEnd": 67,
      "target": "../sections/sec-037-annex-3-business-process-model-and-notation-bpmn.md",
      "narrative": null,
      "content": "## Annex 3. Key Business Process Model and Notation symbols\n\n| Symbol | Symbol name | Description |\n| --- | --- | --- |\n| Pool (Lane 1, Lane 2, Lane 3) | **Pool** | The pool assumes process control and assigns tasks. A pool consists of one or more “swim lanes” that depict all the individuals or types of users involved in carrying out the business process or workflow. Diagrams should be clear, neat and easy for all viewers to understand the relationships across the different swim lanes.<br><br>For example, a pool could depict the business process of conducting an outreach activity, which involv",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Annex 3 defining 15 key Business Process Model and Notation (BPMN 2.0) symbols (Pool, Swim lane, Start event, Start event message, End event, Activity/task, Activity with subprocess, Activity with a business rule, Sequence flow, Message flow, Exclusive gateway, Parallel gateway, Throw – link event, Catch – link event, Ad hoc subprocess, and Loop activity).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-038",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Stakeholder RACI matrix",
      "pageStart": 68,
      "pageEnd": 68,
      "target": "../sections/sec-038-annex-4-stakeholder-raci-matrix.md",
      "narrative": null,
      "content": "## Annex 4. Stakeholder RACI matrix\n\nA sample template for a stakeholder RACI matrix. This can be adjusted to include stakeholders and activities relevant to the country’s context.\n\n| Activities | NMRA | Ministry of health | Implementation partner | Medical product industry | Health care professionals | Others... | Others... |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n| Define project scope | A | R | C | I | I | I | I |\n| Gather requirements | I | R | C | C | C | I | A |\n| Design UI/UX | I | C | C | I | C | C | A |\n\n*Notes:* R (responsible) – person/organization that does the work; A (",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Annex 4 providing a sample stakeholder RACI (Responsible, Accountable, Consulted, Informed) matrix template mapping project activities (Define project scope, Gather requirements, Design UI/UX) across NMRA, Ministry of health, Implementation partner, Medical product industry, Health care professionals, and other stakeholders.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-039",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Template for assessing current software applications",
      "pageStart": 69,
      "pageEnd": 69,
      "target": "../sections/sec-039-annex-5-template-for-assessing-current-software.md",
      "narrative": null,
      "content": "## Annex 5. Template for assessing the current software applications\n\nThis table is a template for assessing the current information systems landscape and identifying systems and gaps.\n\n| Domain / Function | Ministry of health | Regulatory authority | Central warehouse | Branch warehouse | Service delivery point | Community health worker | Individuals |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n| Forecasting and planning | Planning system (Deployed) | — | — | — | — | — | — |\n| Procurement management | — | — | — | — | — | — | — |\n| Supplier and contract management | — | — | — | — | — |",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Annex 5 providing a matrix template for assessing the current software applications landscape across 12 supply chain and regulatory domains and 7 health system actors, illustrating deployed systems (Planning system, OpenLMIS, ERP, RapidSMS, OpenClinic, NPC, Registration system) and in-progress tools (Health analytics platform, Pharmacovigilance mobile app, NPC mobile app).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-040",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Barriers to reporting",
      "pageStart": 70,
      "pageEnd": 70,
      "target": "../sections/sec-040-annex-6-barriers-to-reporting.md",
      "narrative": null,
      "content": "## Annex 6. Barriers to reporting\n\nAn example analysis showing the barriers to reporting substandard and falsified medical products.\n\n| Barrier category | Barrier | Affected stakeholders |\n| --- | --- | --- |\n| Health care barrier | Self-medication and polypharmacy: can't pinpoint the effects of single medicines | Consumer, Health care professionals |\n| Health care barrier | Lack of medical precision: can't pinpoint the effects of individual medicines | Health care professionals |\n| NMRA-related barrier | Lack of legal consequences for criminals | Health care professionals, NMRA |\n| NMRA-relat",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Annex 6 presenting an example barrier analysis mapping 15 barriers across 7 barrier categories (Health care, NMRA-related, Technology, Economic, Social, Education and knowledge, and Capacity barriers) to the affected stakeholders (Health care professionals, NMRA, and Consumer).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    },
    {
      "id": "library/9789240120747-eng/blocks/prose-sec-041",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Risk management template",
      "pageStart": 71,
      "pageEnd": 72,
      "target": "../sections/sec-041-annex-7-risk-management-template.md",
      "narrative": null,
      "content": "## Annex 7. Risk management template\n\nThe following table is a template for ranking risks and identifying mitigation steps.\n\n### Risk 001\n\n| Risk title | Description | Priority | Impact | Probability | Status |\n| --- | --- | --- | --- | --- | --- |\n| Inadequate training | IF system training is not delivered with appropriate content for the audience, THEN the adoption and use of the system may fail. | Low | Major | Medium | Mitigate |\n\n| Mitigation steps | Owner | Raised | Reviewed | Closed |\n| --- | --- | --- | --- | --- |\n| • Perform a skills assessment for each user before completing the tra",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Annex 7 providing a risk management template illustrated with sample risk 001 (Inadequate training: IF/THEN description, priority Low, impact Major, probability Medium, status Mitigate, three mitigation steps, and raised/reviewed dates).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "antigravity",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-31"
      }
    }
  ]
}
