{
  "$schema": "folio-library-document/v1",
  "id": "9789240093362-eng",
  "title": "Digital transformation handbook for primary health care",
  "variant": "pdf",
  "pages": 98,
  "tocSource": "outline",
  "tocMethod": null,
  "toc": [
    {
      "level": 1,
      "title": "Acknowledgements",
      "number": null,
      "page": 6,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-000-acknowledgements"
    },
    {
      "level": 1,
      "title": "Abbreviations",
      "number": null,
      "page": 7,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-001-abbreviations"
    },
    {
      "level": 1,
      "title": "Glossary",
      "number": null,
      "page": 8,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-002-glossary"
    },
    {
      "level": 1,
      "title": "Introduction",
      "number": null,
      "page": 13,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-003-introduction"
    },
    {
      "level": 1,
      "title": "How this handbook was developed",
      "number": "1.3",
      "page": 21,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-006-13-how-this-handbook-was-developed"
    },
    {
      "level": 1,
      "title": "SMART Guidelines",
      "number": "1.2",
      "page": 20,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-005-12-smart-guidelines"
    },
    {
      "level": 1,
      "title": "Person-centred point of service systems",
      "number": "1.1",
      "page": 18,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-004-11-person-centred-point-of-service-systems"
    },
    {
      "level": 1,
      "title": "How to use \nthis handbook",
      "number": null,
      "page": 22,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": null
    },
    {
      "level": 1,
      "title": "Choices for software and digital applications",
      "number": "2.5",
      "page": 27,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-011-25-choices-for-software-and-digital-applications"
    },
    {
      "level": 1,
      "title": "The stepwise approaches to digitizing",
      "number": "2.4",
      "page": 26,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-010-24-the-stepwise-approaches-to-digitizing"
    },
    {
      "level": 1,
      "title": "Before using this resource",
      "number": "2.3",
      "page": 24,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-009-23-before-using-this-resource"
    },
    {
      "level": 1,
      "title": "Targeted users",
      "number": "2.2",
      "page": 23,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-008-22-targeted-users"
    },
    {
      "level": 1,
      "title": "Targeted scenarios of digital readiness",
      "number": "2.1",
      "page": 23,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-007-21-targeted-scenarios-of-digital-readiness"
    },
    {
      "level": 1,
      "title": "Understand user \nrequirements",
      "number": null,
      "page": 28,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": null
    },
    {
      "level": 1,
      "title": "Gather and prioritize requirements",
      "number": "3.8",
      "page": 47,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-019-38-gather-and-prioritize-requirements"
    },
    {
      "level": 1,
      "title": "Map health service schedules",
      "number": "3.7",
      "page": 47,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-018-37-map-health-service-schedules"
    },
    {
      "level": 1,
      "title": "Determine decision-support logic",
      "number": "3.6",
      "page": 44,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-017-36-determine-decision-support-logic"
    },
    {
      "level": 1,
      "title": "Create a data dictionary",
      "number": "3.5",
      "page": 42,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-016-35-create-a-data-dictionary"
    },
    {
      "level": 1,
      "title": "Streamline data collection and indicator reporting",
      "number": "3.4",
      "page": 39,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-015-34-streamline-data-collection-and-indicator-repo"
    },
    {
      "level": 1,
      "title": "Map business processes and workflows",
      "number": "3.3",
      "page": 35,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-014-33-map-business-processes-and-workflows"
    },
    {
      "level": 1,
      "title": "Get to know the users",
      "number": "3.2",
      "page": 33,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-013-32-get-to-know-the-users"
    },
    {
      "level": 1,
      "title": "Follow key requirement-gathering methods",
      "number": "3.1",
      "page": 30,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-012-31-follow-key-requirement-gathering-methods"
    },
    {
      "level": 1,
      "title": "Undertake design and adaptation",
      "number": null,
      "page": 50,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": null
    },
    {
      "level": 1,
      "title": "Build and quality assurance",
      "number": "4.5",
      "page": 60,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-024-45-build-and-quality-assurance"
    },
    {
      "level": 1,
      "title": "Design system architecture",
      "number": "4.4",
      "page": 56,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-023-44-design-system-architecture"
    },
    {
      "level": 1,
      "title": "Develop and test prototype design",
      "number": "4.3",
      "page": 53,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-022-43-develop-and-test-prototype-design"
    },
    {
      "level": 1,
      "title": "Validate functional requirements",
      "number": "4.2",
      "page": 53,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-021-42-validate-functional-requirements"
    },
    {
      "level": 1,
      "title": "Finalize software and vendor selection",
      "number": "4.1",
      "page": 52,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-020-41-finalize-software-and-vendor-selection"
    },
    {
      "level": 1,
      "title": "Conduct training, testing and roll-out",
      "number": null,
      "page": 62,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": null
    },
    {
      "level": 1,
      "title": "Manage feedback and system maintenance",
      "number": "5.4",
      "page": 65,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-028-54-manage-feedback-and-system-maintenance"
    },
    {
      "level": 1,
      "title": "Deploy the system",
      "number": "5.3",
      "page": 65,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-027-53-deploy-the-system"
    },
    {
      "level": 1,
      "title": "Test user acceptance and deployment readiness",
      "number": "5.2",
      "page": 64,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-026-52-test-user-acceptance-and-deployment-readiness"
    },
    {
      "level": 1,
      "title": "Develop and conduct training",
      "number": "5.1",
      "page": 64,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-025-51-develop-and-conduct-training"
    },
    {
      "level": 1,
      "title": "Prepare for\nscale-up",
      "number": null,
      "page": 66,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": null
    },
    {
      "level": 1,
      "title": "Adopt change management practices",
      "number": "6.5",
      "page": 71,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-033-65-adopt-change-management-practices"
    },
    {
      "level": 1,
      "title": "Phase-out of legacy system(s)",
      "number": "6.4",
      "page": 71,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-032-64-phase-out-of-legacy-systems"
    },
    {
      "level": 1,
      "title": "Monitor and evaluate progress on objectives",
      "number": "6.3",
      "page": 71,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-031-63-monitor-and-evaluate-progress-on-objectives"
    },
    {
      "level": 1,
      "title": "Plan for phase-out of legacy system(s)",
      "number": "6.2",
      "page": 68,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-030-62-plan-for-phase-out-of-legacy-systems"
    },
    {
      "level": 1,
      "title": "Determine readiness for scaling up",
      "number": "6.1",
      "page": 68,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-029-61-determine-readiness-for-scaling-up"
    },
    {
      "level": 1,
      "title": "References",
      "number": null,
      "page": 72,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-034-references"
    },
    {
      "level": 1,
      "title": "Principles for digital development",
      "number": null,
      "page": 77,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-035-principles-for-digital-development"
    },
    {
      "level": 1,
      "title": "Worksheet for semi-structured interviews",
      "number": null,
      "page": 78,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": null
    },
    {
      "level": 1,
      "title": "Observations worksheet",
      "number": null,
      "page": 80,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-036-observations-worksheet"
    },
    {
      "level": 1,
      "title": "User persona worksheet",
      "number": null,
      "page": 82,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-037-user-persona-worksheet"
    },
    {
      "level": 1,
      "title": "User stories worksheet",
      "number": null,
      "page": 83,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-038-user-stories-worksheet"
    },
    {
      "level": 1,
      "title": "Business process matrix guide",
      "number": null,
      "page": 84,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-039-business-process-matrix-guide"
    },
    {
      "level": 1,
      "title": "Form inventory guide",
      "number": null,
      "page": 85,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-040-form-inventory-guide"
    },
    {
      "level": 1,
      "title": "Form data mapping guide",
      "number": null,
      "page": 86,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-041-form-data-mapping-guide"
    },
    {
      "level": 1,
      "title": "Aggregate indicator mapping guide",
      "number": null,
      "page": 90,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-042-aggregate-indicator-mapping-guide"
    },
    {
      "level": 1,
      "title": "Decision-support logic and scheduling matrix guide",
      "number": null,
      "page": 91,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": null
    },
    {
      "level": 1,
      "title": "Template for a decision-support table",
      "number": null,
      "page": 92,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-043-template-for-a-decision-support-table"
    },
    {
      "level": 1,
      "title": "Scheduling logic table guide",
      "number": null,
      "page": 94,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-044-scheduling-logic-table-guide"
    },
    {
      "level": 1,
      "title": "Prioritization of requirements guide",
      "number": null,
      "page": 95,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-045-prioritization-of-requirements-guide"
    },
    {
      "level": 1,
      "title": "HL7 FHIR standard components",
      "number": null,
      "page": 96,
      "pageLabel": null,
      "confidence": null,
      "evidence": null,
      "source": "outline",
      "section": "sec-046-hl7-fhir-standard-components"
    }
  ],
  "sections": [
    {
      "id": "sec-front-matter",
      "number": null,
      "title": "Front matter",
      "level": 1,
      "pageStart": 1,
      "pageEnd": 6,
      "labelStart": "A",
      "labelEnd": "iv",
      "words": 3913,
      "summary": {
        "text": "Presents the title page, ISBNs (978-92-4-009336-2 electronic; 978-92-4-009337-9 print), 2024 World Health Organization copyright and CC BY-NC-SA 3.0 IGO licensing terms, suggested citation, disclaimers, and full table of contents (Chapters 1–6, References, and Annexes 1–14) for the Digital transformation handbook for primary health care: optimizing person-centred point of service systems.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "decision-support logic",
          "heading": false
        },
        {
          "term": "transformation handbook",
          "heading": false
        },
        {
          "term": "optimizing person-centred",
          "heading": false
        },
        {
          "term": "digital transformation",
          "heading": false
        },
        {
          "term": "person-centred point",
          "heading": false
        },
        {
          "term": "matrix guide",
          "heading": false
        },
        {
          "term": "legacy system",
          "heading": false
        },
        {
          "term": "mapping guide",
          "heading": false
        }
      ],
      "extract": "Digital transformation handbook for primary health care Optimizing person-centred point of service systems Digital transformation handbook for primary health care Optimizing person-centred point of service systems Digital transformation handbook for primary health care: optimizing person-centred point of service systems ISBN 978-92-4-009336-2 (electronic version) ISBN 978-92-4-009337-9 (print version) © World Health",
      "extractCut": true,
      "blocks": [
        "library/9789240093362-eng/blocks/prose-sec-front-matter",
        "library/9789240093362-eng/blocks/figure-img-p001-1",
        "library/9789240093362-eng/blocks/figure-img-p003-1"
      ]
    },
    {
      "id": "sec-000-acknowledgements",
      "number": null,
      "title": "Acknowledgements",
      "level": 1,
      "pageStart": 6,
      "pageEnd": 7,
      "labelStart": "iv",
      "labelEnd": "v",
      "words": 634,
      "summary": {
        "text": "Credits the core development team from the WHO Department of Digital Health and Innovations, the WHO Department of Sexual and Reproductive Health and Research, Jhpiego, and Ona, lists external reviewers and consultative workshop participants, and acknowledges funding from the UK Foreign, Commonwealth and Development Office (FCDO) and the HRP Special Programme.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "regional office",
          "heading": false
        },
        {
          "term": "western pacific",
          "heading": false
        },
        {
          "term": "united states",
          "heading": false
        },
        {
          "term": "johns hopkins",
          "heading": false
        },
        {
          "term": "hopkins school",
          "heading": false
        },
        {
          "term": "headquarters",
          "heading": false
        },
        {
          "term": "cape town",
          "heading": false
        },
        {
          "term": "hopkins bloomberg",
          "heading": false
        }
      ],
      "extract": "The World Health Organization (WHO) is grateful for the contributions made by many individuals and organizations in the development of this handbook. This handbook was developed by Carl Leitner, Garrett Mehl, Akshita Palliwal, Natschja Ratanaprayul and Ritika Rawlani of the WHO Department of Digital Health and Innovations (Geneva, Switzerland); Tigest Tamrat of the WHO Department of Sexual and Reproductive Health",
      "extractCut": true
    },
    {
      "id": "sec-001-abbreviations",
      "number": null,
      "title": "Abbreviations",
      "level": 1,
      "pageStart": 7,
      "pageEnd": 7,
      "labelStart": "v",
      "labelEnd": "v",
      "words": 293,
      "summary": {
        "text": "Defines abbreviations and acronyms used throughout the handbook, including ANC, API, BPMN, CRDM, DAK, DHA, DICOM, DIIG, EA, FHIR, HL7, HRP, ICD-11, ICF, ICHI, IHE, ITU, JSON, LOINC, MAPS, MVP, OpenHIE, PCPOSS (person-centred point of service system), PHC, POS, SDG, SNOMED-GPS, UAT, UI, WHO, and WHO-FIC.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "blood pressure",
          "heading": false
        },
        {
          "term": "international classification",
          "heading": false
        },
        {
          "term": "notation",
          "heading": false
        },
        {
          "term": "interface",
          "heading": false
        },
        {
          "term": "enterprise",
          "heading": false
        },
        {
          "term": "digital",
          "heading": false
        },
        {
          "term": "healthcare",
          "heading": false
        },
        {
          "term": "user",
          "heading": false
        }
      ],
      "extract": "| Abbreviation | Definition | | --- | --- | | ANC | antenatal care | | API | application programming interface | | BPMN | Business Process Model and Notation | | CRDM | Collaborative Requirements Development Methodology | | DAK | Digital adaptation kit | | DBP | diastolic blood pressure | | DHA | Digital Health Atlas | | DICOM | Digital Imaging and Communications in Medicine | | DIIG | Digital Implementation",
      "extractCut": true
    },
    {
      "id": "sec-002-glossary",
      "number": null,
      "title": "Glossary",
      "level": 1,
      "pageStart": 8,
      "pageEnd": 12,
      "labelStart": "vi",
      "labelEnd": "x",
      "words": 3075,
      "summary": {
        "text": "Provides an alphabetical glossary of key digital health, software engineering, and primary health care terms used in the handbook—including algorithm, business process, care pathway, data dictionary, decision support logic/system/table, digital adaptation kits (DAKs), digitization, digitalization, digital transformation, enterprise architecture, functional and non-functional requirements, interoperability, longitudinal tracking, minimum viable product (MVP), person-centred point of service system (PCPOSS), SMART Guidelines, technical debt, user persona, user story, wireframes, and workflow—along with the opening glossary reference.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "accessed october",
          "heading": false
        },
        {
          "term": "output entries",
          "heading": false
        },
        {
          "term": "input entries",
          "heading": false
        },
        {
          "term": "gartner glossary",
          "heading": false
        },
        {
          "term": "service user",
          "heading": false
        },
        {
          "term": "digital system",
          "heading": false
        },
        {
          "term": "business process",
          "heading": false
        },
        {
          "term": "user health",
          "heading": false
        }
      ],
      "extract": "| Term | Definition | | --- | --- | | Algorithm | A specification of how a computer shall solve a problem, perform a calculation and execute a task. | | Annotation | In a decision table, an annotation simply provides further details and explanation to the rule, for those working on and working from the decision table. | | As-is | The current state of things (also see to-be). | | Beta version | The initial version of",
      "extractCut": true
    },
    {
      "id": "sec-003-introduction",
      "number": null,
      "title": "Introduction",
      "level": 1,
      "pageStart": 13,
      "pageEnd": 18,
      "labelStart": "1",
      "labelEnd": "6",
      "words": 2212,
      "summary": {
        "text": "Completes the glossary reference list (items 2–24) and introduces Chapter 1, framing the progression from paper-based records through digitization and digitalization to digital transformation (Fig. 1), situating person-centred point of service systems (PCPOSSs) within the 2019 WHO digital health guideline Recommendation 8 on digital client tracking with decision support (Fig. 2) and within an integrated primary health care digital ecosystem (Fig. 3), and explaining how workflow-based needs assessments and SMART Guidelines support PCPOSS implementation.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "digital transformation",
          "heading": false
        },
        {
          "term": "paper-based records",
          "heading": false
        },
        {
          "term": "digital systems",
          "heading": false
        },
        {
          "term": "digital tracking",
          "heading": false
        },
        {
          "term": "digital health",
          "heading": false
        },
        {
          "term": "digital formats",
          "heading": false
        },
        {
          "term": "digital ecosystem",
          "heading": false
        },
        {
          "term": "transformational journey",
          "heading": false
        }
      ],
      "extract": "CHAPTER 1 Introduction In many countries, individual-level paper-based systems – paper registers (including immunization registries), health service user charts, medical (or health) records and home-based records – are used by health workers and health service users (i.e. patients, clients, beneficiaries, individuals who receive health services), across all health programmes, at all levels of the health system.",
      "extractCut": true
    },
    {
      "id": "sec-004-11-person-centred-point-of-service-systems",
      "number": "1.1",
      "title": "Person-centred point of service systems",
      "level": 1,
      "pageStart": 18,
      "pageEnd": 20,
      "labelStart": "6",
      "labelEnd": "8",
      "words": 822,
      "summary": {
        "text": "Defines person-centred point of service systems (PCPOSSs) as digital systems combining decision support systems, community-based information systems, electronic health records, and personal health records across WHO digital health intervention classifications; contrasts the clerical and quality burdens of paper or siloed reporting systems with a combined PCPOSS built on the 'collect once, use for many purposes' principle (Fig. 4) and semantic/syntactic interoperability standards (such as ICD-11, SNOMED-GPS, and HL7 FHIR).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "pcposs encompasses",
          "heading": false
        },
        {
          "term": "person-centred",
          "heading": true
        },
        {
          "term": "record systems",
          "heading": false
        },
        {
          "term": "health record",
          "heading": false
        },
        {
          "term": "service",
          "heading": true
        },
        {
          "term": "manage person-centred",
          "heading": false
        },
        {
          "term": "digital health",
          "heading": false
        },
        {
          "term": "service users",
          "heading": false
        }
      ],
      "extract": "A person-centered point of service system (PCPOSS), digital in nature, facilitates the provision and delivery of health services to individuals (i.e. persons, clients, patients, health service users) at the point of care. A PCPOSS includes software capabilities that enable health- care providers to access, record and update individuals’ health information as well as interactively communicate with them. The term",
      "extractCut": true
    },
    {
      "id": "sec-005-12-smart-guidelines",
      "number": "1.2",
      "title": "SMART Guidelines",
      "level": 1,
      "pageStart": 20,
      "pageEnd": 21,
      "labelStart": "8",
      "labelEnd": "9",
      "words": 415,
      "summary": {
        "text": "Summarizes the WHO SMART Guidelines approach and its five reusable knowledge layers—L1 Narrative (enhanced guidelines), L2 Operational (Digital adaptation kits), L3 Machine readable (implementation guides), L4 Executable (reference applications), and L5 Dynamic (precision health models)—and illustrates how countries adapt and localize these layers when implementing a PCPOSS (Fig. 5).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "smart guidelines",
          "heading": true
        },
        {
          "term": "digital adaptation",
          "heading": false
        },
        {
          "term": "knowledge layers",
          "heading": false
        },
        {
          "term": "machine readable",
          "heading": false
        },
        {
          "term": "adaptation kits",
          "heading": false
        },
        {
          "term": "digital health",
          "heading": false
        },
        {
          "term": "digital services",
          "heading": false
        },
        {
          "term": "digital systems",
          "heading": false
        }
      ],
      "extract": "SMART Guidelines are Standards-based, Machine-readable, Adaptive, Requirements-based, and Testable recommended digital capabilities, health and data content. SMART Guidelines are WHO’s approach designed to systematize and accelerate the consistent application of recommended, life- saving interventions in the digital age (18). As countries are investing heavily in PCPOSSs, SMART Guidelines provide detailed",
      "extractCut": true
    },
    {
      "id": "sec-006-13-how-this-handbook-was-developed",
      "number": "1.3",
      "title": "How this handbook was developed",
      "level": 1,
      "pageStart": 21,
      "pageEnd": 21,
      "labelStart": "9",
      "labelEnd": "9",
      "words": 347,
      "summary": {
        "text": "Describes the handbook's development through expert consultations, implementation studies in Bangladesh, Pakistan, and Indonesia, the Collaborative Requirements Development Methodology (CRDM), and the Principles for Digital Development ('establish people-first data practices' and 'design with people'), notes conflict-of-interest declarations, and introduces Chapter 2 on how stakeholders can use the software- and health-area-agnostic handbook.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "establish people-first",
          "heading": false
        },
        {
          "term": "people-first data",
          "heading": false
        },
        {
          "term": "handbook",
          "heading": true
        },
        {
          "term": "data practices",
          "heading": false
        },
        {
          "term": "templates",
          "heading": false
        },
        {
          "term": "information systems",
          "heading": false
        },
        {
          "term": "methodologies",
          "heading": false
        },
        {
          "term": "built",
          "heading": false
        }
      ],
      "extract": "This practical guide was developed from the experiences and feedback of a variety of experts and digital health practitioners. Experiences, insights, templates and feedback were gathered through a series of consultations, a working group, expert interviews and dedicated feedback sessions. This included lessons learned from a study on digitalizing paper-based routine health information systems across different",
      "extractCut": true
    },
    {
      "id": "sec-007-21-targeted-scenarios-of-digital-readiness",
      "number": "2.1",
      "title": "Targeted scenarios of digital readiness",
      "level": 1,
      "pageStart": 22,
      "pageEnd": 23,
      "labelStart": "10",
      "labelEnd": "11",
      "words": 328,
      "summary": {
        "text": "Defines the two primary digital readiness scenarios targeted by the handbook: transitioning from a paper-only point-of-care system to an optimized digital system, and consolidating or upgrading partially digitized, siloed PCPOSSs operating alongside paper records into an integrated, interoperable PCPOSS.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "paper-based systems",
          "heading": false
        },
        {
          "term": "pcposss",
          "heading": false
        },
        {
          "term": "paper forms",
          "heading": false
        },
        {
          "term": "digital system",
          "heading": false
        },
        {
          "term": "pcposs",
          "heading": false
        },
        {
          "term": "care pathways",
          "heading": false
        },
        {
          "term": "health authority",
          "heading": false
        },
        {
          "term": "scenarios",
          "heading": true
        }
      ],
      "extract": "CHAPTER 2 How to use this handbook This chapter outlines how this handbook can be leveraged by key stakeholders and provides references to key resources for creating or updating a PCPOSS – whether from the early point of digitizing paper forms in paper-based systems or updating legacy digital systems to improve the integration of care pathways. Point of service systems that combine community-based information",
      "extractCut": true
    },
    {
      "id": "sec-008-22-targeted-users",
      "number": "2.2",
      "title": "Targeted users",
      "level": 1,
      "pageStart": 23,
      "pageEnd": 24,
      "labelStart": "11",
      "labelEnd": "12",
      "words": 194,
      "summary": {
        "text": "Identifies the primary audience of the handbook as business analysts, solution designers, health informaticians, public health programme teams, implementing partners, and software vendors bridging clinical/public health domains and technology, while emphasizing that end-users (health workers and health service users) must be actively engaged throughout requirements gathering, validation, and testing.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "pcposs",
          "heading": false
        },
        {
          "term": "public health",
          "heading": false
        },
        {
          "term": "targeted",
          "heading": true
        },
        {
          "term": "written",
          "heading": false
        },
        {
          "term": "users",
          "heading": true
        },
        {
          "term": "teams",
          "heading": false
        }
      ],
      "extract": "This handbook is aimed at individuals and teams seeking to gather and optimize the content and functional requirements for either adapting a PCPOSS or developing one bespoke. It is written for those with a public health and/or clinical background who have a baseline understanding of health information systems but may not be technologists themselves. In essence, this handbook is written for those who will fill the",
      "extractCut": true
    },
    {
      "id": "sec-009-23-before-using-this-resource",
      "number": "2.3",
      "title": "Before using this resource",
      "level": 1,
      "pageStart": 24,
      "pageEnd": 26,
      "labelStart": "12",
      "labelEnd": "14",
      "words": 1410,
      "summary": {
        "text": "Outlines strategic and infrastructural prerequisites required before using the handbook—situating it in Phase 5 (Determining health content requirements) of the seven-phase digital health enterprise lifecycle (Fig. 6)—and provides a readiness checklist covering value proposition, alignment with national strategy, scope control, unique identification (Box 1), data privacy governance, sustainable financing, target end-users, product ownership, and interoperability.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "unique ids",
          "heading": false
        },
        {
          "term": "implementing pcposs",
          "heading": false
        },
        {
          "term": "digital investment",
          "heading": false
        },
        {
          "term": "digital health",
          "heading": false
        },
        {
          "term": "unique identifiers",
          "heading": false
        },
        {
          "term": "telecommunications union",
          "heading": false
        },
        {
          "term": "sdg digital",
          "heading": false
        },
        {
          "term": "national digital",
          "heading": false
        }
      ],
      "extract": "The key assumption for users of this resource is that a comprehensive high-level needs assessment and strategic planning has already been conducted and concluded that implementing a PCPOSS is crucial for operationalizing a country’s digital health strategy. This needs assessment should have included a root-cause analysis illustrating the need for the PCPOSS to improve service delivery and accountability measures. If",
      "extractCut": true
    },
    {
      "id": "sec-010-24-the-stepwise-approaches-to-digitizing",
      "number": "2.4",
      "title": "The stepwise approaches to digitizing",
      "level": 1,
      "pageStart": 26,
      "pageEnd": 27,
      "labelStart": "14",
      "labelEnd": "15",
      "words": 491,
      "summary": {
        "text": "Summarizes the four core phases structuring the handbook—understanding user requirements, undertaking design and adaptation, conducting training, testing and roll-out, and preparing for scale-up—and explains how teams apply them iteratively using agile prototyping and continuous user feedback loops from minimum viable product (MVP) to subsequent releases (Fig. 7).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "handbook recognizing",
          "heading": false
        },
        {
          "term": "train users",
          "heading": false
        },
        {
          "term": "user requirements",
          "heading": false
        },
        {
          "term": "user feedback",
          "heading": false
        },
        {
          "term": "prioritize user",
          "heading": false
        },
        {
          "term": "roll out",
          "heading": false
        },
        {
          "term": "manage user",
          "heading": false
        },
        {
          "term": "end users",
          "heading": false
        }
      ],
      "extract": "Adhering to the Principles for Digital Development (see Annex 1), this handbook is organized in a stepwise manner that begins with the assumption of a limited or no digital system in place. It is a starting point for detailing plans to implement an enterprise-grade system planned for national scale up and integration with other national-level systems for long-term sustainability. This handbook outlines the",
      "extractCut": true
    },
    {
      "id": "sec-011-25-choices-for-software-and-digital-applications",
      "number": "2.5",
      "title": "Choices for software and digital applications",
      "level": 1,
      "pageStart": 27,
      "pageEnd": 27,
      "labelStart": "15",
      "labelEnd": "15",
      "words": 158,
      "summary": {
        "text": "Clarifies that the handbook is software-neutral and recommends thorough documentation and collaboration tools during requirements gathering and design, then introduces Chapter 3 (Understand user requirements) with an overview of stakeholder roles, required strategic and clinical inputs, Annex worksheet tools (Annexes 3–13 and WHO DAKs), and expected requirements documentation outputs.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "software",
          "heading": true
        },
        {
          "term": "implementation teams",
          "heading": false
        },
        {
          "term": "applications",
          "heading": true
        },
        {
          "term": "requirements-gathering",
          "heading": false
        },
        {
          "term": "pcposss",
          "heading": false
        }
      ],
      "extract": "Implementation teams using this handbook are not expected to use any specific software applications during the requirements-gathering and detailed design processes. Regardless of the chosen technology used, the only strong recommendation would be to ensure robust, high-quality documentation of the requirements of the system and its design. Collaboration tools such as project management and file sharing tools (e.g.",
      "extractCut": true
    },
    {
      "id": "sec-012-31-follow-key-requirement-gathering-methods",
      "number": "3.1",
      "title": "Follow key requirement-gathering methods",
      "level": 1,
      "pageStart": 28,
      "pageEnd": 33,
      "labelStart": "16",
      "labelEnd": "21",
      "words": 1987,
      "summary": {
        "text": "Details four complementary requirement-gathering methods—desk reviews of local registers, reporting tools, and WHO Digital adaptation kits (DAKs); workplace observations of health workers with attention to minimizing the Hawthorne effect; semi-structured and follow-up interviews using broad-to-narrow questioning and the '5 Whys' root-cause technique (Fig. 8); and multi-stakeholder requirements-gathering validation workshops.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "semi-structured interviews",
          "heading": false
        },
        {
          "term": "observing end-users",
          "heading": false
        },
        {
          "term": "requirements-gathering workshops",
          "heading": false
        },
        {
          "term": "follow-up interviews",
          "heading": false
        },
        {
          "term": "user stories",
          "heading": false
        },
        {
          "term": "matrix template",
          "heading": false
        },
        {
          "term": "service schedule",
          "heading": false
        },
        {
          "term": "mapping template",
          "heading": false
        }
      ],
      "extract": "CHAPTER 3 Understand user requirements The adoption of a person-centred point of service system (PCPOSS) requires a solid understanding of what data health workers need for routine service delivery and bottom-up accountability. This chapter describes the fundamental task of requirements gathering, in which user needs and constraints are documented. This process will rely on desk reviews, observations, workshops, and",
      "extractCut": true
    },
    {
      "id": "sec-013-32-get-to-know-the-users",
      "number": "3.2",
      "title": "Get to know the users",
      "level": 1,
      "pageStart": 33,
      "pageEnd": 35,
      "labelStart": "21",
      "labelEnd": "23",
      "words": 1361,
      "summary": {
        "text": "Explains how to apply human-centred design to understand target users by creating comprehensive user personas (or interim proto-personas validated in the field) covering demographics, work environment, official and actual duties, challenges, and motivations; documenting illustrative use cases; and authoring structured 'As a… I want to… so that…' user stories that translate into functional requirements.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "user stories",
          "heading": false
        },
        {
          "term": "user personas",
          "heading": false
        },
        {
          "term": "user story",
          "heading": false
        },
        {
          "term": "nurse midwife",
          "heading": false
        },
        {
          "term": "end user",
          "heading": false
        },
        {
          "term": "service user",
          "heading": false
        },
        {
          "term": "create user",
          "heading": false
        },
        {
          "term": "personas along",
          "heading": false
        }
      ],
      "extract": "Following the first principle of digital development (design with the user), user-centred design starts with getting to know the people you are designing for through conversation, observation and co-creation. User personas, use cases and user stories are critical tools used in the design process to better understand exactly who the users are and what their needs are. Having an in-depth understanding of who the user",
      "extractCut": true
    },
    {
      "id": "sec-014-33-map-business-processes-and-workflows",
      "number": "3.3",
      "title": "Map business processes and workflows",
      "level": 1,
      "pageStart": 35,
      "pageEnd": 39,
      "labelStart": "23",
      "labelEnd": "27",
      "words": 3333,
      "summary": {
        "text": "Describes how to inventory clinical and operational care pathways in a business process matrix (illustrated with the family planning DAK, Fig. 9), map current ('as-is') and optimized ('to-be') workflows using Business Process Model and Notation (BPMN 2.0) symbols (Table 1), label and annotate workflow steps (illustrated with the ANC DAK registration workflow, Figs. 10–11), and conduct as-is/to-be analyses to eliminate redundancies and bottlenecks.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "business processes",
          "heading": true
        },
        {
          "term": "workflows",
          "heading": true
        },
        {
          "term": "swim lane",
          "heading": false
        },
        {
          "term": "as-is workflows",
          "heading": false
        },
        {
          "term": "to-be workflows",
          "heading": false
        },
        {
          "term": "registration business",
          "heading": false
        },
        {
          "term": "business process",
          "heading": false
        },
        {
          "term": "rounded rectangle",
          "heading": false
        }
      ],
      "extract": "Business processes are sets of related activities and tasks performed to achieve a specific objective (6–9). In health care, business processes include, among many other things, health service user registration, counselling, service provision and referral. Workflows are a visual representation of the progression of activities (tasks, events, interactions) performed within a business process (45). The specific",
      "extractCut": true
    },
    {
      "id": "sec-015-34-streamline-data-collection-and-indicator-repo",
      "number": "3.4",
      "title": "Streamline data collection and indicator reporting",
      "level": 1,
      "pageStart": 39,
      "pageEnd": 42,
      "labelStart": "27",
      "labelEnd": "30",
      "words": 1595,
      "summary": {
        "text": "Presents a five-step process for streamlining paper registers into a PCPOSS: inventorying primary service delivery and summary reporting forms (Annex 7), mapping form data elements in a consolidated spreadsheet (Annex 8), compiling aggregate indicators calculated from primary point-of-care data under the 'collect once, use for many purposes' principle (Annex 9), and removing duplicated, orphaned, or non-essential data elements.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "data collection",
          "heading": true
        },
        {
          "term": "orphaned data",
          "heading": false
        },
        {
          "term": "data elements",
          "heading": false
        },
        {
          "term": "remove duplicated",
          "heading": false
        },
        {
          "term": "paper forms",
          "heading": false
        },
        {
          "term": "data mapping",
          "heading": false
        },
        {
          "term": "elements across",
          "heading": false
        },
        {
          "term": "mapping exercise",
          "heading": false
        }
      ],
      "extract": "Streamlining data collection is a long and tedious task, but it is the crux of translating paper register systems into a PCPOSS. The following are the five key steps needed to complete the streamlining. 1. Create an inventory of paper forms. 2. Map data elements across all forms. 3. Compile all aggregate indicators that need to be linked and reported. 4. Remove duplicated, orphaned and unnecessary data. 5.",
      "extractCut": true
    },
    {
      "id": "sec-016-35-create-a-data-dictionary",
      "number": "3.5",
      "title": "Create a data dictionary",
      "level": 1,
      "pageStart": 42,
      "pageEnd": 44,
      "labelStart": "30",
      "labelEnd": "32",
      "words": 916,
      "summary": {
        "text": "Provides the decision table for reconciling duplicated, non-essential, and orphaned data elements (Fig. 12 continuation) and explains how to construct a streamlined data dictionary—distinguishing database-design vs. UI-design data dictionaries—and map data elements to standardized semantic classifications and terminologies (such as WHO-FIC/ICD-11, LOINC, and SNOMED-GPS) and syntactic standards (HL7 FHIR), leveraging WHO DAKs and terminology services such as Open Concept Lab.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "data dictionary",
          "heading": true
        },
        {
          "term": "data elements",
          "heading": false
        },
        {
          "term": "standardized classifications",
          "heading": false
        },
        {
          "term": "data dictionaries",
          "heading": false
        },
        {
          "term": "data labels",
          "heading": false
        },
        {
          "term": "standardized concepts",
          "heading": false
        },
        {
          "term": "map data",
          "heading": false
        },
        {
          "term": "essential data",
          "heading": false
        }
      ],
      "extract": "The final step in streamlining data collection and indicator reporting is to create a data dictionary, which (in this context) is a repository of all the data elements essential for individual and aggregate levels, including some metadata components, that will be included in the PCPOSS. For the purposes of designing the solution and facilitating understanding across multiple stakeholders, the data dictionary will",
      "extractCut": true
    },
    {
      "id": "sec-017-36-determine-decision-support-logic",
      "number": "3.6",
      "title": "Determine decision-support logic",
      "level": 1,
      "pageStart": 44,
      "pageEnd": 47,
      "labelStart": "32",
      "labelEnd": "35",
      "words": 1566,
      "summary": {
        "text": "Explains how to document the decision-support logic, such as scheduling, risk assessment for triage or referral and medical eligibility, to be built into a digital point-of-service system (PCPOSS) so that health workers follow WHO and national care pathways. It recommends starting from WHO digital adaptation kits, adapting them to national policy, and dropping any logic not backed by evidence-based guidelines because faulty logic can endanger patients. It then describes three tools: a decision-support logic matrix (illustrated by an HIV example in Fig. 13), decision trees (illustrated by an antenatal HIV testing and prevention pathway in Fig. 14), and decision-support tables that engineers translate into code, with templates in the annexes.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "decision-support logic",
          "heading": true
        },
        {
          "term": "decision logic",
          "heading": false
        },
        {
          "term": "decision-support tables",
          "heading": false
        },
        {
          "term": "logic matrix",
          "heading": false
        },
        {
          "term": "pathway decision-support",
          "heading": false
        },
        {
          "term": "decision trees",
          "heading": false
        },
        {
          "term": "support logic",
          "heading": false
        },
        {
          "term": "hiv testing",
          "heading": false
        }
      ],
      "extract": "Digital systems can go beyond simple data collection and aggregation by introducing additional layers of sophistication that are generally unavailable on paper. This includes the opportunity to enhance care provision with built-in decision-support logic. In PCPOSSs, embedded decision-support logic can help health workers follow appropriate clinical care pathways set out by WHO and national public health authorities’",
      "extractCut": true
    },
    {
      "id": "sec-018-37-map-health-service-schedules",
      "number": "3.7",
      "title": "Map health service schedules",
      "level": 1,
      "pageStart": 47,
      "pageEnd": 47,
      "labelStart": "35",
      "labelEnd": "35",
      "words": 372,
      "summary": {
        "text": "Describes how to document recurring and prescribed health service schedules (such as antenatal care contacts, immunizations, and laboratory follow-ups) in spreadsheets organized by health worker occupational group, capturing trigger events, intervals, follow-up actions, expiration criteria, and schedule deviations (Annex 12).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "service schedules",
          "heading": true
        },
        {
          "term": "health service",
          "heading": true
        },
        {
          "term": "pcposs",
          "heading": false
        },
        {
          "term": "worker occupational",
          "heading": false
        },
        {
          "term": "spreadsheet",
          "heading": false
        },
        {
          "term": "occupational group",
          "heading": false
        },
        {
          "term": "upcoming",
          "heading": false
        },
        {
          "term": "anc",
          "heading": false
        }
      ],
      "extract": "Service schedules give health workers an overview of upcoming, due or overdue services, and aim to ensure timeliness of service delivery and continuity of care. Service schedules can also be a basis for reminders that are sent from the PCPOSS to health service users about upcoming services, if targeted health service user communication is an intervention included in the PCPOSS. Workflow mapping already completed by",
      "extractCut": true
    },
    {
      "id": "sec-019-38-gather-and-prioritize-requirements",
      "number": "3.8",
      "title": "Gather and prioritize requirements",
      "level": 1,
      "pageStart": 47,
      "pageEnd": 49,
      "labelStart": "35",
      "labelEnd": "37",
      "words": 1220,
      "summary": {
        "text": "Explains how to translate user stories, workflows, and data dictionaries into functional and non-functional requirements, prioritize them into high, medium, and low tiers using IEEE software requirements specification criteria (Annex 13), verify completion of Chapter 3 checkpoints, and transition to Chapter 4 (Undertake design and adaptation) with an overview of technology partner roles, inputs, tools, and outputs.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "non-functional requirements",
          "heading": false
        },
        {
          "term": "functional requirements",
          "heading": false
        },
        {
          "term": "user stories",
          "heading": false
        },
        {
          "term": "nurse midwife",
          "heading": false
        },
        {
          "term": "service user",
          "heading": false
        },
        {
          "term": "user story",
          "heading": false
        },
        {
          "term": "health worker",
          "heading": false
        },
        {
          "term": "pcposs",
          "heading": false
        }
      ],
      "extract": "The requirements for a PCPOSS are the functional and non-functional criteria that it must meet to ensure end-users are satisfied and the system performs as intended. The following two types of requirements need to be gathered and prioritized. • Functional requirements describe what the system must be able to do (“the water bottle shall be able to store liquid without leaking” would be an everyday example). •",
      "extractCut": true
    },
    {
      "id": "sec-020-41-finalize-software-and-vendor-selection",
      "number": "4.1",
      "title": "Finalize software and vendor selection",
      "level": 1,
      "pageStart": 50,
      "pageEnd": 53,
      "labelStart": "38",
      "labelEnd": "41",
      "words": 899,
      "summary": {
        "text": "Outlines how to conduct an objective landscape analysis and scorecard evaluation to select software and vendors—including leveraging SMART Guidelines L4 executable reference applications such as the WHO Digital ANC module—and provides a four-part checklist covering pre-evaluation, software features and interoperability, software ownership and total cost of ownership, and vendor reputation and support.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "software vendor",
          "heading": true
        },
        {
          "term": "reference software",
          "heading": false
        },
        {
          "term": "software features",
          "heading": false
        },
        {
          "term": "business requirements",
          "heading": false
        },
        {
          "term": "technology partner",
          "heading": false
        },
        {
          "term": "system architecture",
          "heading": false
        },
        {
          "term": "implementation team",
          "heading": false
        },
        {
          "term": "source code",
          "heading": false
        }
      ],
      "extract": "CHAPTER 4 Undertake design and adaptation The steps of undertaking detailed design and adaptation should be led primarily by a technology partner. This section summarizes the standards, concept and activities a technology partner is expected, at a minimum, to undertake. Implementation teams commissioning the design and adaptation are not expected to know how to programme software themselves but understanding the",
      "extractCut": true
    },
    {
      "id": "sec-021-42-validate-functional-requirements",
      "number": "4.2",
      "title": "Validate functional requirements",
      "level": 1,
      "pageStart": 53,
      "pageEnd": 53,
      "labelStart": "41",
      "labelEnd": "41",
      "words": 174,
      "summary": {
        "text": "Recommends holding iterative, component-by-component stakeholder workshops with the selected technology partner to validate and confirm functional requirements prior to software construction, ensuring alignment with business processes and preventing costly rework.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "requirements",
          "heading": true
        },
        {
          "term": "validate",
          "heading": true
        },
        {
          "term": "pcposs",
          "heading": false
        },
        {
          "term": "key stakeholders",
          "heading": false
        },
        {
          "term": "rework",
          "heading": false
        }
      ],
      "extract": "As the steps outlined in Chapter 1 to understand users and the needs for a system to digitize primary health care have shown, creating a PCPOSS is a highly iterative process. Once a team, including technology partners, is in place and an initial set of requirements has been identified, these requirements should be validated with all the key stakeholders. Additional workshops with key stakeholders are necessary to",
      "extractCut": true
    },
    {
      "id": "sec-022-43-develop-and-test-prototype-design",
      "number": "4.3",
      "title": "Develop and test prototype design",
      "level": 1,
      "pageStart": 53,
      "pageEnd": 56,
      "labelStart": "41",
      "labelEnd": "44",
      "words": 1289,
      "summary": {
        "text": "Describes progressive UI design and prototyping across increasing fidelity levels—paper sketches, wireframes, visual mock-ups, and clickable high-fidelity prototypes (Fig. 15)—and details a five-step user-centred design testing cycle (designing test use cases, creating multiple prototypes, validating with end-users via role play, documenting structured feedback, and iterating while guarding against scope creep).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "fidelity prototypes",
          "heading": false
        },
        {
          "term": "mock-ups",
          "heading": false
        },
        {
          "term": "design",
          "heading": true
        },
        {
          "term": "higher fidelity",
          "heading": false
        },
        {
          "term": "user-centred design",
          "heading": false
        },
        {
          "term": "incorporate feedback",
          "heading": false
        },
        {
          "term": "wireframes",
          "heading": false
        },
        {
          "term": "document feedback",
          "heading": false
        }
      ],
      "extract": "Creating mock-ups of a user interface (UI) and prototyping of the product helps to evaluate the layout, flow and usability of the intended digital application prior to coding and development. These design mock-ups and prototypes will prove useful when the engineers start to build the system, as they will help the engineers to visualize how the functional requirements being built into the system will be used. There",
      "extractCut": true
    },
    {
      "id": "sec-023-44-design-system-architecture",
      "number": "4.4",
      "title": "Design system architecture",
      "level": 1,
      "pageStart": 56,
      "pageEnd": 60,
      "labelStart": "44",
      "labelEnd": "48",
      "words": 2390,
      "summary": {
        "text": "Explains how to design a PCPOSS system architecture within a broader Enterprise Architecture (EA) using frameworks such as TOGAF (business, data, application, and technology domains, Table 2) and OpenHIE; defines syntactic, semantic, organizational, and legal interoperability (Table 3); and catalogues global open standards across terminology/classification (WHO-FIC, ICD-11, ICF, ICHI, LOINC, SNOMED-GPS), health content (DAKs, WHO guidelines), communication (HL7 FHIR, IHE, DICOM, GS1), and privacy protection laws (Table 4).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "system architecture",
          "heading": true
        },
        {
          "term": "syntactic interoperability",
          "heading": false
        },
        {
          "term": "semantic interoperability",
          "heading": false
        },
        {
          "term": "interoperability standards",
          "heading": false
        },
        {
          "term": "semantic terminology",
          "heading": false
        },
        {
          "term": "organizational interoperability",
          "heading": false
        },
        {
          "term": "classification standards",
          "heading": false
        },
        {
          "term": "enterprise architecture",
          "heading": false
        }
      ],
      "extract": "A system architecture is a conceptual model that depicts how the PCPOSS will be structured and how it functions and includes all the software and hardware components that comprise the system. Further, the system architecture of a PCPOSS would need to function within an Enterprise Architecture (EA), which describes how the PCPOSS interacts with other parts of the digital health ecosystem and is used to drive",
      "extractCut": true
    },
    {
      "id": "sec-024-45-build-and-quality-assurance",
      "number": "4.5",
      "title": "Build and quality assurance",
      "level": 1,
      "pageStart": 60,
      "pageEnd": 61,
      "labelStart": "48",
      "labelEnd": "49",
      "words": 578,
      "summary": {
        "text": "Outlines key elements of an agile software build (continuous user engagement, vendor communication, comprehensive documentation, and safety-first quality assurance), specifies seven categories of QA system testing (installation, stress, security, graphic UI, integration, general QA, and accessibility testing), provides the Chapter 4 completion checkpoint, and introduces Chapter 5 (Conduct training, testing and roll-out) with its stakeholder roles, inputs, tools, and outputs.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "quality assurance",
          "heading": true
        },
        {
          "term": "build",
          "heading": true
        },
        {
          "term": "pcposs",
          "heading": false
        },
        {
          "term": "testing approach",
          "heading": false
        },
        {
          "term": "release version",
          "heading": false
        },
        {
          "term": "technology partner",
          "heading": false
        },
        {
          "term": "consistent communication",
          "heading": false
        },
        {
          "term": "agile",
          "heading": false
        }
      ],
      "extract": "During this step, the technology partner will take the time to build the PCPOSS. They will need to spend time coding and ensuring that their code results in the required functionality and design. It is easy to underestimate the time and costs needed to build a quality PCPOSS, but it is important to anticipate them properly so that the system is built successfully and meets users’ needs. The nature of this step is",
      "extractCut": true
    },
    {
      "id": "sec-025-51-develop-and-conduct-training",
      "number": "5.1",
      "title": "Develop and conduct training",
      "level": 1,
      "pageStart": 62,
      "pageEnd": 64,
      "labelStart": "50",
      "labelEnd": "52",
      "words": 658,
      "summary": {
        "text": "Identifies the three categories of training required before wide deployment—training end-users on PCPOSS use, training technical staff on PCPOSS maintenance, and training on clinical service delivery changes (managed by national health programmes)—and recommends piloting the training curriculum on a small scale first.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "training",
          "heading": true
        },
        {
          "term": "training curriculum",
          "heading": false
        },
        {
          "term": "pcposs",
          "heading": false
        },
        {
          "term": "beta version",
          "heading": false
        },
        {
          "term": "targeted end-users",
          "heading": false
        },
        {
          "term": "technology partner",
          "heading": false
        },
        {
          "term": "health workers",
          "heading": false
        },
        {
          "term": "local technology",
          "heading": false
        }
      ],
      "extract": "CHAPTER 5 Conduct training, testing and roll-out After the beta version is built, there are some crucial steps that need to be taken before the system is deployed widely to targeted end-users. This includes training and testing, along with final updates to the person-centred point of service system (PCPOSS) for a version one release. End-user training is necessary to help improve the likelihood of adoption, and",
      "extractCut": true
    },
    {
      "id": "sec-026-52-test-user-acceptance-and-deployment-readiness",
      "number": "5.2",
      "title": "Test user acceptance and deployment readiness",
      "level": 1,
      "pageStart": 64,
      "pageEnd": 65,
      "labelStart": "52",
      "labelEnd": "53",
      "words": 426,
      "summary": {
        "text": "Describes conducting user acceptance testing (UAT) of the beta PCPOSS with a small group of trained end-users and advisers in real workflows to catch bugs and usability barriers before production roll-out, alongside detailed guidance on culturally tailored, competency-based end-user training (including device familiarization and training of trainers) and ongoing maintenance training for local technology partners.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "uat testers",
          "heading": false
        },
        {
          "term": "user acceptance",
          "heading": true
        },
        {
          "term": "test cases",
          "heading": false
        },
        {
          "term": "design flaws",
          "heading": false
        },
        {
          "term": "beta version",
          "heading": false
        },
        {
          "term": "test data",
          "heading": false
        },
        {
          "term": "bugs",
          "heading": false
        },
        {
          "term": "deployment",
          "heading": true
        }
      ],
      "extract": "With a beta version of the PCPOSS available, a series of user acceptance tests needs to take place prior to deployment. User acceptance testing (UAT) should be conducted by the core project team with a small group of trusted advisers and end-users. The small number of UAT testers, including some end-users, should initially be trained on how to use the beta version of the software, then tasked with using the PCPOSS",
      "extractCut": true
    },
    {
      "id": "sec-027-53-deploy-the-system",
      "number": "5.3",
      "title": "Deploy the system",
      "level": 1,
      "pageStart": 65,
      "pageEnd": 65,
      "labelStart": "53",
      "labelEnd": "53",
      "words": 315,
      "summary": {
        "text": "Details the creation of realistic UAT test cases and test data (including edge cases and clinical decision-support verification) and outlines the operational steps led by the technology partner to deploy the validated PCPOSS into a production environment—covering site infrastructure, hardware logistics, software installation, data migration, account configuration, site testing, non-disruptive scheduling, and building user trust.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "poor deployment",
          "heading": false
        },
        {
          "term": "system",
          "heading": true
        },
        {
          "term": "production environment",
          "heading": false
        },
        {
          "term": "installing",
          "heading": false
        },
        {
          "term": "digital technologies",
          "heading": false
        },
        {
          "term": "technology partner",
          "heading": false
        },
        {
          "term": "deployed",
          "heading": false
        },
        {
          "term": "health workers",
          "heading": false
        }
      ],
      "extract": "Deployment of the system often requires strong strategic thinking by the technology partner, as poorly deployed systems can make or break an entire project. Once all the required testing has been completed, including UAT, the system can be deployed in a production environment. A production environment refers to the normal operational environment where a system is deployed and will be in full use (98). This",
      "extractCut": true
    },
    {
      "id": "sec-028-54-manage-feedback-and-system-maintenance",
      "number": "5.4",
      "title": "Manage feedback and system maintenance",
      "level": 1,
      "pageStart": 65,
      "pageEnd": 65,
      "labelStart": "53",
      "labelEnd": "53",
      "words": 183,
      "summary": {
        "text": "Covers establishing standard operating procedures for continuous feedback management, bug resolution, hardware/software maintenance, and post-deployment monitoring and evaluation during roll-out, then introduces Chapter 6 (Prepare for scale-up) with an overview of stakeholder roles, inputs, M&E and MAPS toolkit resources, and outputs for phasing out paper and legacy systems.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "feedback",
          "heading": true
        },
        {
          "term": "maintenance",
          "heading": true
        },
        {
          "term": "system",
          "heading": true
        },
        {
          "term": "roll-out",
          "heading": false
        },
        {
          "term": "bug",
          "heading": false
        }
      ],
      "extract": "Feedback management, training, software updates and hardware maintenance will all be needed continually during the roll-out. The implementation team should have a standard operating procedure for managing all this feedback. For example, if there is a bug that occurs during the pilot and roll-out: • How will the team receive feedback? • Is there a call centre or other central feedback mechanism (e.g. email, secure",
      "extractCut": true
    },
    {
      "id": "sec-029-61-determine-readiness-for-scaling-up",
      "number": "6.1",
      "title": "Determine readiness for scaling up",
      "level": 1,
      "pageStart": 66,
      "pageEnd": 68,
      "labelStart": "54",
      "labelEnd": "56",
      "words": 608,
      "summary": {
        "text": "States the prerequisite for scale-up: verifying both that the PCPOSS is technically and operationally ready to scale and that the broader health system is ready to phase out paper and legacy systems.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "legacy systems",
          "heading": false
        },
        {
          "term": "phasing out",
          "heading": false
        },
        {
          "term": "out paper",
          "heading": false
        },
        {
          "term": "pcposs",
          "heading": false
        },
        {
          "term": "scaling",
          "heading": true
        },
        {
          "term": "political buy-in",
          "heading": false
        },
        {
          "term": "maps toolkit",
          "heading": false
        },
        {
          "term": "health authority",
          "heading": false
        }
      ],
      "extract": "CHAPTER 6 Prepare for scale-up To replace a paper system completely, or to replace multiple, disconnected legacy digital systems, successful implementation of a person-centred point of service system (PCPOSS) needs to be scaled up while legacy systems (paper or otherwise) are phased out – a process that requires a great deal of resources and political buy-in. This chapter aims to provide an overview of the key steps",
      "extractCut": true
    },
    {
      "id": "sec-030-62-plan-for-phase-out-of-legacy-systems",
      "number": "6.2",
      "title": "Plan for phase-out of legacy system(s)",
      "level": 1,
      "pageStart": 68,
      "pageEnd": 71,
      "labelStart": "56",
      "labelEnd": "59",
      "words": 1259,
      "summary": {
        "text": "Explains how to assess scale-up readiness using the WHO MAPS toolkit and Digital Health Atlas and how to set SMART (specific, measurable, attainable, relevant, time-bound) objectives and legal/operational policies (including paper backup SOPs for downtime) for phasing out legacy systems, illustrated by Table 5's comprehensive indicators across system functionality, connectivity, power, user adoption, efficiency, care quality, costs, and health outcomes.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "legacy system",
          "heading": true
        },
        {
          "term": "pcposs improve",
          "heading": false
        },
        {
          "term": "service user",
          "heading": false
        },
        {
          "term": "phase-out",
          "heading": true
        },
        {
          "term": "paper system",
          "heading": false
        },
        {
          "term": "health workers",
          "heading": false
        },
        {
          "term": "service delivery",
          "heading": false
        },
        {
          "term": "countrywide coverage",
          "heading": false
        }
      ],
      "extract": "When moving from scale-up to integration and sustainability (see Monitoring and evaluating digital health interventions [99]), answer the following question: What targets, indicators or objectives must the PCPOSS meet for the public health authority to feel comfortable phasing out paper and/or legacy systems? Clear, agreed upon objectives should be set to allow for the phase-out of legacy systems. When these",
      "extractCut": true
    },
    {
      "id": "sec-031-63-monitor-and-evaluate-progress-on-objectives",
      "number": "6.3",
      "title": "Monitor and evaluate progress on objectives",
      "level": 1,
      "pageStart": 71,
      "pageEnd": 71,
      "labelStart": "59",
      "labelEnd": "59",
      "words": 117,
      "summary": {
        "text": "Emphasizes establishing a rigorous monitoring and evaluation plan to track progress against scale-up objectives and points implementers, researchers, and policy-makers to WHO's Monitoring and evaluating digital health interventions guide for assessing implementation fidelity and impact.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "digital health",
          "heading": false
        },
        {
          "term": "health interventions",
          "heading": false
        },
        {
          "term": "progress",
          "heading": true
        },
        {
          "term": "objectives",
          "heading": true
        }
      ],
      "extract": "With clear objectives and indicators to measure progress towards them, it is crucial that the PCPOSS has a clear and robust monitoring and evaluation plan and methodology. WHO offers a practical guide, Monitoring and evaluating digital health interventions (99), with detailed stepwise guidance that is beyond the scope of this handbook. The guidance helps with improving the quality and value of monitoring and",
      "extractCut": true
    },
    {
      "id": "sec-032-64-phase-out-of-legacy-systems",
      "number": "6.4",
      "title": "Phase-out of legacy system(s)",
      "level": 1,
      "pageStart": 71,
      "pageEnd": 71,
      "labelStart": "59",
      "labelEnd": "59",
      "words": 233,
      "summary": {
        "text": "Advises phasing out paper and legacy digital systems in a staged, region-by-region or province-by-province manner rather than waiting for nationwide readiness, enabling manageable resource allocation and cross-provincial learning in coordination with key stakeholders.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "legacy",
          "heading": true
        },
        {
          "term": "out paper",
          "heading": false
        },
        {
          "term": "paper systems",
          "heading": false
        },
        {
          "term": "phasing out",
          "heading": false
        },
        {
          "term": "phase out",
          "heading": false
        },
        {
          "term": "phase-out",
          "heading": true
        },
        {
          "term": "province",
          "heading": false
        }
      ],
      "extract": "Strategically, it is advised to not wait until the entire country is ready to phase out paper systems and/or legacy systems and instead phase out those systems in a staged, or step-wise, manner. For example, if one region or province is ready to phase out paper systems completely, but other provinces are still in the process of adopting PCPOSSs, it might be better to begin the phase out of the paper system in the",
      "extractCut": true
    },
    {
      "id": "sec-033-65-adopt-change-management-practices",
      "number": "6.5",
      "title": "Adopt change management practices",
      "level": 1,
      "pageStart": 71,
      "pageEnd": 72,
      "labelStart": "59",
      "labelEnd": "60",
      "words": 244,
      "summary": {
        "text": "Discusses embedding multi-level change management strategies and cultivating a culture of electronic data use across health workers, supervisors, and programme managers—linking mature data use to SMART Guidelines Layer 5 (Dynamic guidelines and advanced analytics)—while warning that a backup paper system must always remain available for crisis or cybersecurity resilience.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "change management",
          "heading": true
        },
        {
          "term": "advanced analytics",
          "heading": false
        },
        {
          "term": "digital systems",
          "heading": false
        },
        {
          "term": "health system",
          "heading": false
        },
        {
          "term": "health workers",
          "heading": false
        },
        {
          "term": "public health",
          "heading": false
        },
        {
          "term": "big",
          "heading": false
        },
        {
          "term": "smart",
          "heading": false
        }
      ],
      "extract": "As the PCPOSS is adopted and increasingly integrated into routine use, the phasing out of paper systems entirely will require behaviour change, not just at the level of health workers, but within the public health authority itself. Successful change management is a key factor in implementing any new process or system, but it is especially important for implementing new digital systems. Switching from paper to",
      "extractCut": true
    },
    {
      "id": "sec-034-references",
      "number": null,
      "title": "References",
      "level": 1,
      "pageStart": 72,
      "pageEnd": 75,
      "labelStart": "60",
      "labelEnd": "63",
      "words": 2438,
      "summary": {
        "text": "Lists the 107 bibliographic references cited across the handbook, spanning WHO digital health guidelines, SMART Guidelines and Digital adaptation kits (DAKs), business process management and BPMN standards, human-centred design toolkits, enterprise architecture and interoperability frameworks (TOGAF, OpenHIE, HL7 FHIR, WHO-FIC, LOINC, SNOMED-GPS), data protection laws, and M&E/scale-up toolkits, and introduces the Annexes section.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "accessed january",
          "heading": false
        },
        {
          "term": "accessed october",
          "heading": false
        },
        {
          "term": "accessed september",
          "heading": false
        },
        {
          "term": "fhir release",
          "heading": false
        },
        {
          "term": "telecommunication union",
          "heading": false
        },
        {
          "term": "international telecommunication",
          "heading": false
        },
        {
          "term": "world health",
          "heading": false
        },
        {
          "term": "health organization",
          "heading": false
        }
      ],
      "extract": "1. Consolidated guidelines on person-centred HIV strategic information: strengthening routine data for impact. Geneva: World Health Organization; 2022 (https://iris.who.int/handle/10665/360948). 2. WHO guideline: recommendations on digital interventions for health system strengthening. Geneva: World Health Organization; 2019 (https://apps.who.int/iris/handle/10665/311941). 3. Classification of digital interventions,",
      "extractCut": true
    },
    {
      "id": "sec-035-principles-for-digital-development",
      "number": null,
      "title": "Principles for digital development",
      "level": 1,
      "pageStart": 76,
      "pageEnd": 79,
      "labelStart": "64",
      "labelEnd": "67",
      "words": 1125,
      "summary": {
        "text": "Presents Annex 1 (summarizing the nine Principles for Digital Development: understand the existing ecosystem, share/reuse/improve, design with people, design for inclusion, build for sustainability, establish people-first data practices, create open and transparent practices, anticipate and mitigate harms, and use evidence to improve outcomes) and Annex 2 (a structured facility-visit interview worksheet for capturing health workers' background, daily tasks, patient load, outreach, referrals, communication, barriers, and motivations).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "typical day",
          "heading": false
        },
        {
          "term": "service users",
          "heading": false
        },
        {
          "term": "outreach session",
          "heading": false
        },
        {
          "term": "busy day",
          "heading": false
        },
        {
          "term": "digital development",
          "heading": true
        },
        {
          "term": "nurse midwife",
          "heading": false
        },
        {
          "term": "health service",
          "heading": false
        },
        {
          "term": "topic questions",
          "heading": false
        }
      ],
      "extract": "ANNEX 1. Principles for digital development | Principle | Description | | --- | --- | | **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",
      "extractCut": true
    },
    {
      "id": "sec-036-observations-worksheet",
      "number": null,
      "title": "Observations worksheet",
      "level": 1,
      "pageStart": 80,
      "pageEnd": 81,
      "labelStart": "68",
      "labelEnd": "69",
      "words": 357,
      "summary": {
        "text": "Presents Annex 3, a two-part facility observations worksheet for recording (1) the facility work environment—services provided, catchment population, staffing counts, electricity, network connectivity, device usage, and operating hours—and (2) the step-by-step path and duration of each observed health service user visit from clinic arrival through departure and external follow-up.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "worksheet",
          "heading": true
        },
        {
          "term": "service user",
          "heading": false
        },
        {
          "term": "facility",
          "heading": false
        },
        {
          "term": "health service",
          "heading": false
        },
        {
          "term": "observations",
          "heading": true
        },
        {
          "term": "electricity",
          "heading": false
        }
      ],
      "extract": "ANNEX 3. Observations worksheet **The work environment** To be completed once per facility. | Field | Notes / Questions | | --- | --- | | **Facility name** | | | **General description of services** | • What health services are provided at this facility? | | **Catchment population** | • Which populations is this health facility serving | | **Number of staff** | • Full time<br>• Part time<br>• Volunteers | |",
      "extractCut": true
    },
    {
      "id": "sec-037-user-persona-worksheet",
      "number": null,
      "title": "User persona worksheet",
      "level": 1,
      "pageStart": 82,
      "pageEnd": 82,
      "labelStart": "70",
      "labelEnd": "70",
      "words": 301,
      "summary": {
        "text": "Presents Annex 4, a structured user persona worksheet for profiling each end-user type across demographics, persona name/photo/occupational group, expected vs. actual daily/weekly/monthly responsibilities, work context and infrastructure connectivity, routine challenges (with interview quotes), and personal/professional motivations and performance metrics.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "persona worksheet",
          "heading": true
        },
        {
          "term": "user persona",
          "heading": true
        },
        {
          "term": "worker occupational",
          "heading": false
        },
        {
          "term": "health worker",
          "heading": false
        },
        {
          "term": "occupational group",
          "heading": false
        },
        {
          "term": "health service",
          "heading": false
        },
        {
          "term": "photo",
          "heading": false
        },
        {
          "term": "success",
          "heading": false
        }
      ],
      "extract": "ANNEX 4. User persona worksheet A user persona worksheet that summarizes each and every type of end-user (e.g. community health worker, district health officer, health service user) should be completed. | Section | Prompts | | --- | --- | | **Persona title (e.g. nurse)** | | | **Name, photo and type of persona** | • Name (real or illustrative)<br>• Photo or illustration of persona (helps with visualization and",
      "extractCut": true
    },
    {
      "id": "sec-038-user-stories-worksheet",
      "number": null,
      "title": "User stories worksheet",
      "level": 1,
      "pageStart": 83,
      "pageEnd": 83,
      "labelStart": "71",
      "labelEnd": "71",
      "words": 130,
      "summary": {
        "text": "Presents Annex 5, a three-column worksheet template ('As a…', 'I want to…', 'So that…') with an obstetric referral example for capturing end-user needs and translating them into functional and non-functional system requirements.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "user stories",
          "heading": true
        },
        {
          "term": "worksheet",
          "heading": true
        },
        {
          "term": "gynaecology department",
          "heading": false
        },
        {
          "term": "non-functional requirements",
          "heading": false
        }
      ],
      "extract": "ANNEX 5. User stories worksheet User stories help to illustrate the end-users’ views of how they want to use the PCPOSS, which can eventually be translated into functional and non-functional requirements (see section 3.8). | As a… | I want to… | So that… | | --- | --- | --- | | *User persona(s) wanting the use case (see Annex 4)* | *What the user wants to be able to do with the system (i.e. functional and",
      "extractCut": true
    },
    {
      "id": "sec-039-business-process-matrix-guide",
      "number": null,
      "title": "Business process matrix guide",
      "level": 1,
      "pageStart": 84,
      "pageEnd": 84,
      "labelStart": "72",
      "labelEnd": "72",
      "words": 311,
      "summary": {
        "text": "Presents Annex 6, a guide defining the six columns of a business process matrix—business process number, process name, process ID (e.g., DAK convention FP.B), participating personas (corresponding to BPMN swim lanes), process objectives, and task set with start/end triggers.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "business process",
          "heading": true
        },
        {
          "term": "process matrix",
          "heading": true
        },
        {
          "term": "service user",
          "heading": false
        },
        {
          "term": "health worker",
          "heading": false
        },
        {
          "term": "row",
          "heading": false
        },
        {
          "term": "letter",
          "heading": false
        },
        {
          "term": "nurse",
          "heading": false
        },
        {
          "term": "involved",
          "heading": false
        }
      ],
      "extract": "ANNEX 6. Business process matrix guide The business process matrix provides an overview of all the key processes that are involved. This overview serves as an inventory of all the business processes that have been or will be mapped into workflows (see section 3.3). Each row should describe an individual business process with the following information needed for each row, under separate columns. | What to note |",
      "extractCut": true
    },
    {
      "id": "sec-040-form-inventory-guide",
      "number": null,
      "title": "Form inventory guide",
      "level": 1,
      "pageStart": 85,
      "pageEnd": 85,
      "labelStart": "73",
      "labelEnd": "73",
      "words": 443,
      "summary": {
        "text": "Presents Annex 7, a column-by-column guide for logging paper and digital forms in a forms inventory table, capturing form ID, form version/date, local and translated form titles, form type (service delivery register vs. supervisory reporting form), responsible and receiving occupational groups, submission frequency, linked workflow activity ID, and owning authority.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "form",
          "heading": true
        },
        {
          "term": "form title",
          "heading": false
        },
        {
          "term": "form version",
          "heading": false
        },
        {
          "term": "worker occupational",
          "heading": false
        },
        {
          "term": "inventory",
          "heading": true
        },
        {
          "term": "health worker",
          "heading": false
        },
        {
          "term": "occupational group",
          "heading": false
        },
        {
          "term": "reporting purposes",
          "heading": false
        }
      ],
      "extract": "ANNEX 7. Form inventory guide The following explains the information needed for each paper or digital form, which should be logged in separate rows in a table. For each row of the inventory, the following columns should be filled out. This helps organize what data will need to be collected to reflect existing data collection workflows. | Inventory column | Description of information entered | | --- | --- | | **Form",
      "extractCut": true
    },
    {
      "id": "sec-041-form-data-mapping-guide",
      "number": null,
      "title": "Form data mapping guide",
      "level": 1,
      "pageStart": 86,
      "pageEnd": 89,
      "labelStart": "74",
      "labelEnd": "77",
      "words": 1977,
      "summary": {
        "text": "Presents Annex 8, a comprehensive column guide for mapping form data elements in a spreadsheet—covering activity ID, form ID, original and standardized data element labels, definitions, HL7 FHIR/UCUM-aligned data types and quantity subtypes, calculations, optionality (R/O/C) and conditionality, duplication flags, functional groupings, linkages to aggregate indicators, decision-support tables, and scheduling tables, orphaned record flags, and mappings/relationships to standardized terminologies (ICD-11, SNOMED-GPS, LOINC).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "data mapping",
          "heading": true
        },
        {
          "term": "form data",
          "heading": true
        },
        {
          "term": "element label",
          "heading": false
        },
        {
          "term": "element contributes",
          "heading": false
        },
        {
          "term": "element appears",
          "heading": false
        },
        {
          "term": "quantity data",
          "heading": false
        },
        {
          "term": "duplicated data",
          "heading": false
        },
        {
          "term": "list select",
          "heading": false
        }
      ],
      "extract": "ANNEX 8. Form data mapping guide The following guide helps organize and map which data elements are collected from each paper form currently used. A spreadsheet should be created to document this information. Each data element should be noted in a separate row in the spreadsheet. For each row, the following columns should be filled out. This initial form data mapping will help with streamlining data collection",
      "extractCut": true
    },
    {
      "id": "sec-042-aggregate-indicator-mapping-guide",
      "number": null,
      "title": "Aggregate indicator mapping guide",
      "level": 1,
      "pageStart": 90,
      "pageEnd": 91,
      "labelStart": "78",
      "labelEnd": "79",
      "words": 843,
      "summary": {
        "text": "Presents Annex 9 (a guide for documenting aggregate indicators calculated from point-of-care data, including indicator ID, name, definition, numerator/denominator descriptions and data-dictionary-linked formulas, reporting frequency, disaggregation, targets/alerts, and guideline references), Annex 10 (guides for the decision-support logic overview matrix and scheduling logic overview matrix, with links to five WHO DAKs), and the opening field definitions and DMN hit policy indicators (Unique, Rule order, First) of Annex 11.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "decision-support logic",
          "heading": false
        },
        {
          "term": "logic description",
          "heading": false
        },
        {
          "term": "scheduling logic",
          "heading": false
        },
        {
          "term": "indicator",
          "heading": true
        },
        {
          "term": "adaptation kit",
          "heading": false
        },
        {
          "term": "indicator here",
          "heading": false
        },
        {
          "term": "description note",
          "heading": false
        },
        {
          "term": "data dictionary",
          "heading": false
        }
      ],
      "extract": "ANNEX 9. Aggregate indicator mapping guide A spreadsheet should be created to document the indicators that can be calculated from the individual level data that is collected from the PCPOSS. This guide provides a way to consolidate and organize this list of indicators. | What to note | Description | | --- | --- | | **Indicator ID** | The Indicator ID should be a running number or letter that would facilitate",
      "extractCut": true
    },
    {
      "id": "sec-043-template-for-a-decision-support-table",
      "number": null,
      "title": "Template for a decision-support table",
      "level": 1,
      "pageStart": 92,
      "pageEnd": 93,
      "labelStart": "80",
      "labelEnd": "81",
      "words": 775,
      "summary": {
        "text": "Presents the DMN-adapted decision-support table template for Annex 11—showing how hit policy (U/R/F), rule IDs, conjunctive (same-row AND) and disjunctive (different-row OR) input expressions, system actions, data-element outputs, health worker guidance displays, annotations, and guideline references are structured—along with links to five WHO DAKs containing detailed decision-support table examples.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "decision-support table",
          "heading": true
        },
        {
          "term": "entry output",
          "heading": false
        },
        {
          "term": "decision-support logic",
          "heading": false
        },
        {
          "term": "input entry",
          "heading": false
        },
        {
          "term": "hit policy",
          "heading": false
        },
        {
          "term": "rule number",
          "heading": false
        },
        {
          "term": "rule order",
          "heading": false
        },
        {
          "term": "input expression",
          "heading": false
        }
      ],
      "extract": "ANNEX 11. Template for a decision-support table The decision-support table template provides a structured way of parsing out the logic into clear “if/then” statements with a clear list of inputs and action, and outputs. It has been adapted from the Decision Model and Notation (DMN) standard. | Field | Description | | --- | --- | | **Decision-support table ID** | The Decision support table ID should correspond to the",
      "extractCut": true
    },
    {
      "id": "sec-044-scheduling-logic-table-guide",
      "number": null,
      "title": "Scheduling logic table guide",
      "level": 1,
      "pageStart": 94,
      "pageEnd": 94,
      "labelStart": "82",
      "labelEnd": "82",
      "words": 595,
      "summary": {
        "text": "Presents Annex 12, an illustrative guide and worked example (using the hepatitis B birth dose vaccination schedule) for documenting health service scheduling logic across service name, description, trigger event and date, creation condition, due/overdue/expiration date formulas, completion action, safety risks and alternative schedules, implementation comments, and WHO guideline references.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "scheduling logic",
          "heading": true
        },
        {
          "term": "service schedule",
          "heading": false
        },
        {
          "term": "expiration date",
          "heading": false
        },
        {
          "term": "overdue date",
          "heading": false
        },
        {
          "term": "logic table",
          "heading": true
        },
        {
          "term": "trigger date",
          "heading": false
        },
        {
          "term": "child birthdate",
          "heading": false
        },
        {
          "term": "hepatitis vaccine",
          "heading": false
        }
      ],
      "extract": "ANNEX 12. Scheduling logic table guide This illustrative guide can be used to inform how to document health service schedules. The example of the hepatitis B birth dose vaccination schedule is shown here, which is needed to inform clinical decision support. Additional rows for subsequent hepatitis B vaccine doses would be added to complete the hepatitis B vaccination scheduling logic table. The complexity of",
      "extractCut": true
    },
    {
      "id": "sec-045-prioritization-of-requirements-guide",
      "number": null,
      "title": "Prioritization of requirements guide",
      "level": 1,
      "pageStart": 95,
      "pageEnd": 95,
      "labelStart": "83",
      "labelEnd": "83",
      "words": 436,
      "summary": {
        "text": "Presents Annex 13, a table guide for transparently documenting and prioritizing system requirements by recording requirement ID, description, type (functional vs. non-functional), priority tier (high/'need-to-have', medium/'should-have', low/'nice-to-have'), stakeholder/guideline/regulatory sources, and stakeholder validation comments.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "functional requirement",
          "heading": false
        },
        {
          "term": "requirement here",
          "heading": false
        },
        {
          "term": "requirement required",
          "heading": false
        },
        {
          "term": "prioritization",
          "heading": true
        },
        {
          "term": "pcposs",
          "heading": false
        },
        {
          "term": "priority",
          "heading": false
        },
        {
          "term": "non-functional",
          "heading": false
        },
        {
          "term": "guide",
          "heading": true
        }
      ],
      "extract": "ANNEX 13. Prioritization of requirements guide With a long list of functional and non-functional requirements, but a constrained set of resources (budget and time), it will be critical to ensure an accurate assessment of which functions or features are “need-to-have” (high priority) versus “nice-to-have” (low priority). This guide notes how to transparently document the decisions made on prioritization in a table",
      "extractCut": true
    },
    {
      "id": "sec-046-hl7-fhir-standard-components",
      "number": null,
      "title": "HL7 FHIR standard components",
      "level": 1,
      "pageStart": 96,
      "pageEnd": 98,
      "labelStart": "84",
      "labelEnd": "86",
      "words": 573,
      "summary": {
        "text": "Presents Annex 14, defining the core components of the HL7 FHIR standard—FHIR Resources, FHIR Implementation Guides (including their role as SMART Guidelines Layer 3 machine-readable artefacts building on Layer 2 DAKs), FHIR Profiles, FHIR Stores, and FHIR APIs—followed by Annex 14 references and back-matter WHO contact details.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "fhir standard",
          "heading": true
        },
        {
          "term": "fhir api",
          "heading": false
        },
        {
          "term": "fhir resource",
          "heading": false
        },
        {
          "term": "fhir release",
          "heading": false
        },
        {
          "term": "fhir profiles",
          "heading": false
        },
        {
          "term": "fhir implementation",
          "heading": false
        },
        {
          "term": "accessed october",
          "heading": false
        },
        {
          "term": "apis",
          "heading": false
        }
      ],
      "extract": "ANNEX 14. HL7 FHIR standard components Resources A “FHIR Resource” is a modular component that serves as the basic data exchange format in the HL7 FHIR standard. A FHIR Resource contains the data elements, constraints on those data elements and the data relationships that together make up an exchangeable data model, in the context of health data (1). Each FHIR Resource also contains links to relevant information in",
      "extractCut": true
    }
  ],
  "checks": {
    "figureSequenceGaps": []
  },
  "withheld": false,
  "keywords": [
    {
      "term": "digital health",
      "heading": true
    },
    {
      "term": "implementing pcposs",
      "heading": false
    },
    {
      "term": "pcposs improve",
      "heading": false
    },
    {
      "term": "digital system",
      "heading": true
    },
    {
      "term": "interoperable pcposs",
      "heading": false
    },
    {
      "term": "pcposs meet",
      "heading": false
    },
    {
      "term": "user health",
      "heading": false
    },
    {
      "term": "health service",
      "heading": true
    },
    {
      "term": "pcposs encompasses",
      "heading": false
    },
    {
      "term": "data health",
      "heading": false
    },
    {
      "term": "system requirements",
      "heading": false
    },
    {
      "term": "digital adaptation",
      "heading": false
    }
  ],
  "pageLabels": [
    {
      "physical": 1,
      "label": "A",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 2,
      "label": "B",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 3,
      "label": "i",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 4,
      "label": "ii",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 5,
      "label": "iii",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 6,
      "label": "iv",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 7,
      "label": "v",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 8,
      "label": "vi",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 9,
      "label": "vii",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 10,
      "label": "viii",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 11,
      "label": "ix",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 12,
      "label": "x",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 13,
      "label": "1",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 14,
      "label": "2",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 15,
      "label": "3",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 16,
      "label": "4",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 17,
      "label": "5",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 18,
      "label": "6",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 19,
      "label": "7",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 20,
      "label": "8",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 21,
      "label": "9",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 22,
      "label": "10",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 23,
      "label": "11",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 24,
      "label": "12",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 25,
      "label": "13",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 26,
      "label": "14",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 27,
      "label": "15",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 28,
      "label": "16",
      "source": "pdf-labels",
      "confidence": 1
    },
    {
      "physical": 29,
      "label": "17",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 30,
      "label": "18",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 31,
      "label": "19",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 32,
      "label": "20",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 33,
      "label": "21",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 34,
      "label": "22",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 35,
      "label": "23",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 36,
      "label": "24",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 37,
      "label": "25",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 38,
      "label": "26",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 39,
      "label": "27",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 40,
      "label": "28",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 41,
      "label": "29",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 42,
      "label": "30",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 43,
      "label": "31",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 44,
      "label": "32",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 45,
      "label": "33",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 46,
      "label": "34",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 47,
      "label": "35",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 48,
      "label": "36",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 49,
      "label": "37",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 50,
      "label": "38",
      "source": "pdf-labels",
      "confidence": 1
    },
    {
      "physical": 51,
      "label": "39",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 52,
      "label": "40",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 53,
      "label": "41",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 54,
      "label": "42",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 55,
      "label": "43",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 56,
      "label": "44",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 57,
      "label": "45",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 58,
      "label": "46",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 59,
      "label": "47",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 60,
      "label": "48",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 61,
      "label": "49",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 62,
      "label": "50",
      "source": "pdf-labels",
      "confidence": 1
    },
    {
      "physical": 63,
      "label": "51",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 64,
      "label": "52",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 65,
      "label": "53",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 66,
      "label": "54",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 67,
      "label": "55",
      "source": "pdf-labels",
      "confidence": 0.85
    },
    {
      "physical": 68,
      "label": "56",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 69,
      "label": "57",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 70,
      "label": "58",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 71,
      "label": "59",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 72,
      "label": "60",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 73,
      "label": "61",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 74,
      "label": "62",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 75,
      "label": "63",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 76,
      "label": "64",
      "source": "pdf-labels",
      "confidence": 1
    },
    {
      "physical": 77,
      "label": "65",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 78,
      "label": "66",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 79,
      "label": "67",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 80,
      "label": "68",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 81,
      "label": "69",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 82,
      "label": "70",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 83,
      "label": "71",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 84,
      "label": "72",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 85,
      "label": "73",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 86,
      "label": "74",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 87,
      "label": "75",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 88,
      "label": "76",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 89,
      "label": "77",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 90,
      "label": "78",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 91,
      "label": "79",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 92,
      "label": "80",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 93,
      "label": "81",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 94,
      "label": "82",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 95,
      "label": "83",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 96,
      "label": "84",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 97,
      "label": "85",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 98,
      "label": "86",
      "source": "pdf-labels",
      "confidence": 0.7
    }
  ],
  "figures": [
    {
      "kind": "figure",
      "number": "1",
      "title": "From paper to digital: a transformational journey",
      "page": 15,
      "pageLabel": "3",
      "confidence": 0.95,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "2",
      "title": "The 2019 WHO guideline: recommendations on digital interventions for health system strengthening",
      "page": 16,
      "pageLabel": "4",
      "confidence": 0.95,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "3",
      "title": "Primary health care digital ecosystem",
      "page": 17,
      "pageLabel": "5",
      "confidence": 0.95,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "4",
      "title": "The added value of “collect once, use for many purposes” principle",
      "page": 19,
      "pageLabel": "7",
      "confidence": 0.95,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "5",
      "title": "WHO SMART Guidelines approach",
      "page": 20,
      "pageLabel": "8",
      "confidence": 0.95,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "6",
      "title": "Planning and implementing a digital health enterprise: phases, steps and resources",
      "page": 24,
      "pageLabel": "12",
      "confidence": 0.95,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "box",
      "number": "1",
      "title": "Unique identifiers",
      "page": 25,
      "pageLabel": "13",
      "confidence": 0.8,
      "evidence": [
        "referenced",
        "in-sequence"
      ]
    },
    {
      "kind": "figure",
      "number": "7",
      "title": "Steps in this handbook to optimize a person-centred point of service system (PCPOSS)",
      "page": 26,
      "pageLabel": "14",
      "confidence": 0.95,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "8",
      "title": "Example prompts and questions for starting broad and narrowing down",
      "page": 32,
      "pageLabel": "20",
      "confidence": 0.95,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "9",
      "title": "Example business process matrix from family planning DAK",
      "page": 35,
      "pageLabel": "23",
      "confidence": 0.95,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "table",
      "number": "1",
      "title": "Key Business Process Model and Notation (BPMN) symbols",
      "page": 36,
      "pageLabel": "24",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence"
      ]
    },
    {
      "kind": "figure",
      "number": "10",
      "title": "Workflow A: Registration business process",
      "page": 38,
      "pageLabel": "26",
      "confidence": 0.95,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "11",
      "title": "Notes and annotations for Workflow A: Registration business process",
      "page": 38,
      "pageLabel": "26",
      "confidence": 0.95,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "12",
      "title": "Is each and every data element collected truly needed?",
      "page": 41,
      "pageLabel": "29",
      "confidence": 0.95,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "13",
      "title": "Example decision-support logic matrix from DAK for HIV",
      "page": 45,
      "pageLabel": "33",
      "confidence": 0.95,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "14",
      "title": "Decision-support logic for a clinical care pathway in the form of a decision tree",
      "page": 46,
      "pageLabel": "34",
      "confidence": 0.95,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "figure",
      "number": "15",
      "title": "Levels of insight gained from different prototypes",
      "page": 54,
      "pageLabel": "42",
      "confidence": 0.95,
      "evidence": [
        "referenced",
        "in-sequence",
        "graphic"
      ]
    },
    {
      "kind": "table",
      "number": "2",
      "title": "Types of architecture domains",
      "page": 57,
      "pageLabel": "45",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence"
      ]
    },
    {
      "kind": "table",
      "number": "3",
      "title": "Types of interoperability in health",
      "page": 57,
      "pageLabel": "45",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence"
      ]
    },
    {
      "kind": "table",
      "number": "4",
      "title": "Types of standards",
      "page": 58,
      "pageLabel": "46",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence"
      ]
    },
    {
      "kind": "table",
      "number": "5",
      "title": "Key indicators of whether a digital system meets its objectives",
      "page": 69,
      "pageLabel": "57",
      "confidence": 0.9,
      "evidence": [
        "referenced",
        "in-sequence"
      ]
    }
  ],
  "images": [
    {
      "id": "img-p001-1",
      "file": "images/img-p001-1.png",
      "page": 1,
      "narratives": {
        "en": "A blank, solid white rectangular image with no visible graphic content; the original artwork could not be determined from the extracted image.",
        "fr": "Image rectangulaire blanche unie et vierge sans contenu graphique visible ; l'illustration d'origine n'a pas pu être déterminée à partir de l'image extraite.",
        "es": "Imagen rectangular blanca sólida y en blanco sin contenido gráfico visible; la ilustración original no pudo determinarse a partir de la imagen extraída.",
        "ar": "صورة مستطيلة بيضاء خالصة وفارغة دون أي محتوى رسومي مرئي؛ ولم يتسنَّ تحديد الرسم الأصلي من الصورة المستخرجة.",
        "ru": "Пустое сплошное белое прямоугольное изображение без видимого графического содержимого; исходное изображение не удалось определить по извлеченному файлу.",
        "zh": "空白纯白矩形图像，无可见图形内容；无法从提取的图像中确定原始图稿。"
      },
      "state": "draft"
    },
    {
      "id": "img-p003-1",
      "file": "images/img-p003-1.png",
      "page": 3,
      "narratives": {
        "en": "The logo of the WHO Human Reproduction Programme (HRP), reading \"human reproduction programme hrp.\" in blue and grey lettering, with the tagline \"research for impact\" beneath it and the co-sponsoring agencies UNDP, UNFPA, UNICEF, WHO and the World Bank listed at the bottom. It appears on the handbook's imprint page among the credits for contributing WHO programmes.",
        "fr": "Logo du Programme spécial de recherche, de développement et de formation à la recherche en reproduction humaine (HRP) de l'OMS, portant l'inscription « human reproduction programme hrp. » en caractères bleus et gris, avec la devise « research for impact » en dessous et les organismes coparrainants PNUD (UNDP), FNUAP (UNFPA), UNICEF, OMS (WHO) et Banque mondiale (World Bank) énumérés en bas. Il figure sur la page d'ours du manuel parmi les mentions des programmes contributeurs de l'OMS.",
        "es": "Logotipo del Programa Especial de Investigaciones, Desarrollo y Formación de Investigadores sobre Reproducción Humana (HRP) de la OMS, con el texto «human reproduction programme hrp.» en letras azules y grises, el lema «research for impact» debajo y los organismos copatrocinadores PNUD (UNDP), UNFPA, UNICEF, OMS (WHO) y el Banco Mundial (World Bank) enumerados en la parte inferior. Aparece en la página de créditos del manual entre las menciones de los programas colaboradores de la OMS.",
        "ar": "شعار برنامج الإنجاب البشري (HRP) التابع لمنظمة الصحة العالمية، مكتوباً عليه «human reproduction programme hrp.» بحروف زرقاء ورمادية، وتحته الشعار اللفظي «research for impact»، مع إدراج الوكالات المشاركة في الرعاية (برنامج الأمم المتحدة الإنمائي UNDP، وصندوق الأمم المتحدة للسكان UNFPA، واليونيسف UNICEF، ومنظمة الصحة العالمية WHO، والبنك الدولي World Bank) في الأسفل. ويظهر في صفحة بيانات النشر الخاصة بالدليل ضمن اعتمادات برامج منظمة الصحة العالمية المساهمة.",
        "ru": "Логотип Специальной программы ВОЗ по научным исследованиям, разработкам и подготовке научных кадров в области воспроизводства населения (HRP) с надписью «human reproduction programme hrp.» синим и серым шрифтом, подзаголовком «research for impact» под ней и перечнем организаций-коспонсоров (ПРООН/UNDP, ЮНФПА/UNFPA, ЮНИСЕФ/UNICEF, ВОЗ/WHO и Всемирный банк/World Bank) внизу. Расположен на странице выходных данных руководства среди упоминаний участвовавших программ ВОЗ.",
        "zh": "世界卫生组织人类生殖研究、发展和研究培训特别规划（HRP）徽标，以蓝灰双色字体印有“human reproduction programme hrp.”，下方印有口号“research for impact”，底部列出共同发起机构联合国开发计划署（UNDP）、联合国人口基金（UNFPA）、联合国儿童基金会（UNICEF）、世界卫生组织（WHO）和世界银行（World Bank）。它出现在手册版权页上参与贡献的世卫组织规划署名中。"
      },
      "state": "draft"
    },
    {
      "id": "vfig-p015",
      "file": "figures/vfig-p015.png",
      "page": 15,
      "shows": [
        "1"
      ],
      "narratives": {
        "en": "Fig. 1, 'From paper to digital: a transformational journey'. The upper half is a rising staircase of four stages, each an icon and a heading — PAPER, DIGITIZATION, DIGITALIZATION, DIGITAL TRANSFORMATION — joined by arrows labelled 'From paper to digital', 'Improve existing processes' and 'Fundamentally change healthcare delivery'. A vertical axis, 'Data use', runs from 'Limited data use with little to no interoperability standards adopted' at the bottom to 'Greater data use with greater adoption of interoperability standards' at the top; a horizontal arrow beneath is labelled 'Process Optimization'. The lower half is a table with one column per stage (Paper, Digitization, Digitalization, Digital transformation) and five rows: Definition, Examples, Benefits, Challenges and Dependencies. For example, Paper is defined as manually capturing and processing data in paper formats, with examples such as paper register books and tally sheets; Digital transformation is defined as digitally optimizing and driving systems-level change through innovation, analytics and feedback mechanisms, with examples such as algorithms for personalized treatment plans."
      },
      "state": "draft"
    },
    {
      "id": "img-p016-1",
      "file": "images/img-p016-1.png",
      "page": 16,
      "narratives": {
        "en": "The cover of the WHO publication \"WHO guideline: recommendations on digital interventions for health system strengthening,\" showing the title over an illustration of health workers and a patient seated around a desk with a computer, with the WHO emblem at the bottom. It appears in the Introduction alongside the discussion of that 2019 guideline and its Recommendation 8 on digital tracking of clients' health status and services combined with decision support.",
        "fr": "Couverture de la publication de l'OMS intitulée « WHO guideline: recommendations on digital interventions for health system strengthening », montrant le titre au-dessus d'une illustration représentant des agents de santé et un patient assis autour d'un bureau équipé d'un ordinateur, avec l'emblème de l'OMS en bas. Elle figure dans l'introduction en regard de la présentation de cette ligne directrice de 2019 et de sa recommandation 8 sur le suivi numérique de l'état de santé et des services des patients combiné à l'aide à la décision.",
        "es": "Portada de la publicación de la OMS titulada «WHO guideline: recommendations on digital interventions for health system strengthening», que muestra el título sobre una ilustración de trabajadores sanitarios y un paciente sentados alrededor de un escritorio con una computadora, con el emblema de la OMS en la parte inferior. Aparece en la Introducción junto al análisis de esa directriz de 2019 y su Recomendación 8 sobre el seguimiento digital del estado de salud y los servicios de los usuarios combinado con el apoyo a la toma de decisiones.",
        "ar": "غلاف منشور منظمة الصحة العالمية المعنون «WHO guideline: recommendations on digital interventions for health system strengthening»، ويُظهر العنوان فوق رسم توضيحي لعاملين صحيين ومريض يجلسون حول مكتب عليه حاسوب، مع شارة منظمة الصحة العالمية في الأسفل. ويظهر في المقدمة إلى جانب مناقشة ذلك المبدأ التوجيهي الصادر عام 2019 وتوصيته الثامنة بشأن التتبع الرقمي للحالة الصحية للمراجعين والخدمات المقدمة لهم مقترناً بدعم اتخاذ القرار.",
        "ru": "Обложка публикации ВОЗ «WHO guideline: recommendations on digital interventions for health system strengthening», на которой заголовок расположен над иллюстрацией медицинских работников и пациента, сидящих за столом с компьютером, а внизу помещена эмблема ВОЗ. Приводится во введении рядом с обсуждением этого руководства 2019 года и его рекомендации 8 о цифровом отслеживании состояния здоровья и обслуживания пациентов в сочетании с поддержкой принятия решений.",
        "zh": "世界卫生组织出版物《WHO guideline: recommendations on digital interventions for health system strengthening》（世卫组织指南：关于加强卫生系统的数字干预措施的建议）的封面，标题下方为医务人员与患者围坐在配有电脑的办公桌旁的插图，底部印有世卫组织会徽。它出现在导言中，配合介绍该 2019 年指南及其关于将服务对象健康状况和服务数字追踪与决策支持相结合的第 8 项建议。"
      },
      "state": "draft"
    },
    {
      "id": "vfig-p017",
      "file": "figures/vfig-p017.png",
      "page": 17,
      "shows": [
        "3"
      ],
      "narratives": {
        "en": "Fig. 3, 'Delivering an integrated ecosystem of information systems and digital health solutions supports the PHC approach'. Four nested layers surround a figure labelled 'Centered around the needs of the care seeker'. From innermost to outermost: COMMUNITY LINKAGES AND ENGAGEMENT (community health workers, care seekers) holds patient portal, targeted messaging, CHW job aid, self-monitoring devices and capacity building; ORGANIZATION AND MANAGEMENT (primary care providers) holds clinical job aids, AI risk assessment, referral and coordination, and an electronic health record; SELECTION, DESIGN AND PLANNING OF SERVICES (health system decision makers) holds a dashboard and management information systems; DEFINING A TARGET POPULATION AND UNDERSTANDING THEIR NEEDS (policy makers) holds civil registration and vital statistics, and disease surveillance. Each solution carries a one-line purpose. A note says solutions can span more than one layer and are allocated to one only for illustration."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p019",
      "file": "figures/vfig-p019.png",
      "page": 19,
      "shows": [
        "4"
      ],
      "narratives": {
        "en": "Fig. 4, 'The added value of “collect once, use for many purposes” principle'. Five stacked tiers rise from a person icon at the base. Bottom to top: Primary, individual data collection (clinical, lab, pharmacy, registries and ID data); Person-centred health service delivery (clinical decision support, scheduling, case management); Programme management (operational decision support, quality improvement, facility management, process optimization); Health system monitoring (national strategic plans and policies, national indicators, accountability); and Global monitoring (accountability towards the SDGs). A side bar groups the lower two tiers as 'Primary data use' and the upper three as 'Secondary data use'."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p020",
      "file": "figures/vfig-p020.png",
      "page": 20,
      "shows": [
        "5"
      ],
      "narratives": {
        "en": "Fig. 5, 'WHO SMART Guidelines approach'. A 'Research and evidence base' bar feeds five knowledge layers, each with its product: 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 layer passes through a 'Localisation' bar into a matching country-implementation adaptation: national policies and guidelines (L1), localised requirements (L2), localised machine-readable code and standards (L3), localised static digital services (L4) and dynamic digital applications optimised for local outcomes (L5). All five feed 'Data, evidence, and impact', which loops back to the evidence base as 'Evidence from digital implementations'."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p024",
      "file": "figures/vfig-p024.png",
      "page": 24,
      "shows": [
        "6"
      ],
      "narratives": {
        "en": "Fig. 6, 'Planning and implementing a digital health enterprise: phases, steps and resources'. Seven numbered phases run down the left: 01 Assessing the current state and enabling environment; 02 Establishing a shared understanding and strategic planning; 03 Defining the future state; 04 Planning the enterprise architecture; 05 Determining health content requirements; 06 M&E of digital health implementations and fostering data use; 07 Implementing, maintaining and scaling. Each phase lists its steps, for example 'Develop a national digital health strategy' in phase 02 and 'Identify validated health content appropriate for the implementation context' in phase 05. To the right, resource tiles are placed against the phase(s) they serve, some spanning several phases, and each is marked as a PDF for print or an online environment. They include the WHO–ITU national eHealth strategy toolkit, the Digital implementation investment guide (DIIG), the WHO SMART guidelines with digital adaptation kits and machine-readable recommendations, TOGAF, Open HIE, ICD-11, HL7 FHIR, LOINC, the WHO MAPS toolkit and Ethics and governance of artificial intelligence for health. The tile 'WHO handbook for digitalizing primary health care (this document)' sits in phase 05."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p026",
      "file": "figures/vfig-p026.png",
      "page": 26,
      "shows": [
        "7"
      ],
      "narratives": {
        "en": "Fig. 7, 'Iterative and agile approach'. Three circular loops sit along a horizontal timeline arrow: Minimum viable product (MVP), then VERSION 1, then VERSION 2. Each loop has the same four stages: understand and prioritize user requirements, design (adapt design in later versions), build and test, and train users. Milestones along the arrow read: determine that a PCPOSS is an appropriate health intervention; repeat the previous loop until meeting MVP specs to deploy; deploy and roll out; gather and manage user feedback; deploy and roll out; gather and manage user feedback; deploy, roll out and scale; and iterations for continuous improvement."
      },
      "state": "draft"
    },
    {
      "id": "img-p030-1",
      "file": "images/img-p030-1.png",
      "page": 30,
      "narratives": {
        "en": "The cover of the WHO SMART Guidelines publication \"Digital adaptation kit for tuberculosis: operational requirements for implementing WHO recommendations in digital systems,\" carrying the \"SMART GUIDELINES\" banner and the WHO logo. It is one of three example Digital Adaptation Kit (DAK) covers shown where the handbook discusses DAKs as a desk-review resource and reviews what DAKs contain.",
        "fr": "Couverture de la publication SMART Guidelines de l'OMS intitulée « Digital adaptation kit for tuberculosis: operational requirements for implementing WHO recommendations in digital systems », portant le bandeau « SMART GUIDELINES » et le logo de l'OMS. Il s'agit de l'une des trois couvertures d'exemples de kits d'adaptation numérique (DAK) présentées lorsque le manuel aborde les DAK comme ressource d'examen documentaire et passe en revue leur contenu.",
        "es": "Portada de la publicación SMART Guidelines de la OMS titulada «Digital adaptation kit for tuberculosis: operational requirements for implementing WHO recommendations in digital systems», con la banda «SMART GUIDELINES» y el logotipo de la OMS. Es una de las tres portadas de ejemplo de kits de adaptación digital (DAK) que se muestran donde el manual analiza los DAK como recurso de revisión documental y examina su contenido.",
        "ar": "غلاف منشور المبادئ التوجيهية الذكية (SMART Guidelines) التابع لمنظمة الصحة العالمية والمعنون «Digital adaptation kit for tuberculosis: operational requirements for implementing WHO recommendations in digital systems»، ويحمل شريط «SMART GUIDELINES» وشعار منظمة الصحة العالمية. وهو أحد ثلاثة أغلفة أمثلة لمجموعات التكييف الرقمي (DAK) المعروضة حيث يناقش الدليل مجموعات التكييف الرقمي كمورد للمراجعة المكتبية ويستعرض محتوياتها.",
        "ru": "Обложка публикации ВОЗ из серии SMART Guidelines «Digital adaptation kit for tuberculosis: operational requirements for implementing WHO recommendations in digital systems» с баннером «SMART GUIDELINES» и логотипом ВОЗ. Это одна из трех обложек комплектов цифровой адаптации (DAK), приведенных в качестве примеров в разделе руководства, где DAK рассматриваются как источник для кабинетного обзора и описывается их состав.",
        "zh": "世界卫生组织 SMART 指南出版物《Digital adaptation kit for tuberculosis: operational requirements for implementing WHO recommendations in digital systems》（结核病数字适配工具包：在数字系统中实施世卫组织建议的操作要求）的封面，带有“SMART GUIDELINES”横幅和世卫组织徽标。它是手册在探讨将数字适配工具包（DAK）作为案头审查资源并介绍 DAK 内容时所展示的三个 DAK 示例封面之一。"
      },
      "state": "draft"
    },
    {
      "id": "img-p030-2",
      "file": "images/img-p030-2.png",
      "page": 30,
      "narratives": {
        "en": "The cover of the WHO SMART Guidelines publication \"Digital Adaptation Kit for Antenatal Care: operational requirements for implementing WHO recommendations in digital systems,\" carrying the \"SMART GUIDELINES\" banner and the WHO and HRP (\"research for impact\") logos. It is one of three example DAK covers shown where the handbook discusses DAKs as a desk-review resource and reviews what DAKs contain.",
        "fr": "Couverture de la publication SMART Guidelines de l'OMS intitulée « Digital Adaptation Kit for Antenatal Care: operational requirements for implementing WHO recommendations in digital systems », portant le bandeau « SMART GUIDELINES » ainsi que les logos de l'OMS et du HRP (« research for impact »). Il s'agit de l'une des trois couvertures d'exemples de DAK présentées lorsque le manuel aborde les DAK comme ressource d'examen documentaire et passe en revue leur contenu.",
        "es": "Portada de la publicación SMART Guidelines de la OMS titulada «Digital Adaptation Kit for Antenatal Care: operational requirements for implementing WHO recommendations in digital systems», con la banda «SMART GUIDELINES» y los logotipos de la OMS y del HRP («research for impact»). Es una de las tres portadas de ejemplo de DAK que se muestran donde el manual analiza los DAK como recurso de revisión documental y examina su contenido.",
        "ar": "غلاف منشور المبادئ التوجيهية الذكية (SMART Guidelines) التابع لمنظمة الصحة العالمية والمعنون «Digital Adaptation Kit for Antenatal Care: operational requirements for implementing WHO recommendations in digital systems»، ويحمل شريط «SMART GUIDELINES» وشعاري منظمة الصحة العالمية وبرنامج الإنجاب البشري HRP («research for impact»). وهو أحد ثلاثة أغلفة أمثلة لمجموعات التكييف الرقمي (DAK) المعروضة حيث يناقش الدليل مجموعات التكييف الرقمي كمورد للمراجعة المكتبية ويستعرض محتوياتها.",
        "ru": "Обложка публикации ВОЗ из серии SMART Guidelines «Digital Adaptation Kit for Antenatal Care: operational requirements for implementing WHO recommendations in digital systems» с баннером «SMART GUIDELINES» и логотипами ВОЗ и HRP («research for impact»). Это одна из трех обложек примеров DAK, приведенных в разделе руководства, где DAK рассматриваются как источник для кабинетного обзора и описывается их состав.",
        "zh": "世界卫生组织 SMART 指南出版物《Digital Adaptation Kit for Antenatal Care: operational requirements for implementing WHO recommendations in digital systems》（产前保健数字适配工具包：在数字系统中实施世卫组织建议的操作要求）的封面，带有“SMART GUIDELINES”横幅以及世卫组织和 HRP（“research for impact”）徽标。它是手册在探讨将 DAK 作为案头审查资源并介绍 DAK 内容时所展示的三个 DAK 示例封面之一。"
      },
      "state": "draft"
    },
    {
      "id": "img-p030-3",
      "file": "images/img-p030-3.png",
      "page": 30,
      "narratives": {
        "en": "The cover of the WHO SMART Guidelines publication \"Digital adaptation kit for child health (0-59 months) in humanitarian emergencies: operational requirements for implementing WHO recommendations in digital systems,\" carrying the \"SMART GUIDELINES\" banner, icon illustrations of care activities, and the WHO logo. It is one of three example DAK covers shown where the handbook discusses DAKs as a desk-review resource and reviews what DAKs contain.",
        "fr": "Couverture de la publication SMART Guidelines de l'OMS intitulée « Digital adaptation kit for child health (0-59 months) in humanitarian emergencies: operational requirements for implementing WHO recommendations in digital systems », portant le bandeau « SMART GUIDELINES », des illustrations sous forme d'icônes d'activités de soins et le logo de l'OMS. Il s'agit de l'une des trois couvertures d'exemples de DAK présentées lorsque le manuel aborde les DAK comme ressource d'examen documentaire et passe en revue leur contenu.",
        "es": "Portada de la publicación SMART Guidelines de la OMS titulada «Digital adaptation kit for child health (0-59 months) in humanitarian emergencies: operational requirements for implementing WHO recommendations in digital systems», con la banda «SMART GUIDELINES», ilustraciones de iconos de actividades de atención y el logotipo de la OMS. Es una de las tres portadas de ejemplo de DAK que se muestran donde el manual analiza los DAK como recurso de revisión documental y examina su contenido.",
        "ar": "غلاف منشور المبادئ التوجيهية الذكية (SMART Guidelines) التابع لمنظمة الصحة العالمية والمعنون «Digital adaptation kit for child health (0-59 months) in humanitarian emergencies: operational requirements for implementing WHO recommendations in digital systems»، ويحمل شريط «SMART GUIDELINES»، ورسوماً أيقونية لأنشطة الرعاية، وشعار منظمة الصحة العالمية. وهو أحد ثلاثة أغلفة أمثلة لمجموعات التكييف الرقمي (DAK) المعروضة حيث يناقش الدليل مجموعات التكييف الرقمي كمورد للمراجعة المكتبية ويستعرض محتوياتها.",
        "ru": "Обложка публикации ВОЗ из серии SMART Guidelines «Digital adaptation kit for child health (0-59 months) in humanitarian emergencies: operational requirements for implementing WHO recommendations in digital systems» с баннером «SMART GUIDELINES», пиктограммами мероприятий по оказанию помощи и логотипом ВОЗ. Это одна из трех обложек примеров DAK, приведенных в разделе руководства, где DAK рассматриваются как источник для кабинетного обзора и описывается их состав.",
        "zh": "世界卫生组织 SMART 指南出版物《Digital adaptation kit for child health (0-59 months) in humanitarian emergencies: operational requirements for implementing WHO recommendations in digital systems》（人道主义紧急情况下儿童卫生［0–59 个月］数字适配工具包：在数字系统中实施世卫组织建议的操作要求）的封面，带有“SMART GUIDELINES”横幅、护理活动图标插图和世卫组织徽标。它是手册在探讨将 DAK 作为案头审查资源并介绍 DAK 内容时所展示的三个 DAK 示例封面之一。"
      },
      "state": "draft"
    },
    {
      "id": "vfig-p032",
      "file": "figures/vfig-p032.png",
      "page": 32,
      "shows": [
        "8"
      ],
      "narratives": {
        "en": "Fig. 8, 'Example prompts and questions for starting broad and narrowing down'. An inverted pyramid of four bands runs from BROAD (start here) at the top to NARROW (end here) at the tip: TRUST BUMP, BIRD'S EYE VIEW, MAGNIFYING GLASS and MICRO-SCOPE. Beside each band are example interview prompts for health workers: intent and introductions ('Tell me about your background… as a health worker'); 'Tell me about the last time you… registered a new client / provided antenatal care / provided a routine immunization to a child'; 'Can you tell me more… about how you check for malaria?' and 'Can you show me how you… would fill out a paper register now?'; and the 5 Whys ('Why do you… wait until the end of the day to fill out your records?'), continued until a root cause is revealed. It closes with 'Express gratitude for health worker's time'. Adapted from Tran, 2018, under CC BY-NC-SA 4.0."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p035",
      "file": "figures/vfig-p035.png",
      "page": 35,
      "shows": [
        "9"
      ],
      "narratives": {
        "en": "Fig. 9, 'Example business process matrix from family planning DAK'. A table with the columns Process name, Process ID, Personas, Objectives and Task set, the header row defining each column. Three processes follow. A Registration (FP.A), with client and clerk or health-care provider, ensures the client is in the system and queued for counselling; its tasks are to search for, review and update, or create a client record. B Family planning counselling (FP.B), with client and health-care provider, discusses methods and selects one the client is medically eligible for; its tasks run from taking a history and a risk assessment through checking medical eligibility criteria and stock to referral if the facility cannot provide the method. C Service provision (FP.C) provides the chosen method, covering informed consent, start timing, dual protection and follow-up scheduling. Source: WHO (30)."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p038",
      "file": "figures/vfig-p038.png",
      "page": 38,
      "shows": [
        "10",
        "11"
      ],
      "narratives": {
        "en": "Fig. 10, 'Workflow A: Registration business process', is a BPMN-style swimlane diagram. The pool is 'Health facility', with lanes Client and Health worker or Clerk. The client arrives at the facility (1), then rapid assessment and management (2) leads to 'Urgent referral necessary?' (3); Yes ends in C. ANC referral. No leads to gather client details (4), then search for client (5) and 'Match found?' (6). No leads to create client record (7); Yes leads to a grouped subprocess 8, Validate client details: review sociodemographic data with the client (8.1), 'Update needed?' (8.2), then update client details (8.3). Both paths reach check-in client (9), ending in B. ANC contact. Fig. 11, 'Notes and annotations for Workflow A: Registration business process', is a three-column text panel that annotates each numbered activity of Fig. 10 — for example, that rapid assessment is outside the DAK's scope, and the identifiers a client may present when searched for. Both cite WHO (29)."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p042",
      "file": "figures/vfig-p042.png",
      "page": 42,
      "shows": [
        "12"
      ],
      "narratives": {
        "en": "Fig. 12, 'Is each and every data element collected truly needed?'. Three rows, each reading Question → Explanation → Action to be taken, with arrows chaining each row's action into the next question. 1. Is the data element duplicated? Duplicates may share a definition under different labels, or be collected on several forms; reconcile them into one element collected once. 2. Is the data element needed for service delivery or accountability? Ask whether it supports clinical decision-making, mandatory reporting or accountability; if not, consider removing it to reduce the data-entry burden on health workers. 3. Is the data element orphaned? Orphaned data is hard to use without its context; link it to its primary data elements (anything not needed will already have gone at question 2)."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p045",
      "file": "figures/vfig-p045.png",
      "page": 45,
      "shows": [
        "13"
      ],
      "narratives": {
        "en": "Fig. 13, 'Example decision-support logic matrix from DAK for HIV'. A table with four columns: activity ID and name, decision table ID, decision table description, and reference/source. It has six rows, HIV.DT.01 to HIV.DT.06: check for serious illness; test for HIV using the testing algorithm; determine retest recommendation; PrEP eligibility check; determine PEP or PrEP regimen; and screen for TB. Each row cites the WHO consolidated guideline section it is drawn from — for example the 2019 consolidated guidelines on HIV testing services, and its figures on universal HIV testing and early infant diagnosis. Source: WHO (31)."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p046",
      "file": "figures/vfig-p046.png",
      "page": 46,
      "shows": [
        "14"
      ],
      "narratives": {
        "en": "Fig. 14, 'Decision-support logic for a clinical care pathway in the form of a decision tree'. It starts at 'Antenatal registration — provider-initiated HIV testing & counselling' and splits on the result. HIV-positive leads to PMTCT, treatment, support and an offer of partner notification, then partner testing. Partner HIV-negative leads to reassessing the woman's risk and offering partner referral for VMMC. Partner not tested or HIV-positive leads to offering the partner HIV treatment (if positive), condom promotion and risk-reduction counselling. HIV-negative leads to standard post-test guidance and counselling on prevention, then two branches: offer partner testing and a risk assessment (which feeds partner testing), and a risk assessment using a tool. That tool separates a woman at substantial risk of HIV acquisition from one who is not. At substantial risk, she is offered comprehensive prevention options — STI screening and treatment, condom promotion, risk-reduction counselling, PrEP with emphasis on adherence, and follow-up ANC visits. A woman who chooses to initiate PrEP then receives clinical laboratory assessments, adherence counselling, and emphasis on follow-up visits and repeat HIV testing. Source: WHO (29)."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p054",
      "file": "figures/vfig-p054.png",
      "page": 54,
      "shows": [
        "15"
      ],
      "narratives": {
        "en": "Fig. 15, 'Levels of insight gained from different prototypes'. The vertical axis is level of prototype fidelity and the horizontal axis is the time required to develop the protocol. An arrow climbs through three phases: Validation, with low-fidelity prototypes (sketches, wireframes); Refinement, with moderate-fidelity prototypes (mockups); and Deployment, with higher-fidelity prototypes (clickable prototypes). Under each phase are the questions it answers. Validation asks: do users need this, and would this digital record solve their administrative reporting problems? Refinement asks: could it improve service delivery or accountability, and will users use it as intended? Deployment asks: does it have the key features, will users adopt it, and what behaviour change or roadblocks to adoption must be addressed? Adapted from Norman Tran/Stanford school (35)."
      },
      "state": "draft"
    },
    {
      "id": "img-p068-1",
      "file": "images/img-p068-1.png",
      "page": 68,
      "narratives": {
        "en": "The cover of \"The MAPS Toolkit: mHealth Assessment and Planning for Scale,\" showing a photograph of a health worker demonstrating a mobile device to a woman holding a child, with the logos of the United Nations Foundation, the Johns Hopkins University Global mHealth Initiative, WHO and HRP (\"research for impact\") along the bottom. It illustrates the WHO MAPS toolkit referenced in the handbook's discussion of assessing and planning for scale-up.",
        "fr": "Couverture de « The MAPS Toolkit: mHealth Assessment and Planning for Scale », montrant la photographie d'un agent de santé présentant un appareil mobile à une femme tenant un enfant, avec les logos de la Fondation des Nations Unies, de la Global mHealth Initiative de l'Université Johns Hopkins, de l'OMS et du HRP (« research for impact ») alignés en bas. Elle illustre la boîte à outils MAPS de l'OMS référencée dans l'examen de l'évaluation et de la planification du passage à l'échelle.",
        "es": "Portada de «The MAPS Toolkit: mHealth Assessment and Planning for Scale», que muestra una fotografía de un trabajador sanitario enseñando un dispositivo móvil a una mujer con un niño en brazos, con los logotipos de la Fundación de las Naciones Unidas, la Global mHealth Initiative de la Universidad Johns Hopkins, la OMS y el HRP («research for impact») en la parte inferior. Ilustra el conjunto de herramientas MAPS de la OMS citado en la sección del manual sobre evaluación y planificación de la ampliación a escala.",
        "ar": "غلاف «The MAPS Toolkit: mHealth Assessment and Planning for Scale»، ويُظهر صورة فوتوغرافية لعامل صحي يشرح استخدام جهاز محمول لامرأة تحمل طفلاً، مع شعارات مؤسسة الأمم المتحدة، ومبادرة الصحة المحمولة العالمية بجامعة جونز هوبكنز، ومنظمة الصحة العالمية، وبرنامج الإنجاب البشري HRP («research for impact») على طول الجزء السفلي. ويوضح مجموعة أدوات MAPS التابعة لمنظمة الصحة العالمية والمشار إليها في مناقشة الدليل لتقييم وتخطيط التوسع.",
        "ru": "Обложка издания «The MAPS Toolkit: mHealth Assessment and Planning for Scale» с фотографией медицинского работника, демонстрирующего мобильное устройство женщине с ребенком на руках, и расположенными внизу логотипами Фонда ООН, Глобальной инициативы по мобильному здравоохранению Университета Джонса Хопкинса, ВОЗ и программы HRP («research for impact»). Иллюстрирует инструментарий ВОЗ MAPS, упоминаемый в разделе руководства об оценке и планировании масштабирования.",
        "zh": "《The MAPS Toolkit: mHealth Assessment and Planning for Scale》（MAPS 工具包：移动卫生评估与规模化规划）的封面，展示一名医务人员向一位抱着孩子的妇女演示移动设备的照片，底部排列着联合国基金会、约翰斯·霍普金斯大学全球移动卫生倡议、世界卫生组织和 HRP（“research for impact”）的徽标。它展示了手册在讨论规模化评估与规划时所引用的世卫组织 MAPS 工具包。"
      },
      "state": "draft"
    },
    {
      "id": "img-p071-1",
      "file": "images/img-p071-1.png",
      "page": 71,
      "narratives": {
        "en": "The cover of \"Monitoring and Evaluating Digital Health Interventions: A practical guide to conducting research and assessment,\" showing a close-up photograph of hands holding a tablet over paper forms on a desk, a row of four colored circles, and the logos of WHO, HRP (\"research for impact\"), the Johns Hopkins University Global mHealth Initiative and the United Nations Foundation. It illustrates the practical guide cited as reference (99) in the section on monitoring and evaluating progress on objectives.",
        "fr": "Couverture de « Monitoring and Evaluating Digital Health Interventions: A practical guide to conducting research and assessment », montrant une photographie en gros plan de mains tenant une tablette au-dessus de formulaires papier sur un bureau, une rangée de quatre cercles colorés et les logos de l'OMS, du HRP (« research for impact »), de la Global mHealth Initiative de l'Université Johns Hopkins et de la Fondation des Nations Unies. Elle illustre le guide pratique cité en référence (99) dans la section sur le suivi et l'évaluation des progrès accomplis vers les objectifs.",
        "es": "Portada de «Monitoring and Evaluating Digital Health Interventions: A practical guide to conducting research and assessment», que muestra una fotografía en primer plano de unas manos sosteniendo una tableta sobre formularios en papel en un escritorio, una fila de cuatro círculos de colores y los logotipos de la OMS, el HRP («research for impact»), la Global mHealth Initiative de la Universidad Johns Hopkins y la Fundación de las Naciones Unidas. Ilustra la guía práctica citada como referencia (99) en la sección sobre seguimiento y evaluación del progreso hacia los objetivos.",
        "ar": "غلاف «Monitoring and Evaluating Digital Health Interventions: A practical guide to conducting research and assessment»، ويُظهر صورة مقربة ليدين تمسكان بجهاز لوحي فوق استمارات ورقية على مكتب، وصفاً من أربع دوائر ملونة، وشعارات منظمة الصحة العالمية، وبرنامج الإنجاب البشري HRP («research for impact»)، ومبادرة الصحة المحمولة العالمية بجامعة جونز هوبكنز، ومؤسسة الأمم المتحدة. ويوضح الدليل العملي المستشهد به كمرجع (99) في القسم الخاص برصد وتقييم التقدم المحرز في تحقيق الأهداف.",
        "ru": "Обложка издания «Monitoring and Evaluating Digital Health Interventions: A practical guide to conducting research and assessment» с фотографией крупным планом рук, держащих планшет над бумажными бланками на столе, рядом из четырех цветных кругов и логотипами ВОЗ, программы HRP («research for impact»), Глобальной инициативы по мобильному здравоохранению Университета Джонса Хопкинса и Фонда ООН. Иллюстрирует практическое руководство, цитируемое под номером (99) в разделе о мониторинге и оценке прогресса в достижении целей.",
        "zh": "《Monitoring and Evaluating Digital Health Interventions: A practical guide to conducting research and assessment》（监测和评估数字卫生干预措施：开展研究与评估的实用指南）的封面，展示双手在办公桌纸质表格上方握持平板电脑的特写照片、一排四个彩色圆圈，以及世界卫生组织、HRP（“research for impact”）、约翰斯·霍普金斯大学全球移动卫生倡议和联合国基金会的徽标。它展示了关于监测和评估目标进展章节中作为参考文献 (99) 引用的实用指南。"
      },
      "state": "draft"
    },
    {
      "id": "img-p098-1",
      "file": "images/img-p098-1.png",
      "page": 98,
      "narratives": {
        "en": "A printed barcode (EAN/UPC style) encoding the book's ISBN, with the digit string \"9789240093362\" printed above the bars and \"9 789240 093362\" printed below, as it appears on the back cover.",
        "fr": "Code-barres imprimé (de type EAN/UPC) encodant l'ISBN de l'ouvrage, avec la séquence de chiffres « 9789240093362 » imprimée au-dessus des barres et « 9 789240 093362 » en dessous, tel qu'il figure sur la quatrième de couverture.",
        "es": "Código de barras impreso (estilo EAN/UPC) que codifica el ISBN del libro, con la cadena de dígitos «9789240093362» impresa encima de las barras y «9 789240 093362» debajo, tal como aparece en la contraportada.",
        "ar": "رمز شريطي مطبوع (بنمط EAN/UPC) يُشفّر الرقم الدولي المعياري للكتاب (ISBN)، مع طباعة سلسلة الأرقام «9789240093362» أعلى الأشرطة و«9 789240 093362» أسفلها، كما يظهر على الغلاف الخلفي.",
        "ru": "Напечатанный штрихкод (формата EAN/UPC), кодирующий ISBN книги, со строкой цифр «9789240093362» над полосами и «9 789240 093362» под ними на задней обложке.",
        "zh": "编码本书 ISBN 的印刷条形码（EAN/UPC 样式），条形码上方印有数字串“9789240093362”，下方印有“9 789240 093362”，位于封底。"
      },
      "state": "draft"
    }
  ],
  "coverage": [
    {
      "kind": "contents",
      "state": "found",
      "count": 54,
      "note": "outline"
    },
    {
      "kind": "sections",
      "state": "found",
      "count": 48,
      "note": "one level"
    },
    {
      "kind": "figures",
      "state": "found",
      "count": 22
    },
    {
      "kind": "tables",
      "state": "not-extracted",
      "note": "5 captioned in the text"
    },
    {
      "kind": "references",
      "state": "not-extracted",
      "note": "a references section is in the text (p72); its entries are not extracted"
    },
    {
      "kind": "glossary",
      "state": "not-extracted",
      "note": "a glossary section is in the text (p7); its entries are not extracted"
    },
    {
      "kind": "footnotes",
      "state": "not-extracted"
    },
    {
      "kind": "summaries",
      "state": "found",
      "count": 48,
      "note": "48 of 48 sections"
    }
  ],
  "links": {
    "repo": "litlfred/who-iris",
    "branch": "main",
    "dir": "library/9789240093362-eng"
  }
}
