{
  "$schema": "folio-library-entry/v1",
  "id": "9789240093362-eng",
  "blocks": [
    {
      "id": "library/9789240093362-eng/blocks/figure-img-p001-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 1,
      "pageEnd": 1,
      "target": "../images/img-p001-1.png",
      "narrative": "draft",
      "content": "A blank, solid white rectangular image with no visible graphic content; the original artwork could not be determined from the extracted image.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-front-matter",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Front matter",
      "pageStart": 1,
      "pageEnd": 6,
      "target": "../sections/sec-front-matter.md",
      "narrative": null,
      "content": "Digital \ntransformation \nhandbook \nfor primary \nhealth care\nOptimizing person-centred \npoint of service systems\nDigital \ntransformation \nhandbook \nfor primary \nhealth care\nOptimizing person-centred \npoint of service systems\nDigital transformation handbook for primary health care: optimizing person-centred point of service systems\nISBN 978-92-4-009336-2 (electronic version)\nISBN 978-92-4-009337-9 (print version)\n© World Health Organization 2024\nSome rights reserved. This work is available under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 IGO licence \n(CC BY-NC-SA 3.0 IGO; http",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-img-p003-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 3,
      "pageEnd": 3,
      "target": "../images/img-p003-1.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-000",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Acknowledgements",
      "pageStart": 6,
      "pageEnd": 7,
      "target": "../sections/sec-000-acknowledgements.md",
      "narrative": null,
      "content": "The World Health Organization (WHO) is grateful for the contributions made by many individuals and organizations in the \ndevelopment of this handbook.\nThis handbook was developed by Carl Leitner, Garrett Mehl, Akshita Palliwal, Natschja Ratanaprayul and Ritika Rawlani of the \nWHO Department of Digital Health and Innovations (Geneva, Switzerland); Tigest Tamrat of the WHO Department of Sexual and \nReproductive Health and Research (Geneva, Switzerland); Jennifer Snyder of Jhpiego (Baltimore, United States of America); and \nCarolyn Footitt of Ona (Nairobi, Kenya).\nThe following individuals review",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-001",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Abbreviations",
      "pageStart": 7,
      "pageEnd": 7,
      "target": "../sections/sec-001-abbreviations.md",
      "narrative": null,
      "content": "| Abbreviation | Definition |\n| --- | --- |\n| ANC | antenatal care |\n| API | application programming interface |\n| BPMN | Business Process Model and Notation |\n| CRDM | Collaborative Requirements Development Methodology |\n| DAK | Digital adaptation kit |\n| DBP | diastolic blood pressure |\n| DHA | Digital Health Atlas |\n| DICOM | Digital Imaging and Communications in Medicine |\n| DIIG | Digital Implementation Investment Guide |\n| EA | enterprise architecture |\n| FHIR | Fast Healthcare Interoperability Resources |\n| HL7 | Health Level Seven |\n| HRP | UNDP-UNFPA-UNICEF-WHO-World Bank Special Prog",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-002",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Glossary",
      "pageStart": 8,
      "pageEnd": 12,
      "target": "../sections/sec-002-glossary.md",
      "narrative": null,
      "content": "| Term | Definition |\n| --- | --- |\n| Algorithm | A specification of how a computer shall solve a problem, perform a calculation and execute a task. |\n| 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. |\n| As-is | The current state of things (also see to-be). |\n| Beta version | The initial version of the software, after prototyping, that is available for testing among a limited group of people. |\n| Build | In the context of developing a person-centred point of service system (P",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-003",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Introduction",
      "pageStart": 13,
      "pageEnd": 18,
      "target": "../sections/sec-003-introduction.md",
      "narrative": null,
      "content": "CHAPTER 1\nIntroduction\nIn many countries, individual-level paper-based systems – paper registers (including immunization \nregistries), health service user charts, medical (or health) records and home-based records – are \nused by health workers and health service users (i.e. patients, clients, beneficiaries, individuals \nwho receive health services), across all health programmes, at all levels of the health system. \nTransitioning legacy paper and digital systems to interoperable, integrated and comprehensive \ndigital systems that promote health system objectives and improve data utilization is",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-vfig-p015",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 15,
      "pageEnd": 15,
      "target": "../figures/vfig-p015.png",
      "narrative": "draft",
      "content": "Fig. 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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-img-p016-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 16,
      "pageEnd": 16,
      "target": "../images/img-p016-1.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-vfig-p017",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 17,
      "pageEnd": 17,
      "target": "../figures/vfig-p017.png",
      "narrative": "draft",
      "content": "Fig. 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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-004",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Person-centred point of service systems",
      "pageStart": 18,
      "pageEnd": 20,
      "target": "../sections/sec-004-11-person-centred-point-of-service-systems.md",
      "narrative": null,
      "content": "A person-centered point of service system (PCPOSS), digital in nature, facilitates the provision and \ndelivery of health services to individuals (i.e. persons, clients, patients, health service users) at the \npoint of care. \nA PCPOSS includes software capabilities that enable health-\ncare providers to access, record and update individuals’ \nhealth information as well as interactively communicate with \nthem. The term PCPOSS encompasses various services and \napplication types, including:\n•\t Decision support systems: digital “tools which combine \nmedical information databases and algorithms with",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-vfig-p019",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 19,
      "pageEnd": 19,
      "target": "../figures/vfig-p019.png",
      "narrative": "draft",
      "content": "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'.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-vfig-p020",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 20,
      "pageEnd": 20,
      "target": "../figures/vfig-p020.png",
      "narrative": "draft",
      "content": "Fig. 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'.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-005",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "SMART Guidelines",
      "pageStart": 20,
      "pageEnd": 21,
      "target": "../sections/sec-005-12-smart-guidelines.md",
      "narrative": null,
      "content": "SMART Guidelines are Standards-based, Machine-readable, Adaptive, Requirements-based, and \nTestable recommended digital capabilities, health and data content. SMART Guidelines are WHO’s \napproach designed to systematize and accelerate the consistent application of recommended, life-\nsaving interventions in the digital age (18). \nAs countries are investing heavily in PCPOSSs, SMART \nGuidelines provide detailed specifications, documentation \nand encoded content to facilitate accurate and consistent \nincorporation of WHO clinical, public health, data and \ninteroperability recommendations into PCP",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-006",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "How this handbook was developed",
      "pageStart": 21,
      "pageEnd": 21,
      "target": "../sections/sec-006-13-how-this-handbook-was-developed.md",
      "narrative": null,
      "content": "This practical guide was developed from the experiences and feedback of a variety of experts and \ndigital health practitioners. Experiences, insights, templates and feedback were gathered through a \nseries of consultations, a working group, expert interviews and dedicated feedback sessions. \nThis included lessons learned from a study on digitalizing \npaper-based routine health information systems across \ndifferent contexts, including Bangladesh, Pakistan and \nIndonesia (12). Additionally, the approach outlined within \nthis workbook leverages the Collaborative Requirements \nDevelopment Methodol",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-007",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Targeted scenarios of digital readiness",
      "pageStart": 22,
      "pageEnd": 23,
      "target": "../sections/sec-007-21-targeted-scenarios-of-digital-readiness.md",
      "narrative": null,
      "content": "CHAPTER 2\nHow to use this handbook\n\nThis chapter outlines how this handbook can be leveraged by key stakeholders and provides \nreferences to key resources for creating or updating a PCPOSS – whether from the early point of \ndigitizing paper forms in paper-based systems or updating legacy digital systems to improve the \nintegration of care pathways. Point of service systems that combine community-based information \nsystems, decision support systems, electronic health record systems, and personal health records \nare, for short, a person-centred point of service system (PCPOSS). There are many he",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-008",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Targeted users",
      "pageStart": 23,
      "pageEnd": 24,
      "target": "../sections/sec-008-22-targeted-users.md",
      "narrative": null,
      "content": "This handbook is aimed at individuals and teams seeking to \ngather and optimize the content and functional requirements \nfor either adapting a PCPOSS or developing one bespoke. \nIt is written for those with a public health and/or clinical \nbackground who have a baseline understanding of health \ninformation systems but may not be technologists themselves.\nIn essence, this handbook is written for those who will fill \nthe business analyst role on the team, and those who will \nplay a key role in solution design. This can include people \nwho work specifically in health informatics or in relevant \np",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-vfig-p024",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 24,
      "pageEnd": 24,
      "target": "../figures/vfig-p024.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-009",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Before using this resource",
      "pageStart": 24,
      "pageEnd": 26,
      "target": "../sections/sec-009-23-before-using-this-resource.md",
      "narrative": null,
      "content": "The key assumption for users of this resource is that a \ncomprehensive high-level needs assessment and strategic \nplanning has already been conducted and concluded that \nimplementing a PCPOSS is crucial for operationalizing a \ncountry’s digital health strategy. This needs assessment should \nhave included a root-cause analysis illustrating the need for \nthe PCPOSS to improve service delivery and accountability \nmeasures. If such a needs assessment has not been done, \nrefer to the WHO publication, Digital implementation \ninvestment guide (DIIG): integrating digital interventions \ninto health pro",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-vfig-p026",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 26,
      "pageEnd": 26,
      "target": "../figures/vfig-p026.png",
      "narrative": "draft",
      "content": "Fig. 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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-010",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "The stepwise approaches to digitizing",
      "pageStart": 26,
      "pageEnd": 27,
      "target": "../sections/sec-010-24-the-stepwise-approaches-to-digitizing.md",
      "narrative": null,
      "content": "Adhering to the Principles for Digital Development (see Annex 1), \nthis handbook is organized in a stepwise manner that begins \nwith the assumption of a limited or no digital system in place. \nIt is a starting point for detailing plans to implement an \nenterprise-grade system planned for national scale up and \nintegration with other national-level systems for long-term \nsustainability. \nThis handbook outlines the end-to-end process that will help \ntransition from a paper system to a digital system. At a high \nlevel, this process includes the following steps which serve the \nbasis for the struc",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-011",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Choices for software and digital applications",
      "pageStart": 27,
      "pageEnd": 27,
      "target": "../sections/sec-011-25-choices-for-software-and-digital-applications.md",
      "narrative": null,
      "content": "Implementation teams using this handbook are not \nexpected to use any specific software applications during the \nrequirements-gathering and detailed design processes. \nRegardless of the chosen technology used, the only strong \nrecommendation would be to ensure robust, high-quality \ndocumentation of the requirements of the system and its design. \nCollaboration tools such as project management and file sharing \ntools (e.g. Microsoft Teams, Slack, Google Drive) should be used to \nimprove the capacity for knowledge sharing within, and between, \nimplementing teams and others involved in the digitiz",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-012",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Follow key requirement-gathering methods",
      "pageStart": 28,
      "pageEnd": 33,
      "target": "../sections/sec-012-31-follow-key-requirement-gathering-methods.md",
      "narrative": null,
      "content": "CHAPTER 3\nUnderstand user requirements\n\nThe 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.\n\nThis 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 in-depth discussions and interviews with key stakeholders. Stakeholders include, but are not limited to, end-users of the system (e.g. appropriate health worker occupational grou",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-img-p030-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 30,
      "pageEnd": 30,
      "target": "../images/img-p030-1.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-img-p030-2",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 30,
      "pageEnd": 30,
      "target": "../images/img-p030-2.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-img-p030-3",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 30,
      "pageEnd": 30,
      "target": "../images/img-p030-3.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-vfig-p032",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 32,
      "pageEnd": 32,
      "target": "../figures/vfig-p032.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-013",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Get to know the users",
      "pageStart": 33,
      "pageEnd": 35,
      "target": "../sections/sec-013-32-get-to-know-the-users.md",
      "narrative": null,
      "content": "Following the first principle of digital development (design with the user), user-centred design \nstarts with getting to know the people you are designing for through conversation, observation \nand co-creation. User personas, use cases and user stories are critical tools used in the design \nprocess to better understand exactly who the users are and what their needs are. Having an in-depth \nunderstanding of who the user is and co-creating designs with the user themselves will lead to a \nhigher chance of uptake and long-term usage of the system. \n3.2.1 \t Create user personas \nA user persona is a",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-vfig-p035",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 35,
      "pageEnd": 35,
      "target": "../figures/vfig-p035.png",
      "narrative": "draft",
      "content": "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).",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-014",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Map business processes and workflows",
      "pageStart": 35,
      "pageEnd": 39,
      "target": "../sections/sec-014-33-map-business-processes-and-workflows.md",
      "narrative": null,
      "content": "Business processes are sets of related activities and tasks performed to achieve a specific objective \n(6–9). In health care, business processes include, among many other things, health service user \nregistration, counselling, service provision and referral.\nWorkflows are a visual representation of the progression of activities (tasks, events, interactions) \nperformed within a business process (45). The specific activities or tasks depicted in a workflow \ninclude manual and machine-automated activities. \nUnderstanding the experiences of intended users and their \ndaily interactions is an essent",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-vfig-p038",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 38,
      "pageEnd": 38,
      "target": "../figures/vfig-p038.png",
      "narrative": "draft",
      "content": "Fig. 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).",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-015",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Streamline data collection and indicator reporting",
      "pageStart": 39,
      "pageEnd": 42,
      "target": "../sections/sec-015-34-streamline-data-collection-and-indicator-repo.md",
      "narrative": null,
      "content": "Streamlining data collection is a long and tedious task, but it is the crux of translating paper register \nsystems into a PCPOSS. The following are the five key steps needed to complete the streamlining.\n1.\t\nCreate an inventory of paper forms.\n2.\t\nMap data elements across all forms.\n3.\t\nCompile all aggregate indicators that need to be linked \nand reported.\n4.\t\nRemove duplicated, orphaned and unnecessary data.\n5.\t\nStreamline data collection and indicators into a \nconsolidated data dictionary.\nComprehensive paper \nreplacement\nIf there is already a clear list of the data to collect, \neither from",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-vfig-p042",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 42,
      "pageEnd": 42,
      "target": "../figures/vfig-p042.png",
      "narrative": "draft",
      "content": "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).",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-016",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Create a data dictionary",
      "pageStart": 42,
      "pageEnd": 44,
      "target": "../sections/sec-016-35-create-a-data-dictionary.md",
      "narrative": null,
      "content": "The final step in streamlining data collection and indicator reporting is to create a data dictionary, \nwhich (in this context) is a repository of all the data elements essential for individual and aggregate \nlevels, including some metadata components, that will be included in the PCPOSS. \nFor the purposes of designing the solution and facilitating \nunderstanding across multiple stakeholders, the data \ndictionary will also include the data elements’ related \nattributes, plus a mapping to standard classifications and \nterminology concepts. Data dictionaries should utilize \ninteroperability stan",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-017",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Determine decision-support logic",
      "pageStart": 44,
      "pageEnd": 47,
      "target": "../sections/sec-017-36-determine-decision-support-logic.md",
      "narrative": null,
      "content": "Digital systems can go beyond simple data collection and aggregation by introducing additional \nlayers of sophistication that are generally unavailable on paper. This includes the opportunity to \nenhance care provision with built-in decision-support logic. \nIn PCPOSSs, embedded decision-support logic can help health \nworkers follow appropriate clinical care pathways set out by \nWHO and national public health authorities’ guidelines and \nrecommendations. The decision-support logic that can be \nintegrated includes: \n•\t scheduling\n•\t asking\n•\t risk assessment for triage and/or referrals\n•\t medica",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-vfig-p045",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 45,
      "pageEnd": 45,
      "target": "../figures/vfig-p045.png",
      "narrative": "draft",
      "content": "Fig. 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).",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-vfig-p046",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 46,
      "pageEnd": 46,
      "target": "../figures/vfig-p046.png",
      "narrative": "draft",
      "content": "Fig. 14, '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).",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-018",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Map health service schedules",
      "pageStart": 47,
      "pageEnd": 47,
      "target": "../sections/sec-018-37-map-health-service-schedules.md",
      "narrative": null,
      "content": "Service schedules give health workers an overview of upcoming, due or overdue services, and aim to \nensure timeliness of service delivery and continuity of care. Service schedules can also be a basis for \nreminders that are sent from the PCPOSS to health service users about upcoming services, if targeted \nhealth service user communication is an intervention included in the PCPOSS. \nWorkflow mapping already completed by following section \n3.3 is a good starting point for understanding if any health \nservices are recurring (e.g. TB treatment) or need to be \nprovided on a prescribed schedule (e.g",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-019",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Gather and prioritize requirements",
      "pageStart": 47,
      "pageEnd": 49,
      "target": "../sections/sec-019-38-gather-and-prioritize-requirements.md",
      "narrative": null,
      "content": "The requirements for a PCPOSS are the functional and non-functional criteria that it must meet to \nensure end-users are satisfied and the system performs as intended. \nThe following two types of requirements need to be gathered \nand prioritized. \n•\t Functional requirements describe what the system must \nbe able to do (“the water bottle shall be able to store liquid \nwithout leaking” would be an everyday example).\n•\t Non-functional requirements describe how the system \nwill work (“the water bottle must not weigh more than \n0.5 kg and must be blue in colour”, to continue the simple \nexample).\nTh",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-020",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Finalize software and vendor selection",
      "pageStart": 50,
      "pageEnd": 53,
      "target": "../sections/sec-020-41-finalize-software-and-vendor-selection.md",
      "narrative": null,
      "content": "CHAPTER 4\nUndertake design and adaptation\n\nThe 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.\n\nImplementation teams commissioning the design and adaptation are not expected to know how to programme software themselves but understanding the processes that technology partners go through to build a system is important. The effort needed is otherwise often significantly underestimated, leading to mismatched expectations by",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-021",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Validate functional requirements",
      "pageStart": 53,
      "pageEnd": 53,
      "target": "../sections/sec-021-42-validate-functional-requirements.md",
      "narrative": null,
      "content": "As the steps outlined in Chapter 1 to understand users and the needs for a system to digitize primary \nhealth care have shown, creating a PCPOSS is a highly iterative process. Once a team, including \ntechnology partners, is in place and an initial set of requirements has been identified, these \nrequirements should be validated with all the key stakeholders.\nAdditional workshops with key stakeholders are necessary \nto validate and confirm requirements before the technology \npartner can start the build. This can be done in an agile, \nincremental way that breaks down the build of the solution int",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-022",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Develop and test prototype design",
      "pageStart": 53,
      "pageEnd": 56,
      "target": "../sections/sec-022-43-develop-and-test-prototype-design.md",
      "narrative": null,
      "content": "Creating mock-ups of a user interface (UI) and prototyping of the product helps to evaluate the \nlayout, flow and usability of the intended digital application prior to coding and development. These \ndesign mock-ups and prototypes will prove useful when the engineers start to build the system, as \nthey will help the engineers to visualize how the functional requirements being built into the system \nwill be used.\nThere are various types of prototypes and mock-up UIs, as \nwell as multiple methods to create them, but all are intended \nto elicit more detailed feedback from end-users. Some \napplica",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-vfig-p054",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 54,
      "pageEnd": 54,
      "target": "../figures/vfig-p054.png",
      "narrative": "draft",
      "content": "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).",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-023",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Design system architecture",
      "pageStart": 56,
      "pageEnd": 60,
      "target": "../sections/sec-023-44-design-system-architecture.md",
      "narrative": null,
      "content": "A system architecture is a conceptual model that depicts how the PCPOSS will be structured and how \nit functions and includes all the software and hardware components that comprise the system. \nFurther, the system architecture of a PCPOSS would need \nto function within an Enterprise Architecture (EA), which \ndescribes how the PCPOSS interacts with other parts of the \ndigital health ecosystem and is used to drive interoperability \nrequirements. Such architectures can be visualized with a \nvariety of tools, similar to those mentioned for workflow \nmapping, including but not limited to diagrams.n",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-024",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Build and quality assurance",
      "pageStart": 60,
      "pageEnd": 61,
      "target": "../sections/sec-024-45-build-and-quality-assurance.md",
      "narrative": null,
      "content": "During this step, the technology partner will take the time to build the PCPOSS. They will need to \nspend time coding and ensuring that their code results in the required functionality and design.\nIt is easy to underestimate the time and costs needed to \nbuild a quality PCPOSS, but it is important to anticipate them \nproperly so that the system is built successfully and meets \nusers’ needs. The nature of this step is highly dependent on the \nlevel of digital maturity of the software solution chosen, the \namount of customization required and the skills and capacity \nof the technology partner. I",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-025",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Develop and conduct training",
      "pageStart": 62,
      "pageEnd": 64,
      "target": "../sections/sec-025-51-develop-and-conduct-training.md",
      "narrative": null,
      "content": "CHAPTER 5\nConduct training, testing and roll-out\n\nAfter 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 quality assurance tests need to be conducted prior to deployment.\n\n| Component | Details |\n| --- | --- |\n| **Who should be involved?** | • Implementing teams should be responsible for",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-026",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Test user acceptance and deployment readiness",
      "pageStart": 64,
      "pageEnd": 65,
      "target": "../sections/sec-026-52-test-user-acceptance-and-deployment-readiness.md",
      "narrative": null,
      "content": "With a beta version of the PCPOSS available, a series of user acceptance tests needs to take place \nprior to deployment. User acceptance testing (UAT) should be conducted by the core project team \nwith a small group of trusted advisers and end-users. The small number of UAT testers, including \nsome end-users, should initially be trained on how to use the beta version of the software, then \ntasked with using the PCPOSS in existing workflows, and finally invited to provide feedback. \nThese UAT testers could report back on any bugs, design \nflaws and features they liked and disliked. Feedback fro",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-027",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Deploy the system",
      "pageStart": 65,
      "pageEnd": 65,
      "target": "../sections/sec-027-53-deploy-the-system.md",
      "narrative": null,
      "content": "Deployment of the system often requires strong strategic thinking by the technology partner, as \npoorly deployed systems can make or break an entire project. \nOnce all the required testing has been completed, including \nUAT, the system can be deployed in a production environment. \nA production environment refers to the normal operational \nenvironment where a system is deployed and will be in full use \n(98). This translates to health workers being able to input the \nservices they have provided and that information either being \nsaved onto the device and/or uploaded to the server when \nthere is",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-028",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Manage feedback and system maintenance",
      "pageStart": 65,
      "pageEnd": 65,
      "target": "../sections/sec-028-54-manage-feedback-and-system-maintenance.md",
      "narrative": null,
      "content": "Feedback management, training, software updates and \nhardware maintenance will all be needed continually \nduring the roll-out. The implementation team should have a \nstandard operating procedure for managing all this \nfeedback. For example, if there is a bug that occurs during \nthe pilot and roll-out: \n•\t How will the team receive feedback?\n•\t Is there a call centre or other central feedback \nmechanism (e.g. email, secure chat, text messaging) \nthat needs to be set up?\n•\t Who will be addressing that feedback and making \nupdates to the system?\n•\t What are the procedural steps for addressing and",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-029",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Determine readiness for scaling up",
      "pageStart": 66,
      "pageEnd": 68,
      "target": "../sections/sec-029-61-determine-readiness-for-scaling-up.md",
      "narrative": null,
      "content": "CHAPTER 6\nPrepare for scale-up\n\nTo 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.\n\nThis chapter aims to provide an overview of the key steps to begin the possible phase-out of paper and/or legacy systems. A multitude of factors need to be considered. Every country and context will be moving at a different pace due to",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-img-p068-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 68,
      "pageEnd": 68,
      "target": "../images/img-p068-1.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-030",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Plan for phase-out of legacy system(s)",
      "pageStart": 68,
      "pageEnd": 71,
      "target": "../sections/sec-030-62-plan-for-phase-out-of-legacy-systems.md",
      "narrative": null,
      "content": "When moving from scale-up to integration and sustainability (see Monitoring and evaluating digital \nhealth interventions [99]), answer the following question: What targets, indicators or objectives must \nthe PCPOSS meet for the public health authority to feel comfortable phasing out paper and/or legacy \nsystems?\nClear, agreed upon objectives should be set to allow for the \nphase-out of legacy systems. When these objectives are met, \nthey would provide an indication that the legacy system(s) \ncan be phased-out. The objectives for the PCPOSS should be \nspecific, measurable, attainable, relevant",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-img-p071-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 71,
      "pageEnd": 71,
      "target": "../images/img-p071-1.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-031",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Monitor and evaluate progress on objectives",
      "pageStart": 71,
      "pageEnd": 71,
      "target": "../sections/sec-031-63-monitor-and-evaluate-progress-on-objectives.md",
      "narrative": null,
      "content": "With clear objectives and indicators to measure progress \ntowards them, it is crucial that the PCPOSS has a clear and \nrobust monitoring and evaluation plan and methodology. \nWHO offers a practical guide, Monitoring and evaluating \ndigital health interventions (99), with detailed stepwise \nguidance that is beyond the scope of this handbook. The \nguidance helps with improving the quality and value of \nmonitoring and evaluation efforts in the context of digital \nhealth interventions (also commonly referred to as mHealth \nor eHealth interventions). It is intended \nfor implementers and researchers",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-032",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Phase-out of legacy system(s)",
      "pageStart": 71,
      "pageEnd": 71,
      "target": "../sections/sec-032-64-phase-out-of-legacy-systems.md",
      "narrative": null,
      "content": "Strategically, it is advised to not wait until the entire country \nis ready to phase out paper systems and/or legacy systems \nand instead phase out those systems in a staged, or step-wise, \nmanner. For example, if one region or province is ready to \nphase out paper systems completely, but other provinces are \nstill in the process of adopting PCPOSSs, it might be better to \nbegin the phase out of the paper system in the province that \nis ready. This will allow a phased adoption of the PCPOSS \nand phase-out of paper systems, which is beneficial when \nresources are limited. This will set a manage",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-033",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Adopt change management practices",
      "pageStart": 71,
      "pageEnd": 72,
      "target": "../sections/sec-033-65-adopt-change-management-practices.md",
      "narrative": null,
      "content": "As the PCPOSS is adopted and increasingly integrated into \nroutine use, the phasing out of paper systems entirely \nwill require behaviour change, not just at the level of \nhealth workers, but within the public health authority \nitself. Successful change management is a key factor in \nimplementing any new process or system, but it is especially \nimportant for implementing new digital systems. Switching \nfrom paper to digital systems, or from one system to another, \neven with the ubiquity of technology in the world today, \nremains a big change. \nA clear change management strategy needs to align",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-034",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "References",
      "pageStart": 72,
      "pageEnd": 75,
      "target": "../sections/sec-034-references.md",
      "narrative": null,
      "content": "1.\t\nConsolidated guidelines on person-centred HIV strategic information: strengthening routine data for impact. Geneva: World \nHealth Organization; 2022 (https://iris.who.int/handle/10665/360948). \n2.\t\nWHO guideline: recommendations on digital interventions for health system strengthening. Geneva: World Health Organization; \n2019 (https://apps.who.int/iris/handle/10665/311941).\n3.\t\nClassification of digital interventions, services and applications in health: a shared language to describe the uses of digital \ntechnology for health, second edition. Geneva: World Health Organization; 2023 (https:",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-035",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Principles for digital development",
      "pageStart": 76,
      "pageEnd": 79,
      "target": "../sections/sec-035-principles-for-digital-development.md",
      "narrative": null,
      "content": "ANNEX 1.\nPrinciples for digital development\n\n| Principle | Description |\n| --- | --- |\n| **Understand the existing ecosystem** | Trust starts with a thorough understanding of the dynamic cultural, social, and economic context in which you are operating. |\n| **Share, reuse, and improve** | Build on what works, improve what works, and share so that others can do the same. |\n| **Design with people** | Good design starts and ends with people that will manage, use, and ideally benefit from a given digital initiative. |\n| **Design for inclusion** | Consider the full range of human diversity to maxim",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-036",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Observations worksheet",
      "pageStart": 80,
      "pageEnd": 81,
      "target": "../sections/sec-036-observations-worksheet.md",
      "narrative": null,
      "content": "ANNEX 3.\nObservations worksheet\n\n**The work environment**\nTo be completed once per facility.\n\n| Field | Notes / Questions |\n| --- | --- |\n| **Facility name** | |\n| **General description of services** | • What health services are provided at this facility? |\n| **Catchment population** | • Which populations is this health facility serving |\n| **Number of staff** | • Full time<br>• Part time<br>• Volunteers |\n| **Electricity** | • Does the facility have electricity?<br>• Is it reliable? |\n| **Technology and connectivity** | • Is there network connectivity at the facility?<br>• Do staff use a tabl",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-037",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "User persona worksheet",
      "pageStart": 82,
      "pageEnd": 82,
      "target": "../sections/sec-037-user-persona-worksheet.md",
      "narrative": null,
      "content": "ANNEX 4.\nUser persona worksheet\n\nA 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.\n\n| Section | Prompts |\n| --- | --- |\n| **Persona title (e.g. nurse)** | |\n| **Name, photo and type of persona** | • Name (real or illustrative)<br>• Photo or illustration of persona (helps with visualization and storytelling)<br>• Health worker occupational group |\n| **Demographics** | • Gender<br>• Age<br>• Community of origin<br>• Language(s) used |\n| **Expected roles and responsibilities**",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-038",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "User stories worksheet",
      "pageStart": 83,
      "pageEnd": 83,
      "target": "../sections/sec-038-user-stories-worksheet.md",
      "narrative": null,
      "content": "ANNEX 5.\nUser stories worksheet\n\nUser 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).\n\n| As a… | I want to… | So that… |\n| --- | --- | --- |\n| *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 non-functional requirements)* | *Reason for wanting this requirement/purpose* |\n| Example: As a nurse/midwife | Example: I want to refer health service users with high-risk pregnancies to t",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-039",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Business process matrix guide",
      "pageStart": 84,
      "pageEnd": 84,
      "target": "../sections/sec-039-business-process-matrix-guide.md",
      "narrative": null,
      "content": "ANNEX 6.\nBusiness process matrix guide\n\nThe 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.\n\n| What to note | Description |\n| --- | --- |\n| **Business process number** | This is a running number or letter for each business process, to help with organization and references. |\n| **Process name*",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-040",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Form inventory guide",
      "pageStart": 85,
      "pageEnd": 85,
      "target": "../sections/sec-040-form-inventory-guide.md",
      "narrative": null,
      "content": "ANNEX 7.\nForm inventory guide\n\nThe 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.\n\n| Inventory column | Description of information entered |\n| --- | --- |\n| **Form ID** | If the form or register has an existing identification number, list it here.<br>If there is no numbering system in use, create one that will allow the implementation team t",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-041",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Form data mapping guide",
      "pageStart": 86,
      "pageEnd": 89,
      "target": "../sections/sec-041-form-data-mapping-guide.md",
      "narrative": null,
      "content": "ANNEX 8.\nForm data mapping guide\n\nThe 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 design in subsequent steps (see sections 3.4 and 3.5).\n\n| What to note | Description |\n| --- | --- |\n| **Activity ID** | Include the Activity ID under which that data element is collect",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-042",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Aggregate indicator mapping guide",
      "pageStart": 90,
      "pageEnd": 91,
      "target": "../sections/sec-042-aggregate-indicator-mapping-guide.md",
      "narrative": null,
      "content": "ANNEX 9.\nAggregate indicator mapping guide\n\nA 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.\n\n| What to note | Description |\n| --- | --- |\n| **Indicator ID** | The Indicator ID should be a running number or letter that would facilitate organization and references. |\n| **Indicator name** | Brief name of the indicator. |\n| **Definition** | Provide a narrative description of the indicator to provide additional context. |",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-043",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Template for a decision-support table",
      "pageStart": 92,
      "pageEnd": 93,
      "target": "../sections/sec-043-template-for-a-decision-support-table.md",
      "narrative": null,
      "content": "ANNEX 11.\nTemplate for a decision-support table\n\nThe 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.\n\n| Field | Description |\n| --- | --- |\n| **Decision-support table ID** | The Decision support table ID should correspond to the number in the overview matrix (Annex 10). |\n| **Decision name** | The name of the “decision” describing what algorithm or logic is represented (e.g. pre-eclampsia risk counsellin",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-044",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Scheduling logic table guide",
      "pageStart": 94,
      "pageEnd": 94,
      "target": "../sections/sec-044-scheduling-logic-table-guide.md",
      "narrative": null,
      "content": "ANNEX 12.\nScheduling logic table guide\n\nThis 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 different service schedules can be depicted in various ways. The service schedule for antenatal care, for example, can be found in WHO’s 2021 *Digital adaptation kit for antenatal care: o",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-045",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Prioritization of requirements guide",
      "pageStart": 95,
      "pageEnd": 95,
      "target": "../sections/sec-045-prioritization-of-requirements-guide.md",
      "narrative": null,
      "content": "ANNEX 13.\nPrioritization of requirements guide\n\nWith 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 format. Each requirement should be documented in a separate row with each of the following columns filled out.\n\n| What to note | Description |\n| --- | --- |\n| **Requirement ID** | Th",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/prose-sec-046",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "HL7 FHIR standard components",
      "pageStart": 96,
      "pageEnd": 98,
      "target": "../sections/sec-046-hl7-fhir-standard-components.md",
      "narrative": null,
      "content": "ANNEX 14.\nHL7 FHIR standard components\n\nResources\nA “FHIR Resource” is a modular component that serves as the basic data exchange format in the HL7 FHIR standard. A FHIR \nResource contains the data elements, constraints on those data elements and the data relationships that together make up an \nexchangeable data model, in the context of health data (1).\nEach FHIR Resource also contains links to relevant information in other FHIR Resources. For example, the ANC Observation \nresource in the WHO Antenatal Care Guideline Implementation Guide (2) contains information on the observed body part, how",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-28"
      }
    },
    {
      "id": "library/9789240093362-eng/blocks/figure-img-p098-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 98,
      "pageEnd": 98,
      "target": "../images/img-p098-1.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    }
  ]
}
