Document kinds
A document kind is a named structure of sections that a document authored with a harness follows: fixed (exactly these sections) or semi-fixed (these required, others allowed). Every kind and section names its sources.
Digital Adaptation Kit (DAK) dak
The L2 layer of a WHO SMART Guideline: the ten components that make a guideline's recommendations operational, ahead of the L3 FHIR IG that implements them. Fixed: a DAK has exactly these components, in this order.
fixed structure · 10 section(s) · declared by smart-base in smart-base/document-kinds/dak.json · generated by smart-base/scripts/gen-document-kinds.ts
| # | Section | What it holds | Source | |
|---|---|---|---|---|
| 1 | Health Interventions & Recommendationshealth-interventions-and-recommendations | required | Relevant health interventions and recommendations from the WHO guideline and guidance. To inform DAK scope. | the kind's sources |
| 2 | Generic Personasgeneric-personas | required | Roles, responsibilities, and essential interventions performed by targeted personas. Example for human centered design. | the kind's sources |
| 3 | User Scenariosuser-scenarios | required | Brief narrative description of how the targeted personas may engage with the digital system. Example for human centered design. | the kind's sources |
| 4 | Business Processes & Workflowsgeneric-business-processes-and-workflows | required | Generic workflows representing clinical and non-clinical processes. To inform when data is collected and used & required features. | the kind's sources |
| 5 | Core Data Elementscore-data-elements | required | Data elements, used for clinical decision-making, indicators, and other data needs. To inform data collection forms and L3 interoperability requirements. | the kind's sources |
| 6 | Decision Support Logicdecision-support-logic | required | Decision tables representing counselling and treatment algorithms, and any other logic used to determine workflow paths or clinical actions. | the kind's sources |
| 7 | Scheduling Logicscheduling-logic | required | Decision tables representing scheduling logic according to care plans. Previously combined with decision support logic. Not yet a field of its own in WHO's DAK logical model. | the kind's sources |
| 8 | Indicators & Monitoringprogramme-indicators | required | Indicators for reporting & monitoring with numerator, denominator of data elements. Linking person centered data to aggregate. | the kind's sources |
| 9 | Functional & Non-functional Requirementsfunctional-and-non-functional-requirements | required | A non-exhaustive list of key functions and non-functional requirements for a digital tracking and decision support system. To inform system features. | the kind's sources |
| 10 | Test Scenariostest-scenarios | required | Test data and scenarios to check a system against the other nine components. A test harness to run them. | the kind's sources |
Sources: https://www.who.int/publications/i/item/9789240099456 — WHO DAK guidance; https://www.who.int/publications/i/item/9789240085138 — WHO DAK guidance; https://github.com/litlfred/folio-assistant/issues/1614 — owner ruling 2026-09-30: ten components
How each subject realises it
Computed from each artefact's FHIR resource type (owner, 2026-10-01): ActorDefinition → personas; Requirements → requirements; a StructureDefinition the IG files under 'Structures: Logical Models' → core data elements; PlanDefinition and Library → decision-support logic; Measure → indicators. Anything else is listed as unplaced.
| Section | smart-base | smart-immunizations | smart-trust |
|---|---|---|---|
| Health Interventions & Recommendations | — | — | — |
| Generic Personas | 22
| — | 5
|
| User Scenarios | — | — | — |
| Business Processes & Workflows | — | — | — |
| Core Data Elements | 25
| 10
| 5
|
| Decision Support Logic | — | 417
| — |
| Scheduling Logic | — | — | — |
| Indicators & Monitoring | — | 41
| — |
| Functional & Non-functional Requirements | 41
| — | 29
|
| Test Scenarios | — | — | — |
| Unplaced | Basic 63, StructureDefinition 31, ValueSet 24, CodeSystem 12, ConceptMap 4, ActivityDefinition 1, ImplementationGuide 1, Questionnaire 1 | ValueSet 192, QuestionnaireResponse 33, StructureMap 16, StructureDefinition 13, Questionnaire 10, CodeSystem 6, ActivityDefinition 3, ConceptMap 3, Patient 2, ImplementationGuide 1, RelatedPerson 1 | Endpoint 456, Organization 152, CodeSystem 15, ValueSet 14, ConceptMap 1, ImplementationGuide 1 |
| Artefacts classified | 225 | 748 | 678 |
Digital Transformation Handbook (DTH) dth
A WHO guidance publication on digitalising one area of a health system — an L1 publication whose body is a planning method rather than recommendations. It sits within the DIIG process and should use the DPI-H Reference Architecture (owner, 2026-10-01). Its domain sections map onto smart-kg L2 (DAK) classes: a DTH states for a health-system area what a DAK states for a guideline. Structure read from the three DTHs ingested in smart-base/library; a section is required only where all three have it. The Reference Architecture for DPI-H calls itself "A Digital Transformation Handbook for DPI-H" and is cited here as the architecture the others should reference.
semi-fixed structure · 22 section(s) · extends l1 · declared by smart-base in smart-base/document-kinds/dth.json
| # | Section | What it holds | Source | |
|---|---|---|---|---|
| 1 | Audience and how to use this handbookaudience-and-how-to-use | required | Target users/roles per chapter and the stepwise reading path through the handbook. computed from: library | smart-base/library/9789240093362-eng, 2. How to use this handbook > 2.2 Targeted users, p.11 (pdf 23) — this handbook is written for those who will fill the business analyst role on the teamsmart-base/library/9789240101197-eng, Introduction > Who this handbook is for (Table 1), p.8 (pdf 18) — This handbook is for countries, organizations and teams that want to plan and implement digital transformation of the public health supply chain.smart-base/library/9789240116191-eng, Introduction > How to use this handbook, p.8 (pdf 17) — This handbook provides a stepwise approach to implementing standardized NPC and product master data management processes.smart-base/library/who-dpi-h-reference-architecture-draft-v1, 1.1.4 Who can benefit from this guidance, pdf p.23 — Enterprise Architects and Technical Teams: This reference architecture provides TOGAF-based methodology, formal architecture patterns, and systematic requirements frameworks |
| 2 | Position in the DIIG process and SMART Guidelines layersdiig-and-smart-alignment | required | Which phase of the DIIG's "planning and implementing a digital health enterprise" process the handbook supports, and its alignment to the SMART Guidelines layers. The seven phases have ONE source, DIIG §1.1 Fig. 1.1.1 (owner, 2026-10-03, #1984: "use one DIIG seven phase figure as source"); a DTH cites that figure for them, and the copies the handbooks print (PHC Fig. 6, SC Fig 5, PC Fig. 4) are reproductions of it, not further sources. The primary health care DTH places itself in Phase 5, determining health content requirements; the Reference Architecture's Figure 1, which adapts the DIIG figure, places the supply chain and product catalogue handbooks in Phase 7, and the Reference Architecture itself across Phases 1-4. Its SVG rendering, drawn from the DIIG PDF's own vector layer with its provenance inside the file, is smart-base/library/9789240010567-eng/figures/vfig-p017.svg (bean 70zt); the reproductions are listed on smart-base/findings/dth-terms.md. computed from: library | smart-base/library/9789240010567-eng, §1.1 The Guide's role in planning and implementing a digital health enterprise, Fig. 1.1.1, PDF pp.16-17; sections/page-016.md — The process of planning and implementing an appropriate digital health enterprise within the broader ecosystem includes several phases:smart-base/library/9789240093362-eng, 2.3 Before using this resource, p.12-13 (pdf 24-25) — This handbook is intended to support Phase 5, Determining health content requirements.smart-base/library/9789240101197-eng, Introduction > Alignment with the DIIG, p.5 (pdf 15) — This handbook uses the framework and approaches set forth in the DIIGsmart-base/library/9789240101197-eng, Introduction > Alignment with WHO's SMART Guidelines, p.7 (pdf 17) — This handbook aligns with the L1 Narrative layer by providing guidelines for digital transformation of health supply chains.smart-base/library/9789240116191-eng, Introduction > Digital implementation investment guide (DIIG), p.3 (pdf 12) — It has been developed using the framework and approaches from the Digital implementation investment guide (DIIG).smart-base/library/9789240116191-eng, Introduction > SMART Guidelines, p.6 (pdf 15) — This handbook complements the digital capabilities supported by SMART Guidelines by providing guidance on L1 adaptationssmart-base/library/who-dpi-h-reference-architecture-draft-v1, Executive Summary, pdf p.12 (Figure 1) — The Reference Architecture within planning and implementing a digital health enterprisesmart-base/library/who-dpi-h-reference-architecture-draft-v1, 4.2.2 A Phased Implementation Approach, pdf p.101 — This phased approach is consistent with, and complements, the WHO Digital Implementation Investment Guide (DIIG) |
| 3 | Health programme and business contexthealth-domain-context | required | The health-system domain the handbook digitalises (point-of-service care, supply chain processes, product master data), its actors and why it matters to health outcomes. computed from: library | smart-base/library/9789240093362-eng, 1.1 Person-centred point of service systems, p.6 (pdf 18) — PCPOSS combines the functionality of community-based information systems, decision support systems, electronic medical record or health record systemssmart-base/library/9789240101197-eng, Introduction (Fig. 1 partners and processes), p.1 (pdf 11) — Supply chain processes such as forecasting and planning, sourcing, procurement, order management, warehouse management and dispensing must operate in harmonysmart-base/library/9789240116191-eng, Introduction > What is Product Master Data?, p.1 (pdf 10) — Product master data consists of standardized information that accurately describes a health product's characteristics.smart-base/library/who-dpi-h-reference-architecture-draft-v1, Executive Summary, pdf p.11 (goals detailed in 1.5, pdf p.32-35) — anchored on seven priority health goals ... optimising supply chain management; strengthening health financing |
| 4 | Vision, strategic goals and objectivesstrategy-and-goals | optional | Vision and measurable strategic goals aligned to national health, digital health and sector strategies. PHC and PC treat this as a prerequisite rather than a chapter. computed from: library | smart-base/library/9789240101197-eng, Chapter 1, Step 3. Define the DHSC vision and strategic goals and objectives, p.14 (pdf 24) — Strategic goals guide the country's actions and decisions to achieve the vision.smart-base/library/9789240093362-eng, 2.3 Before using this resource, p.12 (pdf 24) [prerequisite only] — comprehensive high-level needs assessment and strategic planning has already been conductedsmart-base/library/9789240116191-eng, Introduction > When to use this handbook, p.10 (pdf 19) [pointer only] — When developing a holistic DHSC strategysmart-base/library/who-dpi-h-reference-architecture-draft-v1, 3.3 The reference architecture in practice (Figure 3.2), pdf p.59; goals in 1.5, pdf p.32 — Reading from the top, the health goals and the governance that frames them sit above the capabilities they depend onsmart-base/library/who-dpi-h-reference-architecture-draft-v1, 2.4 Methodology: Mapping Health Goals to DPI-H, pdf p.48 — Each goal is mapped systematically to the shared capabilities and application components required to achieve it |
| 5 | Stakeholders, roles and governancestakeholders-and-governance | optional | Stakeholder identification and engagement, decision-making bodies (TWG, steering committee, data governance group), roles and responsibilities. computed from: library | smart-base/library/9789240101197-eng, Chapter 1, Step 1. Identify and engage all relevant stakeholders, p.12 (pdf 22) — Establish a technical working group (TWG) and a steering committeesmart-base/library/9789240116191-eng, 02, Institutionalise product master data governance, p.23 (pdf 32) — Establish a master data governance group composed of all relevant stakeholderssmart-base/library/9789240093362-eng, 3. Understand user requirements (chapter opener), p.16 (pdf 28) [stakeholders only, no governance section] — Stakeholders include, but are not limited to, end-users of the systemsmart-base/library/who-dpi-h-reference-architecture-draft-v1, 3.4.1 Purpose and framing, pdf p.64 (3.4.3 strategic p.66; 3.4.4 operational p.67) — Governance is the set of arrangements through which decision authority is distributed, exercised and accounted forsmart-base/library/who-dpi-h-reference-architecture-draft-v1, 1.3.3 Value Across Stakeholders, pdf p.30 — The value of DPI-H is also distributed across a broad range of stakeholders |
| 6 | Current-state assessmentcurrent-state-assessment | required | Inventory and maturity assessment of existing systems, data and regulations, as the baseline for the target state. computed from: library | smart-base/library/9789240093362-eng, 2.1 Targeted scenarios of digital readiness, p.11 (pdf 23); 3.3.3 As-is and to-be analysis, p.23ff — Starting with some parts of the system already digitizedsmart-base/library/9789240101197-eng, Chapter 2, Step 1. Assess the current state of HSCISs, p.20 (pdf 30) — Assessing the current state of HSCISs involves a thorough evaluation of their capabilities, utilization, technical challenges and overall system maturity.smart-base/library/9789240116191-eng, 02, Define product master data management procedures, p.16 (pdf 25) — Begin by identifying and analyzing the existing challenges in master data managementsmart-base/library/who-dpi-h-reference-architecture-draft-v1, 4.1.2 Assessing Where You Are, pdf p.99 — A national digital health architecture assessment should answer four questions. |
| 7 | Personas, actors and rolespersonas | optional | Generic user personas (PHC) or operational roles (PC data owner/custodian/steward; Annex 2 roles). SC has only target user teams per chapter. computed from: librarymodelled by: sgkg-l2#persona | smart-base/library/9789240093362-eng, 3.2.1 Create user personas, p.21 (pdf 33); Annex 4 User persona worksheet, p.70 — A user persona is a generic depiction of a relevant stakeholdersmart-base/library/9789240116191-eng, 02, Define product master data management procedures, p.17 (pdf 26) [roles, not personas] — Data steward: responsible for the day-to-day management, maintenance, and quality control of the product master data.smart-base/library/who-dpi-h-reference-architecture-draft-v1, 4.3.2 Actors and Roles: Defining Who Participates, pdf p.106 — The operational layer — the digital adaptation kit — defines a set of generic personas |
| 8 | Use cases, user scenarios and user storiesuser-scenarios | optional | How each persona will interact with the system; user stories as the source of functional requirements. computed from: librarymodelled by: sgkg-l2#user-scenario | smart-base/library/9789240093362-eng, 3.2.2 Gather use cases; 3.2.3 Gather user stories, p.21-22 (pdf 33-34); Annex 5 — Use cases highlight the various points of interaction between the users and the systemsmart-base/library/9789240101197-eng, Chapter 2, Illustrative architectural approaches (SCISMM L4 to L5), p.27 (pdf 37) [mention only] — A critical step is defining and prioritizing the use cases that are expected to be supported within the health system and supply chain.smart-base/library/who-dpi-h-reference-architecture-draft-v1, 3.3 The reference architecture in practice, pdf p.59-63 — The clearest way to understand the reference architecture is to follow a single health goal through it. |
| 9 | Business processes and workflowsbusiness-processes | optional | As-is/to-be process maps. A dedicated section only in PHC; SC and PC carry process overviews and the ANC DAK workflow figure in their introductions. computed from: librarymodelled by: sgkg-l2#business-process | smart-base/library/9789240093362-eng, 3.3 Map business processes and workflows, p.23 (pdf 35); Annex 6 — These workflows also represent the functional requirementssmart-base/library/9789240101197-eng, Introduction > Alignment with WHO's SMART Guidelines (Fig. 7), p.7 (pdf 17) — they define recommended public health and clinical business processes that use structured, task-based workflowssmart-base/library/9789240116191-eng, Introduction > SMART Guidelines (Fig. 6), p.6 (pdf 15) — Fig. 6: Example of an Antenatal Care Business clinical workflow with highlighted connections to supply chainsmart-base/library/who-dpi-h-reference-architecture-draft-v1, 3.1 The architecture description approach, pdf p.52 — organised across business, application, and technology layers |
| 10 | Data elements, data dictionary and data modeldata-elements-and-dictionary | optional | Data elements, definitions, coding schemes and mappings to standard terminologies and FHIR. computed from: librarymodelled by: sgkg-l2#data-element | smart-base/library/9789240093362-eng, 3.5 Create a data dictionary, p.30 (pdf 42); 3.4 Streamline data collection, p.27 — Data dictionaries should utilize interoperability standards.smart-base/library/9789240116191-eng, 02, Define coding scheme, data definitions and structures, p.18 (pdf 27) — Map country product identifiers to open standard and global standard structures such as Health Level Seven® (HL7) Fast Healthcare Interoperability Resources® (FHIR)smart-base/library/who-dpi-h-reference-architecture-draft-v1, 4.3.1 Design Data Structures and Data Models First, pdf p.105 — Countries should define and standardise a minimum set of data models for each DPI-H component before implementation beginssmart-base/library/who-dpi-h-reference-architecture-draft-v1, 3.5.3.1 The foundational shared data layer, pdf p.78-81 (see also 3.4.5 p.68; App. C Terminology Service p.175, LIMR p.183) — The shared data layer also includes two components that give data its meaning and structure. |
| 11 | Decision-support logic, schedules and indicatorsdecision-logic-and-indicators | optional | Clinical decision logic, service schedules and indicator calculations (PHC only; SC's KPIs are programme-performance indicators, see monitoring). computed from: librarymodelled by: sgkg-l2#decision-support-logic, sgkg-l2#scheduling-logic, sgkg-l2#program-indicator | smart-base/library/9789240093362-eng, 3.6 Determine decision-support logic, p.32 (pdf 44); 3.7 Map health service schedules, p.35; 3.4.3 Compile aggregate indicators — Documented decision logic algorithmssmart-base/library/who-dpi-h-reference-architecture-draft-v1, 3.5.3.2 The business services layer, pdf p.81; App. C Computable Decision Support Engine p.192; HMIS p.221 — Computable Decision Support Engine — delivers computable clinical guidance to point-of-care systems |
| 12 | Functional and non-functional requirementsrequirements | optional | Prioritized functional and non-functional requirements. SC defers to SCISMM / TSS v2 rather than stating them. computed from: librarymodelled by: sgkg-l2#functional-requirement, sgkg-l2#non-functional-requirement | smart-base/library/9789240093362-eng, 3.8 Gather and prioritize requirements, p.35 (pdf 47); 4.2 Validate functional requirements; Annex 13 — Prioritized functional and non-functional requirementssmart-base/library/9789240116191-eng, 03, Define system requirements for the NPC tool, p.26 (pdf 35) — Define functional and non-functional systems requirements for a NPC toolsmart-base/library/9789240101197-eng, Chapter 2, DHSC architecture framework (key components), p.25 (pdf 35) [by reference] — provide details on the functional and nonfunctional requirements of various HSCISssmart-base/library/who-dpi-h-reference-architecture-draft-v1, App. C Product Registry, pdf p.156-166 (structure per 3.5.2, pdf p.76) — The functional and data requirements in this articulation should be interpreted in that context |
| 13 | Architecture: placement in the enterprise architecture, current and targetarchitecture | required | Where the handbook's systems sit in the national digital health enterprise architecture and which shared components they rely on, cited against the DPI-H Reference Architecture: its layered view (Figure 3.2) and the layer each component belongs to. The three DTHs ingested so far predate the draft Reference Architecture and cite the 2020 DIIG architecture figure, OpenHIE or TOGAF instead; the owner's rule is that a DTH should reference it. computed from: library | smart-base/library/9789240101197-eng, Chapter 2, Step 2. Define a target DHSC architecture, p.22 (pdf 32) — Draw the current-state architecture of the HSCISs by mapping existing systems against the DHSC architecture framework.smart-base/library/9789240093362-eng, 4.4 Design system architecture, p.44 (pdf 56) — the system architecture of a PCPOSS would need to function within an Enterprise Architecture (EA)smart-base/library/9789240116191-eng, Introduction > Digital health supply chain (DHSC) architectural components, p.7 (pdf 16) — The primary focus of this handbook is to offer guidance on the implementation and management of the foundational product registry component.smart-base/library/who-dpi-h-reference-architecture-draft-v1, 3.3 The reference architecture in practice, Figure 3.2, pdf p.59 — A single layered view brings the whole picture together.smart-base/library/who-dpi-h-reference-architecture-draft-v1, 3.5.3 How the components are organised, Figure 3.5, pdf p.77 — The components are organised across two layers of the reference architecture |
| 14 | Standards and interoperabilitystandards-and-interoperability | required | Interoperability layer or dimensions, terminology/content/exchange standards (FHIR, ICD-11, SNOMED GPS, GS1, IDMP). computed from: library | smart-base/library/9789240093362-eng, 4.4.2 Types of interoperability in health; 4.4.3 Types of standards, p.45-47 (pdf 57-59); Annex 14 — Interoperability is commonly split into four broad areassmart-base/library/9789240101197-eng, Chapter 2, DHSC architecture framework, Interoperability layer, p.25 (pdf 35) — The use of an interoperability layer eliminates the need for point-to-point integrations of systemssmart-base/library/9789240116191-eng, 02, Define coding scheme, data definitions and structures, p.18 (pdf 27) — identification of medicinal products (IDMP), and GS1's global trade item numberssmart-base/library/who-dpi-h-reference-architecture-draft-v1, 3.6 Interoperability Architecture within DPI-H, pdf p.82 — Interoperability, therefore, is a cross-cutting capability of the reference architecture as a wholesmart-base/library/who-dpi-h-reference-architecture-draft-v1, 4.3.3 Services and Transactions: FHIR as the Recommended Framework, pdf p.107 (see also 3.6.2, pdf p.84) — The reference architecture recommends HL7 FHIR as the framework for specifying and implementing health data exchange services and transactions. |
| 15 | Technology selection, design, build and deploymenttechnology-selection-and-implementation | required | Choosing/sourcing software, design, build, testing and deployment of the system. computed from: library | smart-base/library/9789240093362-eng, 4.1 Finalize software and vendor selection, p.40 (pdf 52); 4.5 Build and QA; 5.3 Deploy the system — Finalize software and vendor selectionsmart-base/library/9789240101197-eng, Chapter 3, Step 4. Implement each DHSC intervention, p.41 (pdf 51) — DHSC implementation materials such as requirements, specifications, test scripts and job aidssmart-base/library/9789240116191-eng, 03, Design, develop and deploy the NPC tool, p.28 (pdf 37) — Deploy the validated NPC tool, load the available product master data and roll out.smart-base/library/who-dpi-h-reference-architecture-draft-v1, 4.3 Profiles and Specifications for Implementation, pdf p.105 — the minimum level of specification that countries should establish regardless of the technology choicessmart-base/library/who-dpi-h-reference-architecture-draft-v1, 3.7.1 Purpose, pdf p.89 — The reference architecture offers a common benchmark against which such architectures — and the systems that realise them — can be assessed |
| 16 | Roadmap, budget, scale-up and legacy phase-outroadmap-budget-and-scale | optional | Sequencing, costing, operational planning and scale-up. PC gives phased regulatory roll-out timelines but no roadmap or budget. computed from: library | smart-base/library/9789240101197-eng, Chapter 3, Step 3. Develop a budget for each DHSC intervention, p.39 (pdf 49); Ch.1 Step 4 roadmap — A strategic roadmap for DHSC sets out timelines and milestones for achieving goalssmart-base/library/9789240093362-eng, 6. Prepare for scale-up, p.54 (pdf 66); 6.2 Plan for phase-out of legacy system(s) — Plan for phase-out of legacy system(s)smart-base/library/who-dpi-h-reference-architecture-draft-v1, 4.2.2 A Phased Implementation Approach, pdf p.101 (4.2.3 Navigating Legacy Systems, p.104) — implementation follows a broadly consistent phased progressionsmart-base/library/who-dpi-h-reference-architecture-draft-v1, 4.6 Financing and Partnerships, pdf p.113 — The Investment Case |
| 17 | Capacity building, training and change managementcapacity-and-change-management | required | Human resources, training, SOPs and change management for adoption. computed from: library | smart-base/library/9789240093362-eng, 5.1 Develop and conduct training, p.52 (pdf 64); 6.5 Adopt change management practices, p.59 — Adopt change management practicessmart-base/library/9789240101197-eng, Chapter 3, Step 1 (project management plan), p.37 (pdf 47) — change management plan (including trainingsmart-base/library/9789240116191-eng, 05. Building capacity to sustainably manage NPC, p.33 (pdf 42); 04 change management, p.29 — Human resource capacity is a critical component for the successful implementation and adoptionsmart-base/library/who-dpi-h-reference-architecture-draft-v1, 4.5 Roles, Skills, and Capacity, pdf p.111 — The Roles and Skills Needed to Build and Govern the Architecture |
| 18 | Monitoring, evaluation and performance indicatorsmonitoring-and-evaluation | optional | M&E framework and KPIs with baselines. PC has only data-management monitoring inside its procedures. computed from: librarymodelled by: sgkg-l2#program-indicator | smart-base/library/9789240093362-eng, 6.3 Monitor and evaluate progress on objectives, p.59 (pdf 71) — it is crucial that the PCPOSS has a clear and robust monitoring and evaluation plan and methodologysmart-base/library/9789240101197-eng, Chapter 1, Step 4. Define a strategic roadmap and performance indicators, p.15 (pdf 25) — Capture baseline performance for comparison with improvements after implementationsmart-base/library/who-dpi-h-reference-architecture-draft-v1, 4.4.1 Assessing impact: Are goals being achieved?, pdf p.110 — Impact depends on baselines captured at the outsetsmart-base/library/who-dpi-h-reference-architecture-draft-v1, 4.4.1 Assessing impact, pdf p.110 (refers to 3.7.5, pdf p.96) — the goal-validation structure described in section 3.7 |
| 19 | Country implementation examplescountry-examples | optional | Worked country experiences. computed from: library | smart-base/library/9789240101197-eng, Chapter 5. Country examples, p.47 (pdf 57) — Ethiopia's DHSC initiativesmart-base/library/9789240116191-eng, 08. Sharing implementation experiences, p.42 (pdf 51) — COUNTRY: RWANDAsmart-base/library/who-dpi-h-reference-architecture-draft-v1, Appendix D: Country and Regional Implementation Examples, pdf p.240 — D.2 Country implementation examples |
| 20 | Annexes: templates and worksheetstemplates-and-worksheets | required | Reusable templates (persona/user-story worksheets, process matrix, HSCIS listing, risk register, role descriptions). computed from: library | smart-base/library/9789240093362-eng, Annexes 2-14, p.66-84 — User persona worksheetsmart-base/library/9789240101197-eng, Annexes 2-7, p.57-62 — Template for listing health supply chain information systemssmart-base/library/9789240116191-eng, Annex 2. Additional roles for NPC implementation, p.48 — Develop use cases or user stories |
| 21 | Abbreviations and glossaryglossary | required | Abbreviations and defined terms. computed from: library | smart-base/library/9789240093362-eng, Abbreviations p.v; Glossary p.vismart-base/library/9789240101197-eng, Abbreviations and acronyms p.v; Glossary p.vismart-base/library/9789240116191-eng, Abbreviations p.v; Glossary p.vii |
| 22 | Annex: Principles for Digital Developmentprinciples-for-digital-development | required | All three DTHs carry the Principles for Digital Development as Annex 1. computed from: library | smart-base/library/9789240093362-eng, Annex 1: Principles for digital development, p.65 (pdf 77) — Principles for digital developmentsmart-base/library/9789240101197-eng, Annex 1. Principles for digital development, p.56 (pdf 66) — The steps outlined in this handbook are informed by the Principles for Digital Development (Annex 1).smart-base/library/9789240116191-eng, Annex 1. Principles for Digital Development, p.47 (pdf 56) — Build on what works, improve what works, and share so that others can do the same.smart-base/library/who-dpi-h-reference-architecture-draft-v1, 1.4 DPI-H Principles, pdf p.31; 2.3 DPI-H Reference Architecture Design Principles, pdf p.42 — DPI-H Principles |
Sources: smart-base/library/9789240093362-eng — DTH for primary health care; smart-base/library/9789240101197-eng — DTH for health supply chain architecture; smart-base/library/9789240116191-eng — DTH for health product catalogue; smart-base/library/who-dpi-h-reference-architecture-draft-v1, title page — A Digital Transformation Handbook for Digital Public Infrastructure for Health (DPI-H); smart-base/library/9789240010567-eng — Digital Implementation Investment Guide (DIIG), the process a DTH sits in
WHO guideline (L1) l1-guideline
An L1 publication containing recommendations for clinical practice or public health policy, structured as the WHO Handbook for Guideline Development (2nd ed.) §12.1 "Guideline format" requires, with the SMART additions Mehl 2021 names: uniquely identified recommendations and data recommendations. Sections modelled by smart-kg L1 classes are the ones a smart-kg L1 graph of the guideline holds (bean 8pzh).
semi-fixed structure · 16 section(s) · extends l1 · declared by smart-base in smart-base/document-kinds/l1-guideline.json
| # | Section | What it holds | Source | |
|---|---|---|---|---|
| 1 | Executive summaryexecutive-summary | required | A stand-alone summary that states the key recommendations, each with its strength and the certainty of its evidence. computed from: library | who-iris/library/9789241548960-eng, §12.1 Guideline format, PDF p.169; sections/sec-225-121-guideline-format.md — All guidelines should have an executive summary, a main body and appendices. The executive summary should contain the key recommendations of the guideline.who-iris/library/9789241548960-eng, §12.1 Guideline format, PDF p.169; sections/sec-225-121-guideline-format.md — the strength of the recommendation and the quality of the evidence for each recommendation should be specified in the executive summary |
| 2 | Table of contentstable-of-contents | required | Navigational listing of the main-body sections. computed from: library | who-iris/library/9789241548960-eng, §12.1 Guideline format, PDF p.169; sections/sec-225-121-guideline-format.md — The main text of the guideline should include a table of contents, introduction, methods, recommendations and conclusions. |
| 3 | Target audience and persons affectedtarget-audience | optional | Who will apply the recommendations (end-users), distinguished from the people who receive the interventions. computed from: library | who-iris/library/9789241548960-eng, §2.2.3 Who is the target audience?, PDF p.29; sections/sec-030-223-who-is-the-target-audience.md — Guidelines must have a clearly defined target audience (end-user) which is identified early in the guideline development processwho-iris/library/9789241548960-eng, §2.2.3 Who is the target audience?, PDF p.29; sections/sec-030-223-who-is-the-target-audience.md — the end-users are those who will apply the guidelines, not the recipients of the recommended interventions.who-iris/library/9789241548960-eng, §4.5 Table 4.1 Essential components of the planning proposal, PDF pp.53-55; sections/sec-075-44-when-should-the-planning-proposal-be-develope.md — 3. Target audience 3.1 The end-user(s) of the guideline |
| 4 | Declarations of interest and their managementdeclarations-of-interest | required | Lists every participant with role and affiliation, and summarises how declarations of interest were collected, assessed and managed (stating explicitly if none were disclosed); acknowledges peer reviewers. computed from: library | who-iris/library/9789241548960-eng, §12.1 Guideline format, PDF p.169; sections/sec-225-121-guideline-format.md — All participants, roles and affiliations should be listed, with their conflicts of interests and how these were managed.who-iris/library/9789241548960-eng, §6.11 Reporting declarations of interest in the guideline, PDF pp.84-86; sections/sec-105-6102-minimizing-the-risk-posed-by-conflicts-of-i.md — A summary of how declarations of interest were collected, assessed and managed must be included in the main guideline document.who-iris/library/9789241548960-eng, §6.11, PDF pp.84-86; sections/sec-105-6102-minimizing-the-risk-posed-by-conflicts-of-i.md — The GRC will not approve a guideline document that does not contain this information.who-iris/library/9789241548960-eng, §12.2 Peer review, PDF p.170; sections/sec-225-121-guideline-format.md — a copy of the published guideline (which includes an acknowledgement of their contribution)smart-base/library/mehl-2021-who-smart-guidelines, Comment, p. e214; sections/sec-000-who-smart-guidelines-optimising-country-level-us.md — L1 also recognises the need for increased representation of health informaticians on guideline panels |
| 5 | Funding sourcesfunding | required | Names every funder of the guideline and, where not evident, the type of entity. computed from: library | who-iris/library/9789241548960-eng, §6.8 Table 6.2 Principles for declarations of interest, PDF pp.76-79; sections/sec-099-68-assessing-declarations-of-interests.md — All funding sources should be reported in the planning proposal and in the final guideline.who-iris/library/9789241548960-eng, §3.6 Funders of the guideline, PDF p.46; sections/sec-060-36-funders-of-the-guideline.md — The funder(s) of a guideline can play no role in the guideline development process and should not influence the recommendations. |
| 6 | Key questions (PICO) and outcomeskey-questions | optional | The foreground questions in population-intervention-comparator-outcome form, the outcomes rated important or critical, and optionally an analytic framework. The PICO question sets themselves come from the guideline development group's scoping and the systematic reviews behind it, which smart-base has not ingested. So this section names no `computedFrom`: computing it needs an evidence graph that does not exist yet (owner, 2026-10-04, bean qvxh, option 1). Ingesting that evidence is bean folio-assistant-0lde. modelled by: sgkg-l1#population, sgkg-l1#intervention, sgkg-l1#comparator, sgkg-l1#outcome | who-iris/library/9789241548960-eng, §10.6 Writing recommendations, PDF pp.142-143; sections/sec-180-106-writing-recommendations.md — Recommendations need to be clear and actionable, reflect the PICO formatwho-iris/library/9789241548960-eng, §7.8 Analytic frameworks, PDF pp.103-104; sections/sec-130-78-analytic-frameworks.md — The analytic framework may be included with the planning proposal or in the final guideline publicationwho-iris/library/9789241548960-eng, §4.5 Table 4.1, PDF pp.53-55; sections/sec-075-44-when-should-the-planning-proposal-be-develope.md — 10.2 Foreground (key/PICO) questions |
| 7 | Evidence retrieval and synthesisevidence-retrieval-and-synthesis | optional | Search strategy, study selection and synthesis of the systematic reviews informing each key question; full reviews may sit in annexes. The systematic reviews it summarises (for WHO guidelines, typically Cochrane or WHO-commissioned reviews) are external evidence that smart-base has not ingested. So this section names no `computedFrom`: computing it needs an evidence graph that does not exist yet (owner, 2026-10-04, bean qvxh, option 1). Ingesting that evidence is bean folio-assistant-0lde. modelled by: sgkg-l1#evidence | who-iris/library/9789241548960-eng, §12.1 Guideline format, PDF p.169; sections/sec-225-121-guideline-format.md — The systematic reviews need to be reported in compliance with the Preferred Reporting Items for Systematic Reviews and Meta-Analyses (PRISMA)who-iris/library/9789241548960-eng, §8.3 Step 2 Identify information sources, PDF pp.111-113; sections/sec-140-step-2-identify-information-sources-and-search-f.md — The development and finalization of the strategies for searching for evidence that meets the established inclusion criteria is a fundamental step |
| 8 | Certainty of the evidence (GRADE)certainty-of-evidence | optional | GRADE assessment of the body of evidence per outcome and key question, summarised in evidence profiles. The GRADE evidence profiles it summarises are built from external systematic reviews (typically Cochrane) that smart-base has not ingested. So this section names no `computedFrom`: computing it needs an evidence graph that does not exist yet (owner, 2026-10-04, bean qvxh, option 1). Ingesting that evidence is bean folio-assistant-0lde. modelled by: sgkg-l1#evidence | who-iris/library/9789241548960-eng, §9.2 What are GRADE evidence profiles?, PDF p.122; sections/sec-154-92-what-are-grade-evidence-profiles.md — GRADE evidence profiles contain the assessment of the quality of the evidence and a summary of findings across studieswho-iris/library/9789241548960-eng, §12.1 Guideline format, PDF p.169; sections/sec-225-121-guideline-format.md — GRADE evidence profiles, evidence-to-decision frameworks and tables, and any other relevant documentation can be supplied in appendices |
| 9 | Evidence to decisionevidence-to-decision | optional | Records the judgements on benefits and harms, values and preferences, resources, equity, acceptability and feasibility that shaped each recommendation's direction and strength. Its judgements rest on the GRADE evidence profiles and the systematic reviews behind them, which smart-base has not ingested. So this section names no `computedFrom`: computing it needs an evidence graph that does not exist yet (owner, 2026-10-04, bean qvxh, option 1). Ingesting that evidence is bean folio-assistant-0lde. | who-iris/library/9789241548960-eng, §10.3 Evidence-to-recommendation tables, PDF p.140; sections/sec-174-103-evidence-to-recommendation-tables.md — These tables enhance the transparency of the process, focus the discussions of the GDG and permit recording of the judgements madewho-iris/library/9789241548960-eng, §10.3, PDF p.140; sections/sec-174-103-evidence-to-recommendation-tables.md — the GDG should, at a minimum, document its judgements on the four main factors. |
| 10 | Recommendationsrecommendations | required | Each recommendation stated actionably, with its direction, strength, certainty of evidence, justification and remarks on applicability, linked to its evidence. For SMART use, each is uniquely identified so digital systems can cite it, and data recommendations may be included. computed from: librarymodelled by: sgkg-l1#recommendation | who-iris/library/9789241548960-eng, §12.1 Guideline format, PDF p.169; sections/sec-225-121-guideline-format.md — The main text of the guideline should include a table of contents, introduction, methods, recommendations and conclusions.who-iris/library/9789241548960-eng, §10.6 Writing recommendations, PDF pp.142-143; sections/sec-180-106-writing-recommendations.md — contain an indication of their strength and of the quality of the evidence on which they are based.who-iris/library/9789241548960-eng, §10.6, PDF pp.142-143; sections/sec-180-106-writing-recommendations.md — A recommendation should include a justification as to why it is strong or conditional and why it is for or against a given intervention.who-iris/library/9789241548960-eng, §10.6, PDF pp.142-143; sections/sec-180-106-writing-recommendations.md — Each recommendation should be linked to a summary of the evidencesmart-base/library/mehl-2021-who-smart-guidelines, Comment, pp. e213-e214; sections/sec-000-who-smart-guidelines-optimising-country-level-us.md — uniquely identifying recommendations, which are updated as evidence improves over time (living guidelines)smart-base/library/mehl-2021-who-smart-guidelines, Figure 1, p. e214; sections/sec-000-who-smart-guidelines-optimising-country-level-us.md — L1: Narrative Guideline and data recommendations: Enhanced guidelines |
| 11 | Implementation and adaptation considerationsimplementation-considerations | optional | Conditions, context, acceptability concerns and adaptation points relevant to applying the recommendations in a setting. computed from: librarymodelled by: sgkg-l1#remark | who-iris/library/9789241548960-eng, §10.6, PDF pp.142-143; sections/sec-180-106-writing-recommendations.md — contain a set of remarks explaining the conditions and context in which the recommendation applies and the points to bear in mind regarding implementation.who-iris/library/9789241548960-eng, §10.2.7 Acceptability, PDF pp.139-140; sections/sec-172-1027-acceptability.md — a strategy to address concerns about acceptability during implementation will be included in the guideline with the recommendations.who-iris/library/9789241548960-eng, Ch.13 Adaptation, implementation and evaluation, PDF pp.177-178; sections/sec-246-13-adaptation-implementation-and-evaluation.md — Although implementation and evaluation plans do not need to be described in the guideline, they should be considered by the steering groupsmart-base/library/mehl-2021-who-smart-guidelines, Comment, p. e214; sections/sec-000-who-smart-guidelines-optimising-country-level-us.md — The adaptation toolkit and monitoring framework aim to facilitate country adaptation and implementation of the recommendations. |
| 12 | Equity, human rights and gender considerationsequity-human-rights-and-gender | optional | How the recommendations bear on equity, human rights, gender and social determinants, and how their equity impact should be evaluated. computed from: library | who-iris/library/9789241548960-eng, §5.4.3.1 Producing and publishing the guideline, PDF pp.65-66; sections/sec-089-543-phase-3-publishing-and-updating.md — The final guideline and in its derivative products must convey clear messages with respect to equity, human rights, gender and social determinants.who-iris/library/9789241548960-eng, §5.4.2.3 Developing recommendations, PDF pp.64-65; sections/sec-088-542-phase-2-development.md — Evaluation and monitoring of the impact of recommendations that potentially affect inequities are also critically important and should be articulated in the guideline document. |
| 13 | Monitoring and evaluationmonitoring-and-evaluation | required | Outcome or performance measures that can be monitored for the main recommendations. computed from: librarymodelled by: sgkg-l1#indicator | who-iris/library/9789241548960-eng, §13.3 Monitoring and evaluation, PDF pp.178-179; sections/sec-247-133-monitoring-and-evaluation.md — The guideline should include outcome or performance measures that can be monitored for the main recommendations.smart-base/library/mehl-2021-who-smart-guidelines, Comment, p. e214; sections/sec-000-who-smart-guidelines-optimising-country-level-us.md — WHO recommendations on antenatal care for a positive pregnancy experience,6 as well as the adaptation toolkit7 and monitoring framework8 are illustrative tools of ANC L1. |
| 14 | Research gaps and future researchresearch-gaps | optional | Knowledge gaps that leave the balance of benefits and harms uncertain, with suggested questions (ideally in PICO form) and methods to close them. computed from: library | who-iris/library/9789241548960-eng, §10.8 Future research, PDF p.144; sections/sec-182-108-future-research.md — such knowledge gaps should be described and questions and methods for addressing the gaps should be suggested.who-iris/library/9789241548960-eng, §10.8, PDF p.144; sections/sec-182-108-future-research.md — This section of the guideline document will inform future recommendations and guidelines.who-iris/library/9789241548960-eng, §5.4.2.3, PDF pp.64-65; sections/sec-088-542-phase-2-development.md — the guideline should outline the key gaps in knowledge and provide an agenda for future research. |
| 15 | Conclusionsconclusions | required | Closing summary of the main body. computed from: library | who-iris/library/9789241548960-eng, §12.1 Guideline format, PDF p.169; sections/sec-225-121-guideline-format.md — The main text of the guideline should include a table of contents, introduction, methods, recommendations and conclusions. |
| 16 | Validity and updatingupdating | required | The review-by date and how the recommendations will be kept current; under SMART, recommendations are versioned as living guidance. computed from: library | who-iris/library/9789241548960-eng, §12.5.1 Review-by date, PDF p.175; sections/sec-241-1251-review-by-date.md — WHO guidelines should be issued with a “review-by” date to indicate how long the recommendations are expected to remain valid.who-iris/library/9789241548960-eng, §4.5 Table 4.1 (continued; extracted into the §4.6 file), PDF pp.55-56; sections/sec-076-46-what-if-there-are-major-changes-in-scope-or-a.md — 17. Updating 17.1 Plans for when and how to updatesmart-base/library/mehl-2021-who-smart-guidelines, Comment, pp. e213-e214; sections/sec-000-who-smart-guidelines-optimising-country-level-us.md — uniquely identifying recommendations, which are updated as evidence improves over time (living guidelines) |
Sources: who-iris/library/9789241548960-eng, §1.1 What is a WHO guideline?, PDF p.13; sections/sec-002-11-what-is-a-who-guideline.md — A WHO guideline is any document developed by the World Health Organization containing recommendations for clinical practice or public health policy.
L1 narrative publication l1
The narrative layer of the WHO SMART Guidelines: "traditional guidelines and guidance" (Mehl 2021). Only the frame a WHO guideline and a Digital Transformation Handbook BOTH carry is here; what each puts in its body is a sub-kind — l1-guideline (recommendations, evidence, GRADE) and dth (a digital transformation handbook). Semi-fixed: these sections are required, others are allowed.
semi-fixed structure · 5 section(s) · declared by smart-base in smart-base/document-kinds/l1.json
| # | Section | What it holds | Source | |
|---|---|---|---|---|
| 1 | Introduction: background, scope and objectivesintroduction | required | Why the publication is needed, what it covers and what it explicitly does not, and its objectives. computed from: librarymodelled by: sgkg-l1#publication-section | who-iris/library/9789241548960-eng, §12.1 Guideline format, PDF p.169; sections/sec-225-121-guideline-format.md — The main text of the guideline should include a table of contents, introduction, methods, recommendations and conclusions.who-iris/library/9789241548960-eng, §2.2.1 What will the guideline achieve?, PDF p.28; sections/sec-028-221-what-will-the-guideline-achieve.md — Resolving uncertainty should be the focus of most guidelines.smart-base/library/9789240093362-eng, 1. Introduction, p.1 (pdf 13) — This handbook not only discusses digitization of paper-based records, but also helps countries move towards digitalizationsmart-base/library/9789240101197-eng, Introduction > What this handbook covers, p.3 (pdf 13) — It does not delve into the intricacies of supply chain processes or the specific functional specifications of various health supply chain information systemssmart-base/library/9789240116191-eng, Introduction > When to use this handbook, p.10 (pdf 19) — When establishing standardized product master data management to support interoperability of health supply chain systems and processes. |
| 2 | How it was developedhow-it-was-developed | required | The method the publication was developed by: for a guideline, the methods the Guideline Review Committee approves; for a handbook, the consultations, working groups, desk reviews and frameworks it was derived from. computed from: librarymodelled by: sgkg-l1#publication-section | who-iris/library/9789241548960-eng, §12.1 Guideline format, PDF p.169; sections/sec-225-121-guideline-format.md — The main text of the guideline should include a table of contents, introduction, methods, recommendations and conclusions.who-iris/library/9789241548960-eng, §1.10.1 Terms of reference of the GRC, PDF pp.24-25; sections/sec-020-1101-terms-of-reference-of-the-grc.md — ensures that the approved process has been followed and that the final guideline document meets WHO standardssmart-base/library/9789240093362-eng, 1.3 How this handbook was developed, p.9 (pdf 21) — How this handbook was developedsmart-base/library/9789240101197-eng, Introduction > How this handbook was developed, p.7 (pdf 17) — Some methodologies and templates have been adapted from prominent sources such as the DIIGsmart-base/library/9789240116191-eng, Introduction > How this handbook was developed, p.8 (pdf 17) — DHSC Small Working Group (DHSC SWG): a subgroup under the Digital Health and Interoperability Working Group |
| 3 | Contributors and acknowledgementscontributors | required | Everyone who contributed, with role and affiliation. A guideline adds declarations of interest and how they were managed (l1-guideline). computed from: librarymodelled by: sgkg-l1#publication-section | who-iris/library/9789241548960-eng, §12.1 Guideline format, PDF p.169; sections/sec-225-121-guideline-format.md — All participants, roles and affiliations should be listed, with their conflicts of interests and how these were managed.smart-base/library/9789240093362-eng, Acknowledgements, p.ivsmart-base/library/9789240101197-eng, Acknowledgements, p.ivsmart-base/library/9789240116191-eng, Acknowledgements, p.iv |
| 4 | Referencesreferences | required | Citations for the evidence and every supporting source. computed from: librarymodelled by: sgkg-l1#citation | who-iris/library/9789241548960-eng, §12.1 Guideline format, PDF p.169; sections/sec-225-121-guideline-format.md — All online material needs to be cited in the guideline itself and supplied to the GRC when final approval is sought.who-iris/library/9789241548960-eng, §8.3 Step 2, PDF pp.111-113; sections/sec-140-step-2-identify-information-sources-and-search-f.md — use it to formulate the reference lists in the final guideline document.smart-base/library/9789240116191-eng, References, p.46 (pdf 55)smart-base/library/9789240093362-eng, References, p.60 |
| 5 | Annexesannexes | required | Supporting material too detailed for the main body. computed from: librarymodelled by: sgkg-l1#publication-section | who-iris/library/9789241548960-eng, §12.1 Guideline format, PDF p.169; sections/sec-225-121-guideline-format.md — All guidelines should have an executive summary, a main body and appendices.smart-base/library/9789240093362-eng, Annex 1: Principles for digital development, p.65 (pdf 77) — Principles for digital development |
Sources: smart-base/library/mehl-2021-who-smart-guidelines, Comment, p. e214, para 'The first knowledge layer'; sections/sec-000-who-smart-guidelines-optimising-country-level-us.md — The first knowledge layer (L1: Narrative layer—enhanced guidelines) represents traditional guidelines and guidance; smart-base/library/mehl-2021-who-smart-guidelines, Figure 1 (WHO SMART guidelines), p. e214; sections/sec-000-who-smart-guidelines-optimising-country-level-us.md — L1: Narrative Guideline and data recommendations: Enhanced guidelines; https://github.com/litlfred/folio-assistant/issues/1767 — owner 2026-10-01: L1 sections from the SMART Guidelines paper, the WHO guideline handbook and the DTHs, each section citing its own