{
  "$schema": "folio-library-entry/v1",
  "id": "10665-341997",
  "blocks": [
    {
      "id": "library/10665-341997/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": "recommendations\nA\nindicators\nworkflows\ndata\ndecisions\nscenarios\nrequirements\npersonas\nDigital \nAdaptation Kit  \nfor Family \nPlanning\nOperational requirements for \nimplementing WHO recommendations  \nin digital systems\nSMART GUIDELINES\nDigital \nAdaptation Kit  \nfor Family \nPlanning\nOperational requirements for \nimplementing WHO recommendations  \nin digital systems\nSMART GUIDELINES\nDigital adaptation kit for family planning: operational requirements for implementing WHO recommendations in digital systems\nISBN 978-92-4-002974-3 (electronic version) \nISBN 978-92-4-002975-0 (print version)\n© World H",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "The front matter of WHO's Digital Adaptation Kit for Family Planning (2021), part of the SMART Guidelines series, with cover, ISBN and licence page, citation, table of contents and links to web annexes on data dictionary, decision logic, indicators and requirements.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/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 of many individuals across different organizations. This digital adaptation kit was \ncoordinated by Mario Festin, Mary Lyn Gaffied and Tigest Tamrat of the WHO Department of Sexual and Reproductive Health and Research (SRH); \nGarrett Mehl and Natschja Ratanaprayul of the WHO Department of Digital Health and Innovations (DHI); Brian Taliesin, Jenny Thompson and Rachel \nTurkel from PATH; Sylvia Wong and Jenny Greaney of the United Nations Population Fund (UNFPA); and Leona Rosenblum from John Snow, Inc (JSI).\nThe following ind",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Acknowledges the WHO, PATH, UNFPA and JSI staff who coordinated the family planning digital adaptation kit, lists the many reviewers who gave feedback, and names HRP and USAID-funded partners as funders.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-001",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Abbreviations",
      "pageStart": 7,
      "pageEnd": 10,
      "target": "../sections/sec-001-abbreviations.md",
      "narrative": null,
      "content": "3TC\nlamivudine\nABC\nabacavir\nART\nantiretroviral therapy\nAZT\nzidovudine\nBBT\nbasal body temperature\nBMD\nbone marrow density\nBMI\nbody mass index\nCHC\ncombined hormonal contraceptive\nCIC\ncombined injectable contraceptive\nCIN\ncervical intraepithelial neoplasia\nCOC\ncombined oral contraceptive\nCu-IUD\ncopper-bearing intrauterine device\nCVR\ncombined contraceptive vaginal ring\nD4T\nstavudine\nDAK\ndigital adaptation kit\nDDI\ndidanosine\nDHIS2\nDistrict Health Information Systems (version 2)\nDMN\nDecision Model and Notation\nDMPA\ndepot medroxyprogesterone acetate\nDTDS\ndigital tracking and decision support\nDVT\ndeep",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "A list of abbreviations used in the family planning digital adaptation kit, covering contraceptive methods, antiretroviral drugs, clinical terms and data standards.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-002",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Background",
      "pageStart": 10,
      "pageEnd": 14,
      "target": "../sections/sec-002-background.md",
      "narrative": null,
      "content": "Digital health – defined broadly as the systematic application of information and communications technologies (ICT), computer science and data \nto support informed decision-making by individuals, the health workforce and health systems, to strengthen resilience to disease and improve health \nand wellness (1) – is increasingly being applied as an essential enabler for health service delivery and accountability. Ministries of health (MOHs) have \nrecognized the value of digital health as articulated within the World Health Assembly resolution (2) and the Global strategy on digital health (3). \nLi",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Explains the background to WHO digital adaptation kits, noting that despite investment in digital health, the data and logic in digital tools are often opaque, inconsistent or proprietary and not clearly linked to evidence-based recommendations. It describes the kits as software-neutral, standardised documentation that distils WHO guidance into content for digital tracking and decision-support systems, mapped to standard terminologies such as ICD. It defines digital tracking and decision support and identifies the core WHO family planning guidance documents the kit draws on, such as the medical eligibility criteria for contraceptive use.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/figure-img-p011-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 11,
      "pageEnd": 11,
      "target": "../images/img-p011-1.webp",
      "narrative": "draft",
      "content": "Cover of the publication 'Digital Adaptation Kit for Family Planning: Operational requirements for implementing WHO recommendations in digital systems' (SMART Guidelines), showing stylized dotted figures of a woman and a man on green and purple panels, with the WHO, HRP and JSI logos.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/figure-img-p012-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 12,
      "pageEnd": 12,
      "target": "../images/img-p012-1.webp",
      "narrative": "draft",
      "content": "Cover of the WHO guideline 'Recommendations on digital interventions for health system strengthening', illustrated with people using a computer, a tablet and a mobile phone, and the WHO logo.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/figure-img-p013-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 13,
      "pageEnd": 13,
      "target": "../images/img-p013-1.webp",
      "narrative": "draft",
      "content": "Small cover image of the 'Digital Adaptation Kit for Family Planning', used in Fig. 2 to represent layer L2 (operational: digital adaptation kits) of the SMART Guidelines.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/figure-img-p013-2",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 13,
      "pageEnd": 13,
      "target": "../images/img-p013-2.webp",
      "narrative": "draft",
      "content": "Icon of a computer monitor displaying XML-style code snippets (e.g. code value=\"AGE_GROUP:SEX\") with the FHIR flame logo, representing layer L3 (machine-readable recommendations) in Fig. 2.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/figure-img-p013-3",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 13,
      "pageEnd": 13,
      "target": "../images/img-p013-3.webp",
      "narrative": "draft",
      "content": "Icon of a computer monitor showing a software form and a tablet showing a health-worker symbol, representing layer L4 (reference software) in Fig. 2.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/figure-img-p013-4",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 13,
      "pageEnd": 13,
      "target": "../images/img-p013-4.webp",
      "narrative": "draft",
      "content": "Icon of a computer monitor and a tablet each showing a human head with a circuit-like brain, representing layer L5 (precision health model) in Fig. 2.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/figure-img-p013-5",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 13,
      "pageEnd": 13,
      "target": "../images/img-p013-5.webp",
      "narrative": "draft",
      "content": "Cover of the WHO publication 'Selected practice recommendations for contraceptive use, Third edition 2016', with grey circular pattern and the WHO logo. Used in Fig. 2 to represent layer L1 (narrative guidelines).",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-003",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Objectives",
      "pageStart": 14,
      "pageEnd": 15,
      "target": "../sections/sec-003-objectives.md",
      "narrative": null,
      "content": "This DAK focuses on family planning and aims to provide a common language across various audiences – family planning and other programme \nmanagers, software developers, and implementers of digital systems – to ensure a common understanding of the appropriate health information content \nwithin a defined health programme area, as a mechanism to catalyse the effective use of these digital systems. The key objectives of the DAK are:\n\t»\nto ensure adherence to WHO clinical, public health and data use guidelines, and facilitate consistency of the health content that is used to inform \nthe development",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "States the objectives of the family planning digital adaptation kit: to keep digital tracking and decision-support systems consistent with WHO guidelines, give health and digital teams a shared understanding of content, and supply core data elements and decision logic. It lists the source guidelines, notes that outputs are generic and must be adapted locally, and mentions related kits for antenatal care, HIV and STIs.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-004",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Components of a digital adaptation kit",
      "pageStart": 15,
      "pageEnd": 19,
      "target": "../sections/sec-004-components-of-a-digital-adaptation-kit.md",
      "narrative": null,
      "content": "The DAK comprises eight interlinked components: (1) health interventions and associated recommendations; (2) generic personas; (3) user scenarios; \n(4) business processes and workflows; (5) core data elements; (6) decision-support logic; (7) indicators and performance metrics; and (8) high-level \nfunctional and non-functional requirements. Table 1 provides an overview of each of the contributing components of the DAK, which this document \nelaborates. All information within the adaptation kit represents a generic starting point, which can then be adapted according to the specific context.\nTable",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Describes the eight interlinked components of a digital adaptation kit, from health interventions and recommendations, personas and user scenarios through workflows, core data elements, decision-support logic, indicators and system requirements. A table sets out each component's purpose, outputs and adaptation needs. It also explains the identifier conventions used for data elements, decision tables, indicators and requirements.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/table-001",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 1. Components of a digital adaptation kit",
      "pageStart": 15,
      "pageEnd": 17,
      "target": "../tables/table-1.csv",
      "narrative": "draft",
      "content": "The table lists the eight components of the digital adaptation kit (DAK), from health interventions and recommendations to functional and non-functional requirements. For each component it gives a description, its purpose, the outputs it provides and the adaptation needed for a specific context.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-005",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "How to use this digital adaptation kit",
      "pageStart": 19,
      "pageEnd": 21,
      "target": "../sections/sec-005-how-to-use-this-digital-adaptation-kit.md",
      "narrative": null,
      "content": "Target audience\nThe primary target audience for this DAK is health programme managers within the MOH, who will be working with their digital or health information \nsystems counterparts in determining the health content requirements for a family planning DTDS system. The health programme manager is responsible \nfor overseeing and monitoring the implementation of the clinical practices and policies for the health programme area, in this case family planning. \nOther stakeholders, including software development teams and implementers in the private sector, will can also benefit from the content in",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Identifies ministry of health family planning programme managers as the main audience for the kit, working with digital health and information system counterparts and business analysts. It explains how the kit supports collaboration and adaptation to local contexts and notes that client-facing digital tools will be covered in a forthcoming self-care kit.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-006",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Linkages to the broader digital health ecosystem",
      "pageStart": 21,
      "pageEnd": 24,
      "target": "../sections/sec-006-linkages-to-the-broader-digital-health-ecosystem.md",
      "narrative": null,
      "content": "overview\nLinkages to the broader digital health ecosystem\nDigital adaptation kits within the broader digital \nhealth ecosystem\nFIG. 3\nWHO core \nindicator \nsets\nGlobal \ndigital \nhealth \nindex\nWHO  \ndigital \nhealth atlas\nDigital \nhealth \ninvestment \nreview tool\nHIS stages of  \ncontinuous \nimprovement\n+\t Conduct an inventory of existing or previously used \nsoftware applications, ICT systems and other tools to better \nunderstand the requirements for reuse and interoperability\n+\t Develop a national digital health strategy outlining \noverarching needs, desired activities and outcomes\n+\t Define a vis",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Places digital adaptation kits within the wider digital health ecosystem, with a figure mapping WHO and partner resources, such as the WHO–ITU national eHealth strategy toolkit, TOGAF and Open HIE, to seven phases running from assessing the current state to implementing and scaling. It advises that DAKs be used once a health ministry has a strategic vision for digital systems, and otherwise to consult the eHealth strategy toolkit, the WHO digital interventions guideline and the digital implementation investment guide first.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-007",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Health interventions and recommendations",
      "pageStart": 24,
      "pageEnd": 26,
      "target": "../sections/sec-007-1-health-interventions-and-recommendations.md",
      "narrative": null,
      "content": "personas\nindicators\nworkflows\ndata\ndecisions\nscenarios\nrequirements\nThis DAK focuses on the following health interventions and recommendations related to contraception and family planning.\n1.1 \tInterventions referenced in this DAK are based on the WHO universal health coverage (UHC) list \nof essential interventions\nThe key interventions for contraception and family planning are the following, as defined in the WHO UHC compendium of interventions (15).\n\t»\nScreening, testing and counselling for choosing contraceptive methods\n\t–\nHIV testing services\n\t–\nScreening for pregnancy and medical eligibil",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Lists the contraception and family planning interventions covered by this digital adaptation kit, drawn from the WHO universal health coverage compendium, including screening and counselling, provision and removal of contraceptive methods, and emergency contraception for survivors of sexual violence. It names the WHO guidance the kit reflects, notably the medical eligibility criteria, selected practice recommendations, contraceptive eligibility for women at high risk of HIV and the family planning handbook for providers, plus several other WHO guidelines. It closes by introducing personas as generic depictions of system end-users that need adapting to each setting.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/figure-img-p025-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 25,
      "pageEnd": 25,
      "target": "../images/img-p025-1.webp",
      "narrative": "draft",
      "content": "Cover of the WHO publication 'Selected practice recommendations for contraceptive use, Third edition 2016', with grey circular pattern and the WHO logo.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-008",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Generic personas",
      "pageStart": 26,
      "pageEnd": 31,
      "target": "../sections/sec-008-2-generic-personas.md",
      "narrative": null,
      "content": "In the case of family planning, auxiliary nurse midwives and midwives are the primary personas for the digital tracking and decision-support system. In \nthe health systems surveyed for this DAK, the common combination of service providers was a lay health worker along with a nurse who was also trained \nas a midwife. The key competences of nurse midwives compared with those of lay health workers are defined by WHO (Table 2 ) (20).\nGeneric  \npersonas\nComponent\nrecommendations\nindicators\nworkflows\ndata\ndecisions\nscenarios\nrequirements\npersonas\nTable 2. Descriptions of key generic personas\nOccupat",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Describes the generic personas of the family planning digital adaptation kit, with auxiliary nurse midwives and midwives as the primary users, and a table giving each role's description, alternative names and ISCO code. Reproduces WHO's task-sharing chart showing which cadres of health workers can typically provide each contraceptive method, followed by a table of related personas such as clients, lay and community health workers, pharmacists and physicians. Closes with factors for adapting personas to local settings, including demographics, working environment, actual versus expected roles, challenges and motivations.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/table-002",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 2. Descriptions of key generic personas",
      "pageStart": 27,
      "pageEnd": 27,
      "target": "../tables/table-2.csv",
      "narrative": "draft",
      "content": "The table describes the three key generic personas targeted by the family planning digital adaptation kit (auxiliary nurse midwife, midwife and nurse). For each occupational title it gives a description, other names used for the role and the corresponding ISCO occupation code.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/table-003",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 3. Descriptions of related personas",
      "pageStart": 29,
      "pageEnd": 29,
      "target": "../tables/table-3.csv",
      "narrative": "draft",
      "content": "The table describes personas related to the targeted auxiliary nurse midwife: the client, lay health worker, community health worker, pharmacist and physician. For each it gives a description, other names where relevant and the ISCO occupation code where relevant.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-009",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "User scenarios",
      "pageStart": 31,
      "pageEnd": 34,
      "target": "../sections/sec-009-3-user-scenarios.md",
      "narrative": null,
      "content": "3.1 \tUser scenario for nurse\nKey personas\nNurse: Aisha\nClient: Hope\nHope is a 26-year-old woman who has brought her 6-week-old baby, Mosi, into a primary health care facility for routine immunizations.\nWhile nurse Aisha is providing the immunizations for the child, they begin discussing Hope’s future and desire for more children. As she is looking to space out the next birth by more \nthan a year, Aisha suggests they talk more about family planning.\nHope has not yet been registered in the electronic system. So, Aisha sets her up as a new client, gathers her contact and address information, and",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Presents two user scenarios for family planning services: a nurse who registers and counsels a breastfeeding mother during her baby's immunization visit and starts her on progestogen-only pills, and a 16-year-old who seeks help after a condom slipped. The adolescent scenario shows confidential registration, a HEADSS assessment, emergency contraception and dual protection with combined pills and condoms, with SMS follow-up reminders in both cases. Explains how such scenarios reveal data elements, decision logic, functional requirements and adolescent-specific considerations, illustrated in a table interpreting the adolescent case.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/table-004",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 4. Interpretation of the adolescent user scenario",
      "pageStart": 33,
      "pageEnd": 33,
      "target": "../tables/table-4.csv",
      "narrative": "draft",
      "content": "The table interprets the adolescent user scenario for system design. Its columns list the data elements to be collected, the decision logic to be embedded, the functional and non-functional requirements, and the adolescent-specific considerations to be triggered when the client’s age is 19 years or younger.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-010",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Business processes and workflows",
      "pageStart": 34,
      "pageEnd": 59,
      "target": "../sections/sec-010-4-business-processes-and-workflows.md",
      "narrative": null,
      "content": "personas\nindicators\ndata\ndecisions\nscenarios\nrequirements\nworkflows\nA business process, or process, is a set of related activities or tasks performed together to achieve the objectives of the health programme area, such \nas registration, counselling and referrals (1,16). Workflows are a visual representation of the progression of activities (tasks, events and interactions) \nthat are performed within the business process (16). The workflow provides a story for the business process being diagrammed and is used to enhance \ncommunication and collaboration among users, stakeholders and engineers.\nT",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Defines business processes and workflows for the family planning digital adaptation kit and summarizes five key processes: registration, family planning counselling, service provision, referral, and aggregate reporting and data use. Lists processes left out because they depend heavily on context, such as billing, dispensing, configuration and follow-up, and explains the standard business process notation symbols used in the diagrams. The workflows are described as roughly 80% generic, with the remainder to be completed through human-centred design and validation with the targeted personas. The section ends by introducing the core data elements component, which sets out the minimum data needed for service delivery, decision support and indicators, with a fuller data dictionary in Web Annex A.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/table-005",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 5. Overview of key family planning module business processes",
      "pageStart": 35,
      "pageEnd": 36,
      "target": "../tables/table-5.csv",
      "narrative": "draft",
      "content": "The table gives an overview of the five key business processes of the family planning module (A–E: registration, family planning counselling, service provision, referral, and aggregate reporting and data use). For each process it lists the process ID, the personas involved, the objectives and the task set, starting from a defined starting point.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/table-006",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 6. Business process symbols used in workflows",
      "pageStart": 36,
      "pageEnd": 37,
      "target": "../tables/table-6.csv",
      "narrative": "draft",
      "content": "The table explains the standard business process notation symbols used in the workflow diagrams, from pools and swim lanes to events, activities, flows, gateways, links and ad hoc subprocesses. For each symbol it gives its name and a description of how it is used.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/figure-vfig-p038",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 38,
      "pageEnd": 38,
      "target": "../figures/vfig-p038.webp",
      "narrative": "draft",
      "content": "Fig. 5, a swimlane diagram of key family planning processes across three lanes: Health facility, Pharmacy and Health facility management. From Start, the flow runs through A. Registration and B. FP counselling to a 'Referral needed?' decision: No leads to C. FP service provision, Yes leads to D. Referral; both then pass to Billing and Dispensing before End. Configuration, Follow-up and Aggregate reporting sit in the management lane.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/figure-vfig-p039",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 39,
      "pageEnd": 39,
      "target": "../figures/vfig-p039.webp",
      "narrative": "draft",
      "content": "Fig. 6, a swimlane workflow of the registration business process with Client and Clerk lanes in a health facility. The client arrives; the clerk gathers client details, searches for the client and checks 'Match found?': Yes leads to a 'Validate client details' subprocess (review socio-demographic data, update if needed), No leads to 'Create client record'; both end with 'Check in client' and hand off to B. Counselling. Source: adapted from PATH.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/figure-vfig-p053",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 53,
      "pageEnd": 53,
      "target": "../figures/vfig-p053.webp",
      "narrative": "draft",
      "content": "Fig. 10, a swimlane workflow of the referral business process with lanes for the client and healthcare provider at the health facility and the health-care provider at the referral health facility. After counselling, an 'Emergency referral?' decision leads either to an emergency subprocess (stabilize client and give pre-referral treatment, check if stable enough to transport, organize transport) or to identifying and contacting a referral facility; once the referral facility confirms it can accommodate, the provider gives information, discusses questions and a backup method, and the client goes to the referral facility, which receives the client for C. Service provision.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/figure-vfig-p056",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 56,
      "pageEnd": 56,
      "target": "../figures/vfig-p056.webp",
      "narrative": "draft",
      "content": "Fig. 11, a swimlane workflow of the aggregate reporting business process with lanes for facility staff, facility in charge and district health officer/staff. Facility staff check data quality, correct fixable issues, generate and check aggregate reports; if in-charge review is needed, the facility in charge reviews and either provides feedback (looping back to data checks) or submits data electronically. The district reviews submitted data and either ends the process or provides feedback to the facility.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-011",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Core data elements",
      "pageStart": 59,
      "pageEnd": 66,
      "target": "../sections/sec-011-5-core-data-elements.md",
      "narrative": null,
      "content": "Table 7 provides a simplified list of core data elements and is merely a snapshot of the comprehensive data dictionary found in Web Annex A. As with \nthe workflows, we view this data dictionary as 80% generic, with the expectation that the other 20% will be supplemented and modified through country \nadaptation.\nCore data \nelements\nComponent\nrecommendations\npersonas\nindicators\nworkflows\ndecisions\nscenarios\nrequirements\ndata\nTable 7. Workflow core data elements for identified business processes\nActivity ID.  \nActivity name\nData element \nID\nData element name\nDescription and definition\nBusiness pr",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Presents a simplified table of core data elements for the family planning digital adaptation kit, a snapshot of the full data dictionary in Web Annex A that is considered about 80% generic and open to country adaptation. The table is organized by business process and activity, listing identifiers, names and definitions for items such as visit date, unique identifier, date of birth, marital status, contact details and communication preferences at registration, and reason for visit and pregnancy intention during counselling. Many activities are marked as recording no new data. The block ends with facility-level contextual elements, including administrative areas, catchment population, available laboratory tests and guidance on how pregnancy test sensitivity affects workflow, before introducing the decision-support logic component.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/table-007",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 7. Workflow core data elements for identified business processes",
      "pageStart": 60,
      "pageEnd": 64,
      "target": "../tables/table-7.csv",
      "narrative": "draft",
      "content": "The table lists the core data elements for each activity in the family planning business processes (registration, counselling, service provision and referral). For each activity it gives the data element IDs, names and descriptions, or notes that no data are recorded during that activity.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/table-008",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 8. Calculated data elements",
      "pageStart": 64,
      "pageEnd": 64,
      "target": "../tables/table-8.csv",
      "narrative": "draft",
      "content": "The table lists derived data elements that are calculated from core data elements: body mass index, postpartum status and recent miscarriage or abortion. For each it names the core data elements used as variables and gives the calculation formula.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/table-009",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 9. Characteristics for local customization and configuration",
      "pageStart": 65,
      "pageEnd": 65,
      "target": "../tables/table-9.csv",
      "narrative": "draft",
      "content": "The table lists points of customization and configuration that each implementation should review against national guidelines and local context, such as unique IDs, services and methods provided, facility details, administrative areas, available lab tests and pregnancy test sensitivity. Each point is paired with a description of what to consider.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-012",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Decision-support logic",
      "pageStart": 66,
      "pageEnd": 73,
      "target": "../sections/sec-012-6-decision-support-logic.md",
      "narrative": null,
      "content": "Table 10 provides an overview of the decision-support tables and algorithms for the different family planning module business processes. The structure \nof the decision-support tables is based on an adaptation of the Decision Model and Notation (DMN), an industry standard for modelling and executing \ndecision logic (27). These decision-support tables detail the business rules, data inputs and outputs to support family planning module business \nprocesses. \nDecision-\nsupport logic\nComponent\nrecommendations\npersonas\nindicators\nworkflows\ndata\nscenarios\nrequirements\ndecisions\nTable 10. Overview of d",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Gives an overview of the decision-support tables and algorithms for the family planning module, structured on an adaptation of the Decision Model and Notation standard. The tables cover reason for visit, HEADSS, STI and intimate partner violence assessments, method concerns and client preferences, and medical eligibility criteria for each contraceptive method, each linked to its WHO source guidance. A further list sets out scheduling logic for follow-up visits by method, from implants and injectables to pills, vaginal rings and sterilization.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/table-010",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 10. Overview of decision-support tables for family planning module",
      "pageStart": 67,
      "pageEnd": 69,
      "target": "../tables/table-10.csv",
      "narrative": "draft",
      "content": "The table gives an overview of the decision-support tables for the family planning module. For each workflow activity it lists the decision-support table ID, a description of the table (such as reason for visit, risk assessments and medical eligibility criteria for each method) and the WHO reference or source it is based on.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/table-011",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 11. Components of the decision-support tables",
      "pageStart": 70,
      "pageEnd": 70,
      "target": "../tables/table-11.csv",
      "narrative": "draft",
      "content": "The table explains the components of the decision-support tables: the decision ID, business rule and trigger, and the inputs, output, action and annotations columns. It defines each component and how multiple inputs on the same row (AND) or on different rows (OR) are read.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/table-012",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 12. Example decision-support logic table for medical eligibility for copper-bearing intrauterine devices (Cu-IUDs)",
      "pageStart": 71,
      "pageEnd": 71,
      "target": "../tables/table-12.csv",
      "narrative": "draft",
      "content": "The table is an example decision-support logic table for medical eligibility for copper-bearing intrauterine devices, giving its decision ID, business rule and trigger. Each row combines input conditions (method requested, health condition, method at intake) with the resulting medical eligibility category and eligibility output, the action for the health worker, an annotation and the references.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/table-013",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 13. Overview of scheduling logic",
      "pageStart": 72,
      "pageEnd": 72,
      "target": "../tables/table-13.csv",
      "narrative": "draft",
      "content": "The table gives an overview of the scheduling logic for follow-up of family planning clients. For each scheduling logic ID it describes the follow-up or removal visit for a given contraceptive method and the WHO reference or source.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-013",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Indicators and performance metrics",
      "pageStart": 73,
      "pageEnd": 75,
      "target": "../sections/sec-013-7-indicators-and-performance-metrics.md",
      "narrative": null,
      "content": "This section details indicators and performance metrics that would be aggregated from core data elements identified in Component 5. The list in  \nTable 14 is a minimum set of indicators that can be aggregated for decision-making, performance metrics, and subnational and national reporting \nbased on data collected from individual-level routine health systems. These indicators may be aggregated automatically from the digital tracking tool to \npopulate a digital HMIS, such as DHIS2. This table is detailed in Web Annex C. \nTable 14. Indicators and performance metrics\nIndicator ID\nIndicator name\nDe",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Sets out a minimum set of indicators and performance metrics for family planning that can be aggregated from the core data elements and fed automatically into a digital health management information system such as DHIS2. For each indicator, the table gives a definition, numerator, denominator, disaggregations such as age, method and service site, and source references, with full details in Web Annex C. The indicators include new and continuing users of modern contraception, number of visits, method switching and discontinuation, receipt of the chosen method, and post-abortion and postpartum contraception.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/table-014",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 14. Indicators and performance metrics",
      "pageStart": 73,
      "pageEnd": 74,
      "target": "../tables/table-14.csv",
      "narrative": "draft",
      "content": "The table lists the minimum set of family planning indicators and performance metrics that can be aggregated from routine digital data, such as new and continuing users, method switching and discontinuation, and post-abortion and postpartum contraception. For each indicator it gives the ID, name, definition, numerator and denominator descriptions, disaggregations and references.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-014",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "High-level functional and non-functional requirements",
      "pageStart": 75,
      "pageEnd": 81,
      "target": "../sections/sec-014-8-high-level-functional-and-non-functional-requi.md",
      "narrative": null,
      "content": "personas\nworkflows\ndata\ndecisions\nscenarios\nindicators\nrequirements\nThis section provides an overview of illustrative functional and non-functional requirements that may be considered to kick-start the process of \ndesigning or adapting the digital tracking and decision-support system. Functional requirements describe the capabilities the system must have in order \nto meet the end-users’ needs and achieve tasks within the business process. Non-functional requirements provide the general attributes and features of \nthe digital system to ensure usability and overcome technical and physical constr",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Provides illustrative functional and non-functional requirements to start designing or adapting a digital tracking and decision-support system for family planning. Functional requirements are written as user stories stating the role, what is wanted and why, starting with registration needs such as urgent-case bypass, client search with at least two identifiers, duplicate avoidance and mandatory fields, with the complete set in Web Annex D. Non-functional requirements describe general system qualities, including multiple languages, usability on small screens, reliability, central configuration of business rules, and interoperability through mediators and APIs. The lists are described as not exhaustive and meant to be adapted to context and user needs, ending with synchronization across facilities even when connectivity is intermittent.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/table-015",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 15. Functional requirementsᵃ",
      "pageStart": 75,
      "pageEnd": 78,
      "target": "../tables/table-15.csv",
      "narrative": "draft",
      "content": "The table lists key functional requirements for the registration, counselling and service provision business processes, written as user stories. For each requirement ID it gives the activity, the user (“As a…”), what they want the system to do (“I want…”) and why (“So that…”).",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/table-016",
      "types": [
        "folio-assistant-core:Table",
        "doco:Table"
      ],
      "kind": "table",
      "title": "Table 16. Non-functional requirements",
      "pageStart": 78,
      "pageEnd": 80,
      "target": "../tables/table-16.csv",
      "narrative": "draft",
      "content": "The table lists the non-functional requirements of the digital system, grouped by category such as security (confidentiality, authentication, audit trail and logs, user management) and system requirements (general, scalability, usability, configuration, interoperability, hardware and connectivity). Each row gives a requirement ID, its category and the requirement.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-015",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Glossary",
      "pageStart": 81,
      "pageEnd": 84,
      "target": "../sections/sec-015-glossary.md",
      "narrative": null,
      "content": "Note: Terms in definitions also defined in this glossary are shown in italics.\nBusiness process\nA set of related activities or tasks performed together to achieve the objectives of the health programme area, such as \nregistration, counselling, referrals (1,16).\nData dictionary\nA centralized repository of information about the data elements that contains their definition, relationships, origin, usage, \nand type of data. For this digital adaptation kit, the data dictionary is provided as a spreadsheet in Web Annex A.\nData element\nA unit of data that has specific and precise meaning.\nDecision-sup",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "The glossary of the family planning digital adaptation kit defines its key terms, among them business process, data dictionary, data element, decision-support logic and tables, digital health, digital tracking, and functional and non-functional requirements. It also explains health information systems, interoperability, personas, standards, tasks, terminologies and workflows, noting which terms are themselves defined in the glossary.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/figure-img-p084-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 84,
      "pageEnd": 84,
      "target": "../images/img-p084-1.webp",
      "narrative": "draft",
      "content": "Persona profile poster for 'Jane, Community Health Worker (CHW)' with photos, 'My Tasks' (80% of time in the community checking in with families and counselling; 20% on administrative duties), 'My Workload', a 'My Typical Day' timeline from 8am to 7pm and a quote: 'Tools are never enough. The regimen changes daily and needs to be continually updated.' The bottom row lists barriers to providing reproductive health services: client beliefs, tracking clients, incentive and workload.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/figure-img-p084-2",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 84,
      "pageEnd": 84,
      "target": "../images/img-p084-2.webp",
      "narrative": "draft",
      "content": "Persona profile poster for 'Roselyn, Nurse-Midwife' with photos, 'My Tasks' (75% of time on maternal and child health with comprehensive obstetric care; 25% on administrative duties), 'My Workplace' (a sub-county hospital), a 'My Typical Day' timeline from 8am to 4pm and the same quote about tools. The bottom row lists barriers to providing reproductive health services: paperwork, unknown demand, high turnover and stock outs.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-016",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Examples of detailed personas",
      "pageStart": 84,
      "pageEnd": 86,
      "target": "../sections/sec-016-annex-1-examples-of-detailed-personas.md",
      "narrative": null,
      "content": "“It’s essential to  \nbe informed to \nkeep trust from  \nmy community.”\nJamilla\nGrace\nannexes\nAnnex 2. Additional user scenario\nUser scenario for community health worker\nKey personas\nCommunity health worker: Jane\nClient: Safia\nSafia is a 20-year-old woman who has recently given birth and has a 3-week-old baby, Said. Her community health worker, Jane, comes to her household (one of 25 or so that Jane \nmonitors) every other day to check up on her and the newborn baby.\nAfter Jane has completed her questions and counselling regarding postnatal care, they began discussing Safia’s future and desire fo",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Annex 2 of the family planning digital adaptation kit gives an additional user scenario in which a community health worker visits a young mother three weeks after birth and uses her app to counsel her on spacing the next pregnancy. Because the client's blood pressure is slightly high, the worker advises against injectables, the client chooses progestogen-only pills, and the worker issues a referral and later follows up, illustrating the counselling and referral business processes.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-017",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Guidance for adding data elements to or amending existing data elements in the data",
      "pageStart": 86,
      "pageEnd": 89,
      "target": "../sections/sec-017-annex-3-guidance-for-adding-data-elements-to-or.md",
      "narrative": null,
      "content": "dictionary\nWhen adapting the data dictionary, data elements may need to be modified or added as a result of the structure of existing paper registers or local \nreporting requirements. If starting from paper-based registers and forms, you can find additional guidance in the Handbook for digitizing primary health \ncare (17), and below is an overview of the data mapping to provide a template for standardizing the data dictionary. When amending the wording of \ndata elements, it is important to ensure that the standard terminology codes still reflect the data element as originally intended.\nWhat to",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Gives guidance for adding or amending data elements when adapting the data dictionary of the family planning digital adaptation kit, for example to match existing paper registers or local reporting needs, while keeping standard terminology codes accurate. A table explains what to record for each element, including activity and form identifiers, labels, names, definitions, data types aligned with FHIR, input options, calculations, validation, editability and whether the field is required. Further columns cover the reason data are required, skip logic, links to aggregate indicators, notes and mappings to concept dictionaries such as ICD-11 or SNOMED.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-018",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Guidance for each method",
      "pageStart": 89,
      "pageEnd": 141,
      "target": "../sections/sec-018-annex-4-guidance-for-each-method.md",
      "narrative": null,
      "content": "This annex is intended to provide additional information that can be used for developing further decision-support logic and counselling aids. This \ninformation is extracted from the Family planning global handbook for providers (2018) (14).\nCopper-bearing intrauterine device (Cu-IUD)\nWhat is it?\n\t» The Cu-IUD is a small, flexible plastic frame with copper sleeves or wire around it. A specifically trained health-care provider inserts it into a woman’s uterus \nthrough her vagina and cervix.\n\t» Almost all types of IUDs have one or two strings, or threads, tied to them. The strings hang through th",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "An annex to the family planning digital adaptation kit gives method-by-method information, drawn from the 2018 Family planning global handbook for providers, to support further decision-support logic and counselling aids. For each contraceptive, starting with the copper-bearing and levonorgestrel-releasing intrauterine devices, it sets out what the method is, how effective it is, who can use it and how. It also covers side-effects, known health benefits and risks, how to advise on side-effects, clinical judgement in special cases and help for continuing users. The section ends with withdrawal, described as one of the least effective methods as commonly used, with no medical restrictions and no protection against sexually transmitted infections.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/prose-sec-019",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "References",
      "pageStart": 141,
      "pageEnd": 144,
      "target": "../sections/sec-019-references.md",
      "narrative": null,
      "content": "1.\t\nDigital implementation investment guide (DIIG): integrating digital interventions into \nhealth programmes. Geneva: World Health Organization; 2020 (https://www.who.\nint/publications/i/item/who-digital-implementation-investment-guide, accessed 18 \nSeptember 2020).\n2.\t\nResolution WHA71.7: Digital health. In: Seventy-first World Health Assembly, 26 May \n2018 (https://apps.who.int/gb/ebwha/pdf_files/WHA71/A71_R7-en.pdf, accessed \n16 December 2020).\n3.\t\nDraft global strategy on digital health 2020–2025. Geneva: World Health \nOrganization; undated (https://www.who.int/docs/default-source/documen",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "The reference list of the family planning digital adaptation kit.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-11-11"
      }
    },
    {
      "id": "library/10665-341997/blocks/figure-img-p144-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 144,
      "pageEnd": 144,
      "target": "../images/img-p144-1.webp",
      "narrative": "draft",
      "content": "ISBN barcode for 9789240029743.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    }
  ]
}
