{ "methodologies": [ { "id": "dth-phc-stepwise-digitizing", "title": "Stepwise approach to digitizing primary health care (PCPOSS)", "summary": "The PHC handbook's end-to-end path from a paper system to a person-centred point of service system, in four phases that structure the handbook (Chapters 3-6), run iteratively in an agile loop (Fig. 7) rather than strictly linearly. The handbook places itself at Phase 5 (\"Determining health content requirements\") of the DIIG-derived digital-health-enterprise figure, so it is a domain instance downstream of DIIG rather than a rival to it.", "steps": [ { "n": 1, "name": "Understand user requirements", "detail": "Understand users, map their workflows, understand data needs and care pathways (Chapter 3)." }, { "n": 2, "name": "Undertake design and adaptation", "detail": "Design or adapt the PCPOSS for its context (Chapter 4)." }, { "n": 3, "name": "Conduct training, testing and roll-out", "detail": "Test with end users and equip them to use it (Chapter 5)." }, { "n": 4, "name": "Prepare for scaling up", "detail": "Plan health information exchange within an enterprise architecture and phase out legacy systems (Chapter 6)." }, { "n": 5, "name": "Iterate (cross-cutting)", "detail": "Agile loop of build-test-train-deploy-gather feedback until MVP specs are met, then continuous-improvement iterations (Fig. 7)." } ], "status": "extends:smart-base/methodologies/diig.md", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-010-24-the-stepwise-approaches-to-digitizing", "pages": "26-27", "quote": "This handbook outlines the end-to-end process that will help transition from a paper system to a digital system." }, { "libraryId": "9789240093362-eng", "sectionId": "sec-010-24-the-stepwise-approaches-to-digitizing", "pages": "26-27", "quote": "Quick prototyping and incorporation of feedback is often performed based on the agile methodology" }, { "libraryId": "9789240093362-eng", "sectionId": "sec-009-23-before-using-this-resource", "pages": "24-26", "quote": "This handbook is intended to support Phase 5, Determining health content requirements." } ] }, { "id": "dth-digital-health-enterprise-seven-phases", "title": "Planning and implementing a digital health enterprise: seven phases (DIIG-derived figure)", "summary": "All three handbooks reproduce the same DIIG-adapted figure of seven phases, each with steps and named resources, and position themselves on it. It is DIIG's own framing but is NOT the nine-chapter sequence that diig.md renders, so it is a second view of the same source method. Figure text is vector-extracted; phase-to-handbook placement for the supply-chain and product-catalogue handbooks cannot be read from the text and is not asserted here.", "steps": [ { "n": 1, "name": "Assessing the current state and enabling environment" }, { "n": 2, "name": "Establishing a shared understanding and strategic planning" }, { "n": 3, "name": "Defining the future state" }, { "n": 4, "name": "Planning the enterprise architecture" }, { "n": 5, "name": "Determining health content requirements" }, { "n": 6, "name": "M&E of digital health implementations and fostering data use" }, { "n": 7, "name": "Implementing, maintaining and scaling" } ], "status": "overlaps:smart-base/methodologies/diig.md", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-009-23-before-using-this-resource", "pages": "24-26", "quote": "Planning and implementing a digital health enterprise: phases, steps and resources" }, { "libraryId": "9789240101197-eng", "sectionId": "page-015", "pages": "15", "quote": "DIIG process for planning and implementing a digital health enterprise" }, { "libraryId": "9789240116191-eng", "sectionId": "page-013", "pages": "13", "quote": "Planning and implementing a digital health enterprise: phases, steps and resources" } ] }, { "id": "dth-phc-requirements-gathering-methods", "title": "Requirements-gathering methods (desk review, observation, interviews, workshops)", "summary": "A combination of corroborating methods used before and during Chapter 3: desk review first, then observation/shadowing and semi-structured interviews (broad-to-narrow, \"5 whys\", Fig. 8), follow-up interviews to verify observations, and requirements-gathering workshops reserved for validation at the end.", "steps": [ { "n": 1, "name": "Desk review", "detail": "National and context-specific guidelines, registers, reporting tools, DAKs, SCORE." }, { "n": 2, "name": "Observations", "detail": "Shadow health workers at various busy/quiet times; Annex 3 observation worksheet; respect confidentiality and consent." }, { "n": 3, "name": "Semi-structured interviews", "detail": "Agreed minimum question set; broad to narrow; avoid leading/hypothetical questions; Annex 2 interview guide." }, { "n": 4, "name": "Follow-up interviews", "detail": "Verify observations and find root causes of observed actions." }, { "n": 5, "name": "Requirements-gathering workshops", "detail": "Validate requirements gathered through other methods with end-users and secondary users." } ], "status": "overlaps:cat-harness/processes/crdm-needs.bpmn", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-012-31-follow-key-requirement-gathering-methods", "pages": "30-33", "quote": "this section provides an overview of some of these methods: desk review, semi-structured interviews, observations, follow-up interviews to verify observations, and requirements-gathering workshops." }, { "libraryId": "9789240093362-eng", "sectionId": "sec-012-31-follow-key-requirement-gathering-methods", "pages": "30-33", "quote": "Workshops can be reserved for the end of the requirements-gathering process to validate requirements gathered through other methods" } ] }, { "id": "dth-dhsc-stepwise-approach", "title": "Stepwise approach to digitalizing the health supply chain (DHSC)", "summary": "Umbrella method of the supply-chain handbook: four chapters, each a stepwise sub-method (strategy, architecture, implementation) plus a traceability chapter. Built on the DIIG framework and assumes supply chain process/maturity assessments and an adopted supply chain design as prerequisites.", "steps": [ { "n": 1, "name": "Defining a holistic DHSC strategy", "detail": "Steps 1-4; see dth-dhsc-strategy." }, { "n": 2, "name": "Defining the DHSC architecture", "detail": "Steps 1-3; see dth-dhsc-architecture." }, { "n": 3, "name": "Planning for scalable implementation and sustainable operations", "detail": "Steps 1-4; see dth-dhsc-implementation." }, { "n": 4, "name": "Using the DHSC to implement traceability", "detail": "Traceability models and components; see process dhsc-traceability-event-flow." } ], "status": "extends:smart-base/methodologies/diig.md", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-014", "pages": "14", "quote": "This handbook provides a stepwise approach to digitalizing the health supply chain, as depicted in Fig. 4." }, { "libraryId": "9789240101197-eng", "sectionId": "page-013", "pages": "13", "quote": "This handbook assumes that the country has conducted supply chain process and maturity assessments and has adopted an appropriate supply chain design." }, { "libraryId": "9789240101197-eng", "sectionId": "page-015", "pages": "15", "quote": "This handbook uses the framework and approaches set forth in the DIIG" } ] }, { "id": "dth-dhsc-strategy", "title": "Defining a holistic DHSC strategy (Chapter 1, Steps 1-4)", "summary": "Produces the DHSC vision, strategic goals, strategic objectives and strategic roadmap, aligned with national health, IT, digital-health, supply-chain and medicines strategies. SOURCE DEFECT: the text announces \"five steps\" but lists and details four.", "steps": [ { "n": 1, "name": "Identify and engage all relevant stakeholders" }, { "n": 2, "name": "Analyse the current state of HSCISs" }, { "n": 3, "name": "Define the DHSC vision and strategic goals and objectives" }, { "n": 4, "name": "Define a strategic roadmap and performance indicators" } ], "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-021", "pages": "21", "quote": "The following sections describe five steps to developing a DHSC vision, strategic goals and measurable objectives" }, { "libraryId": "9789240101197-eng", "sectionId": "page-026", "pages": "26", "quote": "The steps outlined in this chapter will result in the following outputs (Fig. 10):" } ] }, { "id": "dth-dhsc-architecture", "title": "Defining the DHSC architecture (Chapter 2, Steps 1-3)", "summary": "Assess current HSCISs (using SCISMM, five maturity levels: Reporting Based, Transactional, Advanced Digitalization, End to End Visibility, Digital Ecosystem), define a target architecture against the DHSC architecture framework (foundational components, interoperability layer, HSCISs, data services, external systems, digital ecosystems), then map implementation activities to strategic goals. Offers illustrative approaches: maturity-based (SCISMM L3->L4, L4->L5) and supply-chain-design-based (centralized; decentralized options A and B).", "steps": [ { "n": 1, "name": "Assess the current state of HSCISs" }, { "n": 2, "name": "Define a target DHSC architecture" }, { "n": 3, "name": "Identify implementation activities and map them to strategic goals" } ], "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-029", "pages": "29", "quote": "The following sections detail the steps to defining an overarching DHSC architecture." }, { "libraryId": "9789240101197-eng", "sectionId": "page-031", "pages": "31", "quote": "SCISMM provides a continuum of maturity for systems that support health supply chain functions (Fig. 12)" } ] }, { "id": "dth-dhsc-implementation", "title": "Planning for scalable implementation and sustainable operations (Chapter 3, Steps 1-4)", "summary": "Per DHSC intervention: project plan, operational plan, budget (total cost of ownership over 5-10 years) and implementation, framed by the seven building blocks of the WHO-ITU National eHealth Strategy Toolkit. The budget step and TCO figure are adapted from the DIIG.", "steps": [ { "n": 1, "name": "Plan the implementation of each DHSC intervention" }, { "n": 2, "name": "Develop an operational plan for each DHSC intervention" }, { "n": 3, "name": "Develop a budget for each DHSC intervention" }, { "n": 4, "name": "Implement each DHSC intervention" } ], "status": "overlaps:smart-base/methodologies/diig.md", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-045", "pages": "45", "quote": "They are derived from the seven foundational building blocks of digital health as outlined in the WHO-ITU National eHealth Strategy Toolkit (Fig. 22)." }, { "libraryId": "9789240101197-eng", "sectionId": "page-046", "pages": "46", "quote": "each intervention should include a project implementation plan, an operational plan and a budget that considers the total cost of ownership." }, { "libraryId": "9789240101197-eng", "sectionId": "page-049", "pages": "49", "quote": "Budget matrix template (from the DIIG)" } ] }, { "id": "dth-dhsc-challenge-prioritization", "title": "Template for prioritizing DHSC challenges (Annex 3) - bottleneck scoring", "summary": "Rates each bottleneck 1-3 on impact, likelihood of overcoming it, and breadth of stakeholder importance, SUMS the scores and ranks by total. Same three criteria as DIIG Table 3.3.1 - and diig.md explicitly adopts the criteria but REFUSES the arithmetic. Adopting this annex as written would contradict an existing refusal; flagged for the owner.", "steps": [ { "n": 1, "name": "List bottlenecks/challenges" }, { "n": 2, "name": "Score impact on the process (1-3)" }, { "n": 3, "name": "Score likelihood of overcoming it (1-3)" }, { "n": 4, "name": "Score importance to a wide range of stakeholders (1-3)" }, { "n": 5, "name": "Add scores and rank (the step diig.md refuses)" } ], "status": "overlaps:smart-base/methodologies/diig.md", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-068", "pages": "68", "quote": "which receive scores of Low (1), Medium (2) or High (3) based on responses to three questions. Adding the scores yields the prioritized ranking." } ] }, { "id": "dth-npc-stepwise-approach", "title": "Stepwise approach to a national product catalogue (NPC) and product master data management (chapters 01-05)", "summary": "Regulation first (manufacturers are the source of truth), then data management and governance, technology (the NPC tool), change management, and human-resource capacity; chapters 06-07 offer the WHO-hosted PCMT and sharing to the WHO global catalogue as options. Steps \"might not always follow a linear order\". SOURCE DEFECT: chapter 04 is titled \"Creating protocols for managing change\" in the contents but \"Managing change to institutionalize standardized product master data\" in the body, and \"How to use this handbook\" numbers chapters 1-7 while the contents numbers 01-08.", "steps": [ { "n": 1, "name": "01 Establishing regulatory policies to promote product master data standardization", "detail": "Steps 1-4" }, { "n": 2, "name": "02 Instituting data management and governance policies", "detail": "Steps 1-5" }, { "n": 3, "name": "03 Deploying appropriate technology to manage product master data", "detail": "Steps 1-4" }, { "n": 4, "name": "04 Managing change to institutionalize standardized product master data", "detail": "Steps 1-2" }, { "n": 5, "name": "05 Building capacity to sustainably manage NPC", "detail": "Steps 1-3" }, { "n": 6, "name": "06 Leveraging the WHO-hosted PCMT (optional)" }, { "n": 7, "name": "07 Sharing product master data as a global good (optional)" } ], "status": "extends:smart-base/methodologies/diig.md", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-017", "pages": "17", "quote": "This handbook provides a stepwise approach to implementing standardized NPC and product master data management processes." }, { "libraryId": "9789240116191-eng", "sectionId": "page-012", "pages": "12", "quote": "It has been developed using the framework and approaches from the Digital implementation investment guide (DIIG)." }, { "libraryId": "9789240116191-eng", "sectionId": "page-025", "pages": "25", "quote": "It is important to note that the steps might not always follow a linear order and may be implemented simultaneously or concurrently." } ] }, { "id": "dth-smart-guidelines-knowledge-layers", "title": "SMART Guidelines five knowledge layers (L1-L5) as a stepwise pathway", "summary": "Each handbook frames SMART Guidelines as a step-by-step pathway of five progressive knowledge layers, each with a country adaptation/localisation step. Borderline as a \"methodology\" (it is a layering model); listed because the handbooks call it a pathway and each handbook declares which layer it contributes to (SC and PC: L1).", "steps": [ { "n": 1, "name": "L1 Narrative", "detail": "Enhanced guidelines and data recommendations" }, { "n": 2, "name": "L2 Operational", "detail": "Digital adaptation kits" }, { "n": 3, "name": "L3 Machine-readable", "detail": "Machine-readable recommendations" }, { "n": 4, "name": "L4 Executable", "detail": "Reference applications and services" }, { "n": 5, "name": "L5 Dynamic", "detail": "Precision health models" } ], "status": "overlaps:smart-base/skills/content/authoring-who-smart-guidelines/smart-stack-layering.md", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-016", "pages": "16", "quote": "The SMART Guidelines offer a step-by-step pathway that builds five progressive knowledge layers and associated products" }, { "libraryId": "9789240116191-eng", "sectionId": "page-014", "pages": "14", "quote": "following a five-step model that progressively increases in complexity" }, { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "This is knowledge layer 2, or L2, of the “SMART Guidelines” framework" } ] }, { "id": "ra-goals-to-dpih-mapping", "title": "Methodology: mapping health goals to DPI-H (goals-first, TOGAF-based)", "summary": "Top-down from seven priority health goals through stakeholder value, business capabilities, application services and application components, converging with a bottom-up pass from known DPI-H components. Every goal is articulated with the same four-part structure; detailed mappings are in Appendix E. Worked example: health financing yields one new component (Benefits Package Registry).", "steps": [ { "n": 1, "name": "State the goal as an outcome the health system is accountable for" }, { "n": 2, "name": "Describe what the health system should be able to do, in technology-neutral terms" }, { "n": 3, "name": "Map the required capabilities to DPI-H components and foundational-DPI dependencies" }, { "n": 4, "name": "Show how those components are reused across other goals" }, { "n": 5, "name": "Converge with the bottom-up pass from known DPI-H components and existing infrastructure" } ], "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-022-24-methodology-mapping-health-goals-to-dpi-h", "pages": "48-49", "quote": "The mapping was conducted using a TOGAF-based approach, working top-down from health" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-023-241-how-each-health-goal-is-articulated", "pages": "49-50", "quote": "Each of the seven priority health goals is articulated using the same structure" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-022-24-methodology-mapping-health-goals-to-dpi-h", "pages": "48-49", "quote": "mapping is the methodological backbone of the architecture, and it provides the consolidated" } ] }, { "id": "ra-archimate-architecture-description", "title": "Architecture description with a typed ArchiMate subset (elements, relationships, views)", "summary": "Express the architecture with a subset of ArchiMate element types (Stakeholder, Goal, Outcome, Value, Capability, Application component, Application service, Data object, Product) and relationships (Realises, Composes, Serves, Accesses; plus Assignment and Triggering for conformance), read through goal/capability, layered-realisation and motivation views; countries adopt, extend or set aside elements. Neighbour to the platform's BPMN/DMN methods, but no ArchiMate method exists here.", "steps": [ { "n": 1, "name": "Identify stakeholders, goals and outcomes (motivation)" }, { "n": 2, "name": "Decompose goals into capabilities" }, { "n": 3, "name": "Realise capabilities with application services and components; record data objects accessed" }, { "n": 4, "name": "Publish navigable views (goal/capability, layered, motivation) from one consistent model" }, { "n": 5, "name": "Tailor to country context: adjust, extend or set aside elements" } ], "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-025-31-the-architecture-description-approach", "pages": "52-59", "quote": "Rather than define a new vocabulary, the reference architecture is expressed using ArchiMate®," }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-025-31-the-architecture-description-approach", "pages": "52-59", "quote": "It is this network of typed relationships — not the elements in isolation — that allows the" } ] }, { "id": "ra-conformance-and-testing", "title": "Conformance and testing across architecture and components (Section 3.7)", "summary": "Conformance is declared per Application Component against the services of a named actor role (role-directional, one side of an interaction at a time, with a simulator for the other side); testing is planned from the architecture (standard components arrive tested via IHE, bespoke ones are tested by the adopter); progress is measured by three ratios; goals are validated through Outcomes; country adoption is measured by realisation mapping (adopt/adapt/map) yielding coverage and gaps.", "steps": [ { "n": 1, "name": "Model actors as Application Components and their offered/required services with mandatory/optional qualifiers" }, { "n": 2, "name": "Plan testing from the architecture: separate standard (reuse IHE tests) from bespoke (build tests)" }, { "n": 3, "name": "Test each component in its claimed role against a simulator (or via UI with a test operator)" }, { "n": 4, "name": "Measure requirements coverage, standards conformance and capability completeness" }, { "n": 5, "name": "Validate goals: criterion (Outcome) -> evaluating mechanism -> (implicit) verdict" }, { "n": 6, "name": "Evaluate adoption by mapping country elements to reference elements; compute coverage; surface gaps" } ], "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-048-372-the-model", "pages": "90-94", "quote": "Conformance is the assertion that a given Application Component correctly realises the" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-050-374-planning-testing-from-the-architecture", "pages": "95-96", "quote": "Three ratios are useful: requirements coverage" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-051-375-validating-goals-and-adoption", "pages": "96-97", "quote": "A country relates its architecture to the reference in one of three ways, and the mapping records" } ] }, { "id": "ra-phased-implementation-to-reddhi", "title": "Charting a path to REDDHI: four entry points and a four-phase implementation approach", "summary": "Identify the entry point (1 building from the ground up; 2 integrating existing systems; 3 upgrading existing infrastructure; 4 scaling and deepening), then follow broadly consistent, overlapping phases with governance, financing, partnership, capacity and evaluation running throughout. Explicitly complements the DIIG: DIIG guides the programme-level investment; this guides the shared infrastructure those investments reuse.", "steps": [ { "n": 1, "name": "Phase 1 - Assess, align, and plan", "detail": "National architecture assessment with baselines; governance body; stakeholders; 2-3 priority goals and use cases; procurement aligned to open standards; roadmap; early financing conversation." }, { "n": 2, "name": "Phase 2 - Establish the foundation", "detail": "Foundational shared data layer components the priority goals need; integration with foundational DPI; interoperability capability; connect 2-3 programme systems." }, { "n": 3, "name": "Phase 3 - Connect and expand", "detail": "More programme systems; semantic governance infrastructure; geographic/offline coverage; legacy transition; business services layer." }, { "n": 4, "name": "Phase 4 - Sustain and evolve", "detail": "Domestic financing; in-country EA capacity; financing models; partner alignment; continuous evolution." } ], "status": "extends:smart-base/methodologies/diig.md", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-057-421-different-entry-points-toward-reddhi", "pages": "100-101", "quote": "this guidance identifies four common entry points" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-058-422-a-phased-implementation-approach", "pages": "101-104", "quote": "Regardless of entry point, implementation follows a broadly consistent phased progression." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-058-422-a-phased-implementation-approach", "pages": "101-104", "quote": "This phased approach is consistent with, and complements, the WHO Digital Implementation" } ] }, { "id": "ra-navigating-legacy-systems", "title": "Navigating legacy systems (assess, integrate, replace at transition points, stop new silos)", "summary": "Four ordered principles for deciding what to preserve, integrate or retire; architectural conformance becomes a mandatory procurement requirement. Closely related to the PHC handbook's Chapter 6 phase-out of paper/legacy systems.", "steps": [ { "n": 1, "name": "Assess before you act" }, { "n": 2, "name": "Integrate before you replace" }, { "n": 3, "name": "Replace at natural transition points" }, { "n": 4, "name": "Stop creating new silos" } ], "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-059-423-navigating-legacy-systems", "pages": "104", "quote": "Legacy systems are not the enemy of DPI-H — unplanned legacy systems are." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-059-423-navigating-legacy-systems", "pages": "104", "quote": "Countries should treat architectural conformance as a mandatory procurement" } ] }, { "id": "ra-measuring-progress-and-impact", "title": "Measuring progress and impact (four dimensions, baselines, process evaluation)", "summary": "Capture outcome baselines at the starting-point assessment, pair outcome measurement with a process evaluation, and repeat a four-dimension assessment annually or biannually to adjust the roadmap and evidence the investment case.", "steps": [ { "n": 1, "name": "Component coverage" }, { "n": 2, "name": "Standards conformance" }, { "n": 3, "name": "Governance maturity" }, { "n": 4, "name": "Outcome linkage" } ], "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-070-442-tracking-progress-over-time", "pages": "110-111", "quote": "Four dimensions provide a practical summary:" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-069-441-assessing-impact-are-goals-being-achieved", "pages": "110", "quote": "Impact depends on baselines captured at the outset" } ] } ], "processes": [ { "id": "phc-understand-user-requirements", "title": "PHC Chapter 3 - Understand user requirements", "steps": [ { "n": "3.1", "name": "Follow key requirement-gathering methods" }, { "n": "3.2", "name": "Get to know the users (personas, use cases, user stories)" }, { "n": "3.3", "name": "Map business processes and workflows" }, { "n": "3.4", "name": "Streamline data collection and indicator reporting" }, { "n": "3.5", "name": "Create a data dictionary" }, { "n": "3.6", "name": "Determine decision-support logic" }, { "n": "3.7", "name": "Map health service schedules" }, { "n": "3.8", "name": "Gather and prioritize requirements" } ], "actors": [ "Targeted health worker occupational groups (e.g. physicians, nurses, midwives and community health workers), health service users and other intended end-users (guide the requirements)", "Business analysts, health informaticians and people trained in user research (lead)", "Software engineers (engaged)", "Public health authority (responsible, or at least consulted)" ], "inputs": [ "National health strategy, digital health strategy, health policies, and a strategic direction and scope for the PCPOSS", "Health information system, privacy, security and data use policies", "Digital health architecture blueprint and high-level requirements for meeting interoperability standards", "Infrastructure readiness assessment", "Unique identifier method", "List of anticipated outcomes against which to measure success", "WHO and national guidelines for the health area targeted, SOPs for care delivery, data and indicator definitions", "Existing paper records and register forms", "End user and key stakeholder interviews and insights", "Tools: Annex 3-13 templates; WHO Digital adaptation kits" ], "outputs": [ "Requirements documentation: user personas; use cases; user stories; as-is and to-be business processes; data dictionary and data model; documented health service schedule; documented decision logic algorithms; list of indicators and calculation method; prioritized functional and non-functional requirements" ], "status": "overlaps:smart-base/processes/l2-dak-authoring.bpmn", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-011-25-choices-for-software-and-digital-applications", "pages": "27-30", "quote": "Business analysts, health informaticians and people trained in user research should lead the process of gathering requirements" }, { "libraryId": "9789240093362-eng", "sectionId": "sec-019-38-gather-and-prioritize-requirements", "pages": "47-52", "quote": "After finishing the processes outlined in previous sections, there should be answers to all of the following questions." } ] }, { "id": "phc-business-process-workflow-mapping", "title": "PHC 3.3 - Map business processes and workflows (as-is / to-be, BPMN)", "steps": [ { "n": 1, "name": "Inventory business processes with a business process matrix (Annex 6): process name, ID, personas, objectives, task set, start/end point" }, { "n": 2, "name": "Map as-is workflows in BPMN 2.0 - what actually happens, not what should happen" }, { "n": 3, "name": "Label each process with a process ID and each activity with an activity ID, consistently" }, { "n": 4, "name": "Annotate activities (forms, time required, non-digitizable activities, guideline references)" }, { "n": 5, "name": "As-is analysis: label data-collection points, bottlenecks, redundancies, pain points" }, { "n": 6, "name": "Map to-be workflows: eliminate redundant tasks and unnecessary data, reduce bottlenecks, consolidate, link data, integrate along care pathways" }, { "n": 7, "name": "Gain consensus among key stakeholder groups on the to-be workflows" } ], "actors": [ "Requirements-gathering / implementation team", "Health worker occupational groups (swim lanes)", "Health service users (swim lane)", "Key stakeholder groups (consensus)" ], "inputs": [ "Desk reviews, interviews and service-delivery observations", "Reference business processes and workflows from WHO DAKs", "Standard workflow guidelines (for to-be)" ], "outputs": [ "Inventory of business processes", "As-is workflows with data-collection points, bottlenecks and redundancies labelled", "To-be workflows labelling where the PCPOSS facilitates or replaces tasks" ], "status": "overlaps:smart-base/processes/l2-dak-authoring.bpmn", "notes": "The handbook also prescribes BPMN drawing rules (e.g. at most two outputs from an exclusive gateway, otherwise use a business-rule activity; one end event per lane) that should be checked against cat-harness/skills/process/workflow/bpmn-authoring.md before adoption.", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-014-33-map-business-processes-and-workflows", "pages": "35-39", "quote": "Prior to mapping and creating these workflows, it is recommended that a full inventory of the business processes that will be involved with the PCPOSS is taken." }, { "libraryId": "9789240093362-eng", "sectionId": "sec-014-33-map-business-processes-and-workflows", "pages": "35-39", "quote": "As-is workflows should depict what actually happens, not what should happen." }, { "libraryId": "9789240093362-eng", "sectionId": "sec-014-33-map-business-processes-and-workflows", "pages": "35-39", "quote": "There should only be two different outputs that originate from the decision point." } ] }, { "id": "phc-streamline-data-and-data-dictionary", "title": "PHC 3.4-3.5 - Streamline data collection and indicator reporting into a data dictionary", "steps": [ { "n": 1, "name": "Create an inventory of paper forms (Annex 7)" }, { "n": 2, "name": "Map data elements across all forms (Annex 8)" }, { "n": 3, "name": "Compile aggregate indicators (Annex 9)" }, { "n": 4, "name": "Remove duplicated, orphaned and non-essential data (Fig. 12 questions)" }, { "n": 5, "name": "Streamline into a consolidated data dictionary (database-design and/or UI-design dictionary)" }, { "n": 6, "name": "Map data elements to standardized classifications and terminologies (ICD-11, LOINC, WHO-FIC), via spreadsheet or terminology service" } ], "actors": [ "Implementation team", "Public health authority (authoritative list of forms)", "In-country programme manager (indicator cross-check)", "Health informaticians (terminology mapping)", "Targeted health worker occupational group" ], "inputs": [ "Data collection instruments and registers the health worker is responsible for", "National/global guidance or prior implementations listing data to collect (allows skipping steps 1-2)", "DAK data dictionaries" ], "outputs": [ "Forms inventory", "Form data mapping spreadsheet", "Aggregate indicator list with calculation method", "Clean data dictionary mapped to standard terminologies" ], "status": "overlaps:smart-base/processes/l2-dak-authoring.bpmn", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-015-34-streamline-data-collection-and-indicator-repo", "pages": "39-42", "quote": "The following are the five key steps needed to complete the streamlining." }, { "libraryId": "9789240093362-eng", "sectionId": "sec-016-35-create-a-data-dictionary", "pages": "42-44", "quote": "Engaging individuals with expertise in health informatics, classifications and terminologies in order to map data elements to standardized concepts is highly recommended." } ] }, { "id": "phc-decision-support-logic-and-schedules", "title": "PHC 3.6-3.7 - Determine decision-support logic and map health service schedules", "steps": [ { "n": 1, "name": "Identify the clinical protocol for the target occupational group (WHO / national authority)" }, { "n": 2, "name": "Start from DAK decision logic where it exists; adapt thresholds/triggers" }, { "n": 3, "name": "Inventory decisions in a decision-support logic matrix (Annex 10)" }, { "n": 4, "name": "Depict the sequence of decisions as decision trees" }, { "n": 5, "name": "Detail each decision as a decision-support table (Annex 11; DMN)" }, { "n": 6, "name": "Have clinical experts agree any changes or additions" }, { "n": 7, "name": "Map service schedules per service (and per occupational group where they differ): trigger events, intervals, follow-up actions, stop conditions, deviations (Annex 12)" } ], "actors": [ "Clinical experts", "Health worker occupational groups", "Engineers (translate logic into code and a rules engine)", "Local public health authority (approves schedules)" ], "inputs": [ "WHO and national clinical guidelines and protocols", "DAK decision-support tables and schedule logic tables", "Workflows from 3.3" ], "outputs": [ "Decision-support logic matrix", "Decision trees", "Decision-support tables", "Service schedule spreadsheets" ], "status": "overlaps:smart-base/processes/l2-dak-authoring.bpmn", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-017-36-determine-decision-support-logic", "pages": "44-47", "quote": "Decision-support tables include a decision ID, business rule, trigger, inputs, output, action and annotations." }, { "libraryId": "9789240093362-eng", "sectionId": "sec-018-37-map-health-service-schedules", "pages": "47", "quote": "For each health service, a service schedule spreadsheet should be created to map the key events and dates." } ] }, { "id": "phc-gather-and-prioritize-requirements", "title": "PHC 3.8 - Gather and prioritize functional and non-functional requirements", "steps": [ { "n": 1, "name": "Checkpoint: confirm users, wants, workflow fit, guidelines, data volume and logic are understood" }, { "n": 2, "name": "Translate the \"I want to...\" part of user stories into functional requirements" }, { "n": 3, "name": "Derive further requirements from workflows and the data dictionary" }, { "n": 4, "name": "Gather non-functional requirements from user and context constraints" }, { "n": 5, "name": "Build a long list and group it into high, medium and low priority (e.g. systematic voting)" }, { "n": 6, "name": "Check against the eight IEEE characteristics of good requirements; record in Annex 13" } ], "actors": [ "End-users and key stakeholders (prioritization voting)", "Implementation team", "Engineers" ], "inputs": [ "Use cases and user stories (3.2)", "Workflows (3.3)", "Data dictionary (3.4-3.5)", "Decision logic and schedules (3.6-3.7)", "DAK functional/non-functional requirements where available" ], "outputs": [ "Prioritized functional and non-functional requirements" ], "status": "overlaps:cat-harness/processes/crdm-requirements-definition.bpmn", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-019-38-gather-and-prioritize-requirements", "pages": "47-52", "quote": "Once a long list of requirements has been gathered, they can be put into groups of high, medium and low priority." }, { "libraryId": "9789240093362-eng", "sectionId": "sec-019-38-gather-and-prioritize-requirements", "pages": "47-52", "quote": "One way to translate user stories into functional and non-functional requirements is to look at the “I want to…” part" } ] }, { "id": "phc-design-and-adaptation", "title": "PHC Chapter 4 - Undertake design and adaptation", "steps": [ { "n": "4.1", "name": "Finalize software and vendor selection (landscape analysis, scorecard, checklist: pre-evaluation, features, ownership and costs, vendor evaluation)" }, { "n": "4.2", "name": "Validate functional requirements with key stakeholders (incrementally)" }, { "n": "4.3", "name": "Develop and test prototype design" }, { "n": "4.4", "name": "Design system architecture (within the EA; TOGAF domains; interoperability and standards)" }, { "n": "4.5", "name": "Build and quality assurance (agile; test plan; installation, stress, security, GUI, integration, QA, accessibility testing)" } ], "actors": [ "Software engineers and solutions architects (lead)", "Business analysts and designers", "Health informaticians", "Targeted health worker occupational groups and end-users (feedback)", "Technology partner" ], "inputs": [ "Scope for PCPOSS", "Project team governance structure", "Budget, timeline, and risk and mitigations plan", "Digital adaptation kits (if available)", "Requirements documentation (personas, use cases, user stories, as-is/to-be processes, data dictionary, data model, decision logic, service schedule, prioritized requirements)" ], "outputs": [ "Selected software and software vendor", "System architecture", "User interface design", "Product documentation", "Beta version of the PCPOSS" ], "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-019-38-gather-and-prioritize-requirements", "pages": "47-52", "quote": "The steps of undertaking detailed design and adaptation should be led primarily by a technology partner." }, { "libraryId": "9789240093362-eng", "sectionId": "sec-024-45-build-and-quality-assurance", "pages": "60-64", "quote": "A test plan must be established as soon as the requirements are finalized." } ] }, { "id": "phc-prototype-design-and-testing", "title": "PHC 4.3 - Develop and test the prototype design", "steps": [ { "n": 0, "name": "Develop the design: sketches -> wireframes -> mock-ups -> higher-fidelity (clickable) prototypes" }, { "n": 1, "name": "Design testing use cases (from 3.2 use cases and user stories)" }, { "n": 2, "name": "Create multiple mock-ups or prototypes" }, { "n": 3, "name": "Validate mock-ups or prototypes with targeted end-users (role play, interviews, focus groups)" }, { "n": 4, "name": "Document feedback (structured feedback template)" }, { "n": 5, "name": "Incorporate feedback after stakeholder vetting; record decisions not to incorporate" } ], "actors": [ "Designer", "Targeted end-users", "Key stakeholders (vet feedback)", "Technical team" ], "inputs": [ "Use cases and user stories (3.2)", "User personas" ], "outputs": [ "Validated mock-ups / prototypes", "Structured feedback record and incorporation decisions" ], "status": "overlaps:cat-harness/processes/wireframe-design-review.bpmn", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-022-43-develop-and-test-prototype-design", "pages": "53-56", "quote": "The goal is to start with low-fidelity artefacts that can elicit user feedback quickly and then slowly move on to higher fidelity prototypes" }, { "libraryId": "9789240093362-eng", "sectionId": "sec-022-43-develop-and-test-prototype-design", "pages": "53-56", "quote": "Feedback should be discussed and vetted by key stakeholders before it is incorporated." } ] }, { "id": "phc-training-testing-rollout", "title": "PHC Chapter 5 - Conduct training, testing and roll-out", "steps": [ { "n": "5.1", "name": "Develop and conduct training (on use incl. training of trainers; on maintenance for local technology partners); pilot the curriculum at small scale" }, { "n": "5.2", "name": "Test user acceptance and deployment readiness (UAT with trained small group; test cases and test data incl. edge cases)" }, { "n": "5.3", "name": "Deploy the system to a production environment" }, { "n": "5.4", "name": "Manage feedback and system maintenance (feedback SOP; M&E of impact)" } ], "actors": [ "Implementing teams (training, interfacing with end-users)", "Software engineers (act on feedback)", "Public health authority (change management, policies)", "End-users (feedback, use)", "Local technology partner(s) (maintenance)" ], "inputs": [ "Beta version of the PCPOSS", "Tools: testing checklist" ], "outputs": [ "Training materials", "A deployed and rolled-out PCPOSS" ], "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-026-52-test-user-acceptance-and-deployment-readiness", "pages": "64-65", "quote": "User acceptance testing (UAT) should be conducted by the core project team with a small group of trusted advisers and end-users." }, { "libraryId": "9789240093362-eng", "sectionId": "sec-028-54-manage-feedback-and-system-maintenance", "pages": "65-68", "quote": "The implementation team should have a standard operating procedure for managing all this feedback." } ] }, { "id": "phc-deploy-the-system", "title": "PHC 5.3 - Deploy the system (ad hoc set of roll-out activities)", "steps": [ { "n": 1, "name": "Install infrastructure at roll-out sites" }, { "n": 2, "name": "Determine hardware delivery logistics" }, { "n": 3, "name": "Install the software on selected hardware" }, { "n": 4, "name": "Migrate data from the old system" }, { "n": 5, "name": "Load configuration data" }, { "n": 6, "name": "Set up facility and health worker data and accounts" }, { "n": 7, "name": "Test infrastructure and hardware at each site" }, { "n": 8, "name": "Schedule deployment with health workers / facility manager" }, { "n": 9, "name": "Implement feedback management processes" }, { "n": 10, "name": "Deploy the software system" } ], "actors": [ "Technology partner (leads)", "Health workers", "Health facility manager" ], "inputs": [ "System that has passed all testing including UAT", "Earlier needs assessments (infrastructure)" ], "outputs": [ "System deployed in the production environment" ], "status": "new", "notes": "The handbook states these are \"not in any particular order\" - a BPMN ad hoc sub-process, not a sequence.", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-027-53-deploy-the-system", "pages": "65", "quote": "Some common steps, not in any particular order, include:" }, { "libraryId": "9789240093362-eng", "sectionId": "sec-027-53-deploy-the-system", "pages": "65", "quote": "This deployment and roll-out phase should be led by the technology partner" } ] }, { "id": "phc-prepare-for-scale-up", "title": "PHC Chapter 6 - Prepare for scale-up and phase out paper/legacy systems", "steps": [ { "n": "6.1", "name": "Determine readiness for scaling up (PCPOSS and health system)" }, { "n": "6.2", "name": "Plan for phase-out: SMART objectives and indicators (Table 5); downtime SOPs; keep paper backup" }, { "n": "6.3", "name": "Monitor and evaluate progress on objectives" }, { "n": "6.4", "name": "Phase out legacy systems in a staged, region-by-region manner" }, { "n": "6.5", "name": "Adopt change management practices" } ], "actors": [ "Leading public health authority, e.g. ministry of health (leads)", "Implementing teams", "Monitoring and evaluation specialists", "Technology partners", "End-users" ], "inputs": [ "Live version of the PCPOSS being used", "Tools: Monitoring and evaluating digital health interventions; the MAPS toolkit" ], "outputs": [ "Set of objectives and benchmarks the PCPOSS must meet before phasing out paper and/or legacy systems", "Strategic plan for phasing out paper and/or legacy systems" ], "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-030-62-plan-for-phase-out-of-legacy-systems", "pages": "68-71", "quote": "The objectives for the PCPOSS should be specific, measurable, attainable, relevant and time-bound (or SMART for short)" }, { "libraryId": "9789240093362-eng", "sectionId": "sec-032-64-phase-out-of-legacy-systems", "pages": "71", "quote": "it is advised to not wait until the entire country is ready to phase out paper systems and/or legacy systems" } ] }, { "id": "dhsc-define-strategy", "title": "DHSC Chapter 1 - Define a holistic DHSC strategy", "steps": [ { "n": 1, "name": "Identify and engage all relevant stakeholders", "inputs": [ "National health strategy and priorities", "Organograms of MOH, regulatory authority, central warehouse" ], "tasks": [ "Identify focal points from all stakeholder organizations", "Identify relevant managerial and technical staff", "Define a stakeholder matrix", "Establish a TWG and a steering committee" ], "outputs": [ "DHSC stakeholder matrix", "DHSC steering committee terms of reference", "DHSC TWG terms of reference" ] }, { "n": 2, "name": "Analyse the current state of HSCISs", "inputs": [ "National health strategy and priorities", "National health supply chain assessments", "Identified improvements", "Details on national supply chain, digital health and traceability systems", "Supply chain improvements and digital achievements" ], "tasks": [ "Identify challenges, problems and digitalization needs (incl. end-user perspectives)", "Prioritize them within a defined time frame" ], "outputs": [ "Health supply chain digital transformation priorities" ] }, { "n": 3, "name": "Define the DHSC vision and strategic goals and objectives", "inputs": [ "National supply chain, health, digital health, medicines/health product and IT strategies", "Digital transformation priorities" ], "tasks": [ "Identify solutions", "Define strategic goals", "Define strategic objectives", "Define the overarching DHSC vision" ], "outputs": [ "DHSC transformation vision", "DHSC strategic goals", "DHSC strategic objectives" ] }, { "n": 4, "name": "Define a strategic roadmap and performance indicators", "inputs": [ "DHSC strategic goals", "DHSC strategic objectives", "Timelines of other initiatives" ], "tasks": [ "Define a strategic roadmap", "Define performance indicators for all strategic objectives" ], "outputs": [ "DHSC strategic roadmap", "Performance indicators" ] } ], "actors": [ "Ministry of health (leads)", "Focal points from MOH, regulatory authority, IT authority, central and regional warehouses, health facilities, implementation partners and funders", "Technical working group (TWG)", "Steering committee", "DHSC sponsor (senior MOH leader)", "Senior management/leaders; chief digital officers; supply chain leaders" ], "inputs": [ "National health strategy and priorities", "Organograms", "National supply chain assessments (e.g. NSCA)", "National strategies (supply chain, digital health, IT, medicines)" ], "outputs": [ "DHSC vision", "DHSC strategic goals", "DHSC strategic objectives", "DHSC strategic roadmap" ], "status": "new", "notes": "Stakeholder matrix / steering-committee roles touch cat-harness/methodologies/raci.md.", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-022", "pages": "22", "quote": "Define a stakeholder matrix to clearly establish roles and responsibilities." }, { "libraryId": "9789240101197-eng", "sectionId": "page-025", "pages": "25", "quote": "Define performance indicators for all strategic objectives, to measure progress and effectiveness." }, { "libraryId": "9789240101197-eng", "sectionId": "page-019", "pages": "19", "quote": "The steps outlined in this chapter will result in the following outputs:" } ] }, { "id": "dhsc-define-architecture", "title": "DHSC Chapter 2 - Define the DHSC architecture", "steps": [ { "n": 1, "name": "Assess the current state of HSCISs", "inputs": [ "NSCA outcomes", "SCISMM assessment outcomes", "DHSC strategic goals and objectives", "National digital health strategy", "Landscape analysis of hardware, infrastructure, software and master data management" ], "tasks": [ "List existing HSCISs and map them to services", "Conduct SCISMM assessment (if not done)", "Analyse SCISMM outputs to identify gaps" ], "outputs": [ "List of existing HSCISs", "SCISMM assessment report", "HSCIS gaps to address" ] }, { "n": 2, "name": "Define a target DHSC architecture", "inputs": [ "Supply chain assessment", "List of existing HSCISs", "SCISMM assessment report", "HSCIS gaps" ], "tasks": [ "Draw the current-state architecture against the DHSC architecture framework", "Identify gaps and necessary digital interventions", "Define the future state" ], "outputs": [ "Current-state architecture of health supply chain systems", "Future state of the DHSC architecture" ] }, { "n": 3, "name": "Identify implementation activities and map them to strategic goals", "inputs": [ "Current state of HSCISs", "Future-state DHSC architecture", "DHSC strategic goals" ], "tasks": [ "Prioritize DHSC interventions based on strategic goals", "Define implementation activities", "Develop a high-level roadmap" ], "outputs": [ "List of DHSC implementation activities mapped to strategic goals", "High-level roadmap of DHSC implementations" ] } ], "actors": [ "Ministry of health", "Central warehouse", "Chief digital officers", "Technical/system/enterprise architects", "TWG (oversight of solution choices)" ], "inputs": [ "Outputs of Chapter 1 (strategic goals and objectives)", "NSCA / SCISMM assessments" ], "outputs": [ "Current state of HSCISs", "Future-state DHSC architecture", "Implementation activities mapped to strategic goals", "High-level roadmap" ], "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-032", "pages": "32", "quote": "Draw the current-state architecture of the HSCISs by mapping existing systems against the DHSC architecture framework." }, { "libraryId": "9789240101197-eng", "sectionId": "page-042", "pages": "42", "quote": "Prioritize DHSC interventions based on strategic goals." } ] }, { "id": "dhsc-implement-interventions", "title": "DHSC Chapter 3 - Plan, budget and implement each DHSC intervention", "steps": [ { "n": 1, "name": "Plan the implementation of each DHSC intervention", "inputs": [ "Prioritized DHSC interventions", "List of DHSC implementation activities" ], "tasks": [ "Develop a project charter", "Develop a project management plan", "Establish project governance and reporting via steering committee/TWG", "Define the project performance monitoring and analysis framework" ], "outputs": [ "Project charter", "Project management plan", "Steering committee and TWG terms of reference", "Project performance monitoring and analysis framework" ] }, { "n": 2, "name": "Develop an operational plan for each DHSC intervention", "inputs": [ "List of DHSC implementation activities", "DHSC stakeholder matrix" ], "tasks": [ "Update the stakeholder matrix (system owner/custodian, users)", "Identify operational resources", "Develop an operations and sustainability plan", "Develop an operational performance M&E framework" ], "outputs": [ "Updated stakeholder matrix", "Operations and sustainability plan", "Operational performance M&E framework" ] }, { "n": 3, "name": "Develop a budget for each DHSC intervention", "inputs": [ "Project management plan", "Operations and sustainability plan", "Historical budgets and costs" ], "tasks": [ "Identify cost drivers", "Determine implementation costs", "Determine operational costs over 5-10 years", "Develop a budget matrix", "Identify funding sources and needs" ], "outputs": [ "Total cost of ownership", "Budget matrix", "Funding needs" ] }, { "n": 4, "name": "Implement each DHSC intervention", "inputs": [ "Prioritized DHSC interventions", "List of DHSC implementation activities" ], "tasks": [ "Define functional and nonfunctional requirements", "Identify vendor via RFP/RFQ", "Develop solution design and integration specifications", "Develop and/or configure", "Integrate via an interoperability platform", "Validate through system, integration and UAT", "Train the users", "Roll out" ], "outputs": [ "Requirements", "Sourcing documents", "Contracts", "Solution design and integration specifications", "DHSC application components", "Test scripts", "User training materials", "Application issues log" ] } ], "actors": [ "Ministry of health", "Central warehouse", "Donors and funding partners", "Implementing partners", "Chief digital officers", "Project sponsors", "Project managers", "Technical/system/enterprise architects", "Supply chain/operational leaders", "Steering committee and TWG", "Implementation partner/vendor", "Annex 7 roles (CTO/CIO/CDO, solution architect, integration specialist, QA/test manager, support engineer, superuser/trainer, ...)" ], "inputs": [ "Prioritized DHSC interventions", "List of DHSC implementation activities" ], "outputs": [ "Project management plans", "Stakeholder matrix for operations", "Operations sustainability plan", "Implementation and operations M&E framework", "Implementation materials (requirements, specifications, test scripts, job aids)", "Developed DHSC applications" ], "status": "overlaps:smart-base/methodologies/diig.md", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-047", "pages": "47", "quote": "Establish a project governance and reporting mechanism through the steering committee and/or TWG." }, { "libraryId": "9789240101197-eng", "sectionId": "page-051", "pages": "51", "quote": "Validate the intervention through system, integration and user acceptance testing." }, { "libraryId": "9789240101197-eng", "sectionId": "page-049", "pages": "49", "quote": "Determine all operational costs for the life of the DHSC intervention, which could typically be five to 10 years." } ] }, { "id": "dhsc-traceability-event-flow", "title": "DHSC Chapter 4 - Track, trace and verify a health product (centralized traceability model)", "steps": [ { "n": 1, "name": "Manufacturer identifies and marks the product with global standards and shares traceability data" }, { "n": 2, "name": "Ship event recorded" }, { "n": 3, "name": "Central/regional warehouse verifies and receives" }, { "n": 4, "name": "Warehouse ships" }, { "n": 5, "name": "Health facility verifies and receives" }, { "n": 6, "name": "Health facility verifies and dispenses to the patient" }, { "n": 7, "name": "Each event (what / when / where / why) is aggregated in the repository via the interoperability layer" }, { "n": 8, "name": "Traceability services answer track, trace and verification queries" } ], "actors": [ "Manufacturer", "Central, regional and district warehouses", "Health facilities", "Patients", "Regulator" ], "inputs": [ "Globally unique product and facility identifiers in a data carrier (barcode)", "Supplier/product/facility master data", "Transactional and event data from HSCISs" ], "outputs": [ "Track and trace results", "Product verification" ], "status": "new", "notes": "The handbook recommends no traceability model; it illustrates the centralized one.", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-055", "pages": "55", "quote": "What: product identifier, batch no., serial no. When: date and time of the event Where: location of the event" }, { "libraryId": "9789240101197-eng", "sectionId": "page-056", "pages": "56", "quote": "sharing data across all stakeholders of the supply chain creates an information flow that precedes the physical flow of the product." } ] }, { "id": "npc-01-regulatory-policies", "title": "NPC 01 - Establish regulatory policies to promote product master data standardization", "steps": [ { "n": 1, "name": "Identify necessary regulatory policies and legislations", "inputs": [ "Existing regulatory policies and legislations" ], "tasks": [ "Analyse current regulations against internationally accepted standards", "Check compliance mechanisms", "Identify additions and updates needed" ], "outputs": [ "List of additional regulatory policies and legislations required", "List of modifications needed for existing policies and legislations" ] }, { "n": 2, "name": "Develop the identified regulatory policies and legislations", "tasks": [ "Develop policies such as master data guidelines (consistent with data standardization and AIDC regulation)", "Outline phased roll-out timelines", "Update existing policies if necessary" ], "outputs": [ "Master data related policies and legislations" ] }, { "n": 3, "name": "Coordinate reviews and approvals of the drafted policies", "tasks": [ "NRA-led evaluation with MOH, warehouses, procurement entities, manufacturers, distributors, operational leaders", "Address feedback", "Obtain approvals for publishing" ], "outputs": [ "Approved master data policies and legislations" ] }, { "n": 4, "name": "Publish and enforce the approved regulatory policies", "tasks": [ "Publish the policy document", "Define mechanisms to institutionalize and monitor compliance" ], "outputs": [ "Endorsed master data policies and legislations" ] } ], "actors": [ "Ministry of Health", "National Regulatory Authority (leads evaluation)", "Senior management/leaders", "Regulatory staff", "Manufacturers and distributors", "Funding organizations and implementation partners" ], "inputs": [ "Existing regulatory policies and legislations", "Master data guideline template", "Product identification and labelling guidance and template" ], "outputs": [ "Regulatory policies and legislations such as master data guidelines for product master data" ], "status": "new", "notes": "Mitigation names a Responsibility Assignment Matrix (RACI): cf. cat-harness/methodologies/raci.md.", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-021", "pages": "21", "quote": "Analyse current regulations to determine if they clearly articulate policies for product master data standardization and sharing, in alignment with internationally accepted standards." }, { "libraryId": "9789240116191-eng", "sectionId": "page-023", "pages": "23", "quote": "Define mechanisms to institutionalize and monitor compliance of the policies" } ] }, { "id": "npc-02-data-management-governance", "title": "NPC 02 - Institute data management and governance policies", "steps": [ { "n": 1, "name": "Define product master data management procedures", "outputs": [ "Data harmonization activities plan", "Master data management procedures incl. governance policies", "TOR for master data governance group" ] }, { "n": 2, "name": "Define coding scheme, data definitions and structures", "tasks": [ "Harmonize coding schemes, definitions, structures", "Map country identifiers to HL7 FHIR, IDMP, GS1 GTIN", "Review with stakeholders and approve" ], "outputs": [ "Standardized master data coding schemes and structures", "Updated master data management procedures" ] }, { "n": 3, "name": "Define data use policies and data sharing mechanisms", "outputs": [ "Data sharing and data use policies" ] }, { "n": 4, "name": "Institutionalise product master data governance policies and procedures", "tasks": [ "Establish a master data governance group", "Promote consistent use across processes, systems and organizations" ], "outputs": [ "Master data governance group established", "Procedures integrated in operations" ] }, { "n": 5, "name": "Define short- and long-term strategies to source standardized product master data", "outputs": [ "Short-term and long-term sourcing strategies" ] } ], "actors": [ "Ministry of Health", "NRA", "Central Medical Stores", "Funders and implementation partners", "Senior management", "Regulatory staff", "Data officers and data management staff", "Data owner, data custodian, data steward", "Master data governance group", "Manufacturers and distributors (data sources)" ], "inputs": [ "Published master data policies and legislations (from 01)" ], "outputs": [ "Master data management procedures incl. governance policies", "TOR for the master data governance group", "Standardized master data coding schemes and structures", "Data harmonization activity plan", "Data sharing and data use policies", "Short-term and long-term strategies for sourcing master data" ], "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-025", "pages": "25", "quote": "Develop a set of data management procedures* to continuously and securely maintain master data." }, { "libraryId": "9789240116191-eng", "sectionId": "page-032", "pages": "32", "quote": "Establish a master data governance group composed of all relevant stakeholders to provide leadership and guidance in managing product master data additions and changes." } ] }, { "id": "npc-03-deploy-technology", "title": "NPC 03 - Deploy appropriate technology to manage product master data", "steps": [ { "n": 1, "name": "Define system requirements for the NPC tool", "outputs": [ "Approved functional and non-functional system requirements for NPC" ] }, { "n": 2, "name": "Identify technology options and select the appropriate tool", "tasks": [ "RFI market research", "Assess existing tools (e.g. ERP)", "Consider open-source PCMT / WHO-hosted PCMT", "RFQ/RFP if needed" ], "outputs": [ "Selection of an appropriate technology tool for NPC" ] }, { "n": 3, "name": "Prepare a plan to implement the NPC tool and integrate with other systems", "outputs": [ "NPC implementation project plan" ] }, { "n": 4, "name": "Design, develop and deploy the NPC tool", "tasks": [ "Design and configure; approvals", "Develop and integrate", "System, integration, performance testing and UAT", "Infrastructure setup", "Deploy, load master data, roll out" ], "outputs": [ "NPC system design and configuration specifications", "NPC system validation report", "Deployed NPC tool" ] } ], "actors": [ "Ministry of Health", "NRA", "Donors and funding partners", "Implementation partners", "Chief digital officers", "Project sponsors and managers", "Technical/system/enterprise architects", "Supply chain/operational leaders" ], "inputs": [ "Standardized master data coding schemes and structures", "Master data management procedures", "Data sharing and data use policies", "Resources: NPC system requirements, TSS v2, ISO IDMP, HL7 FHIR IGs" ], "outputs": [ "Approved functional and non-functional system requirements for NPC", "NPC implementation plan", "NPC tool deployed" ], "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-036", "pages": "36", "quote": "Conduct market research activities such as Request for information (RFI) to explore technology options for an appropriate tool for NPC." }, { "libraryId": "9789240116191-eng", "sectionId": "page-037", "pages": "37", "quote": "Deploy the validated NPC tool, load the available product master data and roll out." } ] }, { "id": "npc-04-manage-change", "title": "NPC 04 - Manage change to institutionalize standardized product master data", "steps": [ { "n": 1, "name": "Develop a change management plan to institutionalise use of NPC", "tasks": [ "Identify systems and processes needing standardized product master data", "Define process changes, system enhancements, data structure/model changes, data exchange mechanisms and event triggers" ], "outputs": [ "Change management plan for all systems and processes to use NPC" ] }, { "n": 2, "name": "Define SOPs to collect, organize and manage product master data", "tasks": [ "Define SOPs incl. approval workflows in the NPC", "Validate SOPs against NPC workflows", "Approve SOPs", "Define continuous training and advocacy plan", "Train users" ], "outputs": [ "Product master data management SOPs", "Continuous training plan" ] } ], "actors": [ "Ministry of Health", "NRA", "Central Medical Stores", "Donors and funding partners", "Implementation partners", "Project managers", "Data management staff", "Regulatory/monitoring/pharmacovigilance teams", "NPC users" ], "inputs": [ "Standardized master data coding schemes and structures", "Master data management procedures", "Data sharing and data use policies" ], "outputs": [ "Change management plan", "Product master data management SOPs", "Continuous training plan" ], "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-039", "pages": "39", "quote": "Identify all the systems and processes that need standardized product master data." }, { "libraryId": "9789240116191-eng", "sectionId": "page-040", "pages": "40", "quote": "Define SOPs to collect, organize, add, update master data, and manage data approval workflows within the NPC." } ] }, { "id": "npc-05-build-capacity", "title": "NPC 05 - Build capacity to sustainably manage the NPC", "steps": [ { "n": 1, "name": "Identify human resource capacity needs to support NPC", "outputs": [ "List of roles", "Job descriptions", "Human resource management plan" ] }, { "n": 2, "name": "Onboard and assign individuals to the identified roles", "outputs": [ "Budget for human resource capacity needs", "Onboarded resources" ] }, { "n": 3, "name": "Develop knowledge management plan to enhance skills and capacity", "outputs": [ "Organogram for product master data management", "Knowledge management plan for master data and NPC", "Governmental strategy to engage and enable local technical capacity" ] } ], "actors": [ "Ministry of Health", "NRA", "Central Medical Stores", "Donors and funding partners", "Implementation partners", "Senior management", "Chief digital officers", "Catalogue manager", "NPC system administrator", "Local vendors and implementation partners" ], "inputs": [ "TOR for the master data governance group", "Master data management procedures", "SOPs for product master data management" ], "outputs": [ "Roles and job descriptions", "Human resource management plan", "Organogram", "Knowledge management plan", "Governmental strategy for local technical capacity" ], "status": "new", "notes": "SOURCE DEFECT: the Step 3 table repeats Step 2's budgeting/recruitment rows before its own knowledge-management row.", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-043", "pages": "43", "quote": "Identify each operational and technical role needed (e.g., Catalogue Manager, NPC System Administrator)." }, { "libraryId": "9789240116191-eng", "sectionId": "page-044", "pages": "44", "quote": "Develop strategies to expand human resource capacity by engaging and enabling local vendors and implementation partners." } ] }, { "id": "ra-national-architecture-assessment", "title": "RA 4.1 - National digital health architecture assessment -> roadmap", "steps": [ { "n": 1, "name": "What do we already have? Inventory all HIS, registries and tools, incl. partner/programme-funded ones; assess alignment with REDDHI, openness, coverage, ownership" }, { "n": 2, "name": "What is the state of our foundational DPI? Identity, payments, data exchange reach and health use-case support" }, { "n": 3, "name": "What are our governance and institutional conditions? Legal framework, institutional home, procurement alignment, government capacity" }, { "n": 4, "name": "What are our priority health goals? Two to three goals and their high-value use cases" }, { "n": 5, "name": "Produce the national digital health architecture roadmap (current state, target, gap, sequenced investments), with benefits case, logic model and baselines" } ], "actors": [ "Ministries and agencies governing the national effort", "Architects and modellers", "Development partners" ], "inputs": [ "Existing systems landscape", "Foundational DPI status", "Legal/regulatory and institutional context", "Seven priority health goals", "Digital-readiness / capability assessment frameworks" ], "outputs": [ "National digital health architecture roadmap", "Benefits case and logic model", "Baseline values for outcomes" ], "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-055-412-assessing-where-you-are", "pages": "99-100", "quote": "A national digital health architecture assessment should answer four questions." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-055-412-assessing-where-you-are", "pages": "99-100", "quote": "The outputs of this assessment form the foundation of a national digital health architecture" } ] }, { "id": "ra-semantic-governance-content-lifecycle", "title": "RA 3.4.5 - Semantic Governance Infrastructure: governed content lifecycle", "steps": [ { "n": 1, "name": "Intake: register change requests, ingest upstream releases, handle deprecation notices; triage into an auditable queue" }, { "n": 2, "name": "Authoring and publication: review, approve, version and release under business rules, with audit trail and provenance" }, { "n": 3, "name": "Distribution: access-controlled delivery across consumption modalities" }, { "n": 4, "name": "Consumption: implementers discover, retrieve and integrate content; field feedback captured" }, { "n": 5, "name": "Monitoring: (a) publication process and content quality; (b) field use and adoption - feeds the next cycle" } ], "actors": [ "Stakeholders submitting change requests", "Reviewers/approvers (committees with decision rights)", "Maintainers of national extensions", "Standards development organisations (upstream)", "Terminology and semantic specialists", "Consuming systems and implementers" ], "inputs": [ "Change requests", "Upstream standard releases", "Deprecation notices", "Field feedback" ], "outputs": [ "Published, versioned terminologies, value sets and information models", "Monitoring of conformance and adoption" ], "status": "overlaps:fhir-harness/skills/content/fhir-ig-authoring/terminology-management.md", "notes": "Governance-first: invest in committees, roles and decision rights before tooling. Maturity spectrum from reference-list management to fully governed ecosystems (OpenHIE terminology maturity model). Compare cat-harness/processes/upstream-version-adoption.bpmn for the upstream-release intake step.", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-032-345-semantic-governance-infrastructure", "pages": "68-73", "quote": "the governance layer, five categories of capability recur across the metadata registry components." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-032-345-semantic-governance-infrastructure", "pages": "68-73", "quote": "therefore invest first in the committees, roles, decision rights and community processes of" } ] }, { "id": "ra-operational-to-strategic-escalation", "title": "RA 3.4.4 - Escalation from operational to strategic governance", "steps": [ { "n": 1, "name": "Operational governance detects an issue" }, { "n": 2, "name": "Test against defined escalation triggers (scope change, utilisation near overuse thresholds, unresolvable stakeholder conflict, systemic security incident, continuity-threatening funding constraint)" }, { "n": 3, "name": "Escalate to strategic governance - documented and time-bound" }, { "n": 4, "name": "Strategic governance decides" }, { "n": 5, "name": "Decision communicated back to the operational body" } ], "actors": [ "Operational governance body", "Strategic governance body" ], "inputs": [ "Issue exceeding operational mandate" ], "outputs": [ "Documented, communicated decision" ], "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-031-344-operational-governance", "pages": "67-68", "quote": "time-bound, and resolved with a clear decision communicated back to the operational body, so" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-031-344-operational-governance", "pages": "67-68", "quote": "arise that cross scope boundaries, carry equity or sustainability implications, or exceed" } ] }, { "id": "ra-component-conformance-testing", "title": "RA 3.7 / 4.3.5 - Conformance testing of a component in an actor role", "steps": [ { "n": 1, "name": "System declares the actor roles and optional services it supports (cf. IHE Integration Statement)" }, { "n": 2, "name": "Derive test scope: every mandatory service; optional services only where declared" }, { "n": 3, "name": "For standardised actors reuse IHE test plans, simulators and reference data; for bespoke ones build tests" }, { "n": 4, "name": "Per interaction, the system under test plays one actor role while a simulator (or a test operator via UI) plays the other" }, { "n": 5, "name": "Verify the system-under-test's services behave as specified; record the verdict" }, { "n": 6, "name": "Report ratios (requirements coverage, standards conformance, capability completeness); certification as a procurement condition" } ], "actors": [ "System under test (vendor product / national service)", "Simulator (realises the opposite actor)", "Test operator", "Adopter / national team", "IHE (deferred specification and tooling)", "Procurement authority" ], "inputs": [ "Reference architecture model (actors, services, interactions)", "Published profiles", "IHE test tooling / interoperability test bed" ], "outputs": [ "Test plan", "Conformance results per actor role", "Conformance certification" ], "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-048-372-the-model", "pages": "90-94", "quote": "Testing exercises one side of an interaction at a time." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-067-435-minimum-conformance-and-testing", "pages": "109", "quote": "certification against published profiles as a condition of approval for procurement of DPI-H" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-050-374-planning-testing-from-the-architecture", "pages": "95-96", "quote": "Standard components arrive tested. Where a component realises a standardised" } ] }, { "id": "ra-adoption-mapping-and-coverage", "title": "RA 3.7.5 - Evaluate country adoption of the reference by mapping (coverage and gaps)", "steps": [ { "n": 1, "name": "Express the country architecture in the same formal language" }, { "n": 2, "name": "Map each country element to the reference element it realises" }, { "n": 3, "name": "Record the relation as adoption, adaptation (with documented rationale) or mapping" }, { "n": 4, "name": "Covered reference elements inherit their criteria; test them as in component conformance" }, { "n": 5, "name": "Compute coverage = share of reference elements realised; list unrealised elements as gaps for the roadmap" } ], "actors": [ "National architects", "Reviewers and assessors" ], "inputs": [ "Country architecture model", "Reference architecture model" ], "outputs": [ "Element mapping", "Coverage measure", "Gap list feeding the roadmap" ], "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-051-375-validating-goals-and-adoption", "pages": "96-97", "quote": "A reference element is covered when at least one country element realises it." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-051-375-validating-goals-and-adoption", "pages": "96-97", "quote": "case the correspondence is expressed as a realisation relationship, and it is this that makes" } ] } ], "glossary": [ { "term": "Accesses (relationship)", "definition": "Accesses — a component accesses the data objects it reads or writes.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-025-31-the-architecture-description-approach", "pages": "52-59", "quote": "Accesses — a component accesses the data objects it reads or writes." } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Actor (conformance model)", "definition": "An actor is an abstract information-processing role — for example a Document Source or a Patient Demographics Consumer.", "status": "overlaps:folio-assistant-core/glossary/cat-harness.glossary.json", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-048-372-the-model", "pages": "90-94", "quote": "An actor is an abstract information-processing role — for example a Document Source or a" } ], "conflictsWith": [ { "repository": "folio-assistant-core/glossary/cat-harness.glossary.json", "term": "actor", "definition": "A concrete participant, human, agentic or mechanical, that persists across every process and takes on roles. (truncated)", "severity": "substantive", "difference": "The platform's \"actor\" is a concrete participant that takes on roles; the RA's \"actor\" is an abstract information-processing ROLE realised by concrete systems - closer to the platform's \"role\". Adopting the RA term unqualified would collide." } ], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Adaptation (country-to-reference)", "definition": "Under adaptation, it modifies or extends reference elements to suit local context, health system structure, or regulatory requirements — the most common path —", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-051-375-validating-goals-and-adoption", "pages": "96-97", "quote": "adaptation, it modifies or extends reference elements to suit local context, health system" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Adoption (country-to-reference)", "definition": "Under adoption, the national architecture uses the reference elements directly, without modification — the strongest form of alignment, and the most straightforward to assess.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-051-375-validating-goals-and-adoption", "pages": "96-97", "quote": "Under adoption, the national architecture uses the reference elements directly, without" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Algorithm", "definition": "A specification of how a computer shall solve a problem, perform a calculation and execute a task.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "8", "quote": "A specification of how a computer shall solve a problem, perform a calculation and execute a task." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Annotation", "definition": "In a decision table, an annotation simply provides further details and explanation to the rule, for those working on and working from the decision table.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "8", "quote": "In a decision table, an annotation simply provides further details and explanation to the rule, for those working on and working from the decision table." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Application Component", "definition": "A deployable, modular piece of software that provides a defined set of functionality and holds the data it manages, exposing both through services.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "A deployable, modular piece of software that provides a defined set of functionality and holds the data it manages, exposing both through services." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Application Function", "definition": "Internal automated behaviour of a component", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-048-372-the-model", "pages": "90-94", "quote": "Internal automated behaviour of a component" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Application Interaction", "definition": "Collective application behaviour performed by two or more components", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-048-372-the-model", "pages": "90-94", "quote": "Collective application behaviour performed by two or more components" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Application Service", "definition": "An explicitly defined unit of application behaviour. An application service exposes the functionality of an application component to its environment.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "An explicitly defined unit of application behaviour. An application service exposes the functionality of an application component to its environment." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-025-31-the-architecture-description-approach", "pages": "52-59", "quote": "The functionality an application component exposes to its environment, as a unit of useful behaviour." } ], "conflictsWith": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-025-31-the-architecture-description-approach", "term": "Application service (Table 3.1)", "definition": "The functionality an application component exposes to its environment, as a unit of useful behaviour.", "severity": "wording", "difference": "RA glossary vs Table 3.1 phrasing." } ], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Artificial intelligence", "definition": "Artificial intelligence is understood here broadly, as machine-based systems that, for a given set of objectives, infer from the data they receive how to generate outputs such as predictions, recommendations, classifications, or decisions.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-078-463-approaches-to-financing", "pages": "114-115", "quote": "Artificial intelligence is understood here broadly, as machine-based systems that, for a given set" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "As-is", "definition": "The current state of things (also see to-be).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "8", "quote": "The current state of things (also see to-be)." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Assignment (relationship)", "definition": "Allocates an active structure element to the behaviour it performs", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-048-372-the-model", "pages": "90-94", "quote": "Allocates an active structure element to the behaviour it performs" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Benefits Package Registry", "definition": "The Benefits Package Registry is the national authoritative record of all health benefit packages offered within a country's health financing ecosystem.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-100-benefits-package-registry", "pages": "210-218", "quote": "The Benefits Package Registry is the national authoritative record of all health benefit packages offered" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Beta version", "definition": "The initial version of the software, after prototyping, that is available for testing among a limited group of people.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "8", "quote": "The initial version of the software, after prototyping, that is available for testing among a limited group of people." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Build", "definition": "In the context of developing a person-centred point of service system (PCPOSS), build is when a software engineer is writing the necessary code or programming the software.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "8", "quote": "In the context of developing a person-centred point of service system (PCPOSS), build is when a software engineer is writing the necessary code or programming the software." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Business Domain", "definition": "A specific focus area or subsystem within a broader business system, characterized by its own essential attributes [Under review]", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "A specific focus area or subsystem within a broader business system, characterized by its own essential attributes [Under review]" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Business objective", "definition": "A time-targeted and measurable output or outcome of a routine health system function. Examples include, “completed health service user registration”, or “health service user referral sent” (1).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "8", "quote": "A time-targeted and measurable output or outcome of a routine health system function. Examples include, “completed health service user registration”, or “health service user referral sent” (1)." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Business process", "definition": "A set of activities and tasks performed in coordination to achieve a specified business objective, or to deliver value in a specific way to a health service user. In the context of digitizing care pathways, this could include “health service user registration” and “referrals”, for example (see section 3.3).", "status": "overlaps:smart-base/docs/artifact/StructureDefinition-BusinessProcessWorkflow.md", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "8", "quote": "A set of activities and tasks performed in coordination to achieve a specified business objective, or to deliver value in a specific way to a health service user. In the" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Business Services layer", "definition": "A layer of the reference architecture grouping the health capabilities that national health systems strive to deliver across their principal domains — clinical care, public health, the health supply chain, and health financing — together with the shared components that enable them.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "A layer of the reference architecture grouping the health capabilities that national health systems strive to deliver across their principal domains — clinical care, public health, the health supply chain," } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Capability", "definition": "A high-level ability the health system possesses or needs in order to achieve its goals. It expresses what the health system is able to do, independently of how that ability is implemented.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "A high-level ability the health system possesses or needs in order to achieve its goals. It expresses what the health system is able to do, independently of how that ability" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-025-31-the-architecture-description-approach", "pages": "52-59", "quote": "An ability the health system possesses or needs, expressed independently of how it is implemented." } ], "conflictsWith": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-025-31-the-architecture-description-approach", "term": "Capability (Table 3.1)", "definition": "An ability the health system possesses or needs, expressed independently of how it is implemented.", "severity": "wording", "difference": "RA glossary: \"A high-level ability ... in order to achieve its goals\"; RA Table 3.1: \"An ability ... expressed independently of how it is implemented\"." } ], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Care pathway", "definition": "A care pathway is a complex intervention for the mutual decision-making and organization of care processes for a well defined group of health service users during a well defined period (2,3).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "8", "quote": "A care pathway is a complex intervention for the mutual decision-making and organization of care processes for a well defined group of health service users during a well defined period" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Client", "definition": "Members of the public who are potential or current users of health services, including health prevention and wellness activities.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "Members of the public who are potential or current users of health services, including health prevention and wellness activities." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Client Registry", "definition": "The Client Registry is the national authoritative source of health-specific person identity.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-090-client-registry", "pages": "125-135", "quote": "The Client Registry is the national authoritative source of health-specific person identity." } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Clinical protocol", "definition": "An official set of procedures or processes outlined by clinical guidelines set at national and/or higher levels.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "8", "quote": "An official set of procedures or processes outlined by clinical guidelines set at national and/or higher levels." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Community-based information system", "definition": "Applications that facilitate data collection and use at the community level. These applications are utilized by community-based workers who provide health promotion and disease prevention activities (6).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "8", "quote": "Applications that facilitate data collection and use at the community level. These applications are utilized by community-based workers who provide health promotion and disease prevention activities (6)." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Composes (relationship)", "definition": "Composes — a component is composed of the functions and data objects it contains;", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-025-31-the-architecture-description-approach", "pages": "52-59", "quote": "Composes — a component is composed of the functions and data objects it contains;" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Computable Decision Support Engine (CDSE)", "definition": "The Computable Decision Support Engine is a governed, shared application component that delivers context-appropriate, evidence-based guidance at the point of clinical decision-making by applying computable clinical rules, algorithms, and logic to person-specific data drawn from the Lifelong Health Record and other relevant sources.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-098-computable-decision-support-engine", "pages": "191-202", "quote": "The Computable Decision Support Engine is a governed, shared application component that delivers" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Conformance", "definition": "Conformance is the assertion that a given Application Component correctly realises the Application Services associated with a named actor role — as initiator, as responder, or both.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-048-372-the-model", "pages": "90-94", "quote": "Conformance is the assertion that a given Application Component correctly realises the" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Coverage (adoption)", "definition": "coverage is the proportion of reference elements realised by the country architecture, while the conformance of those covered elements is tested through their inherited criteria.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-051-375-validating-goals-and-adoption", "pages": "96-97", "quote": "coverage is the proportion of reference elements realised by" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Data custodian (body, ch. 02)", "definition": "Data custodian: responsible for the technical management and security of product master data.", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-026", "pages": "26", "quote": "Data custodian: responsible for the technical management and security of product master data." } ], "conflictsWith": [], "kind": "body", "definedIn": [ "9789240116191-eng" ] }, { "term": "Data dictionary", "definition": "A singular storage location for information about the data elements, detailing their type and definition, relationships, origin and use.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "8", "quote": "A singular storage location for information about the data elements, detailing their type and definition, relationships, origin and use." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Data element", "definition": "A unit of data that has a specific and precise meaning.", "status": "overlaps:smart-base/docs/artifact/StructureDefinition-CoreDataElement.md", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "8", "quote": "A unit of data that has a specific and precise meaning." }, { "libraryId": "9789240116191-eng", "sectionId": "page-008", "pages": "8", "quote": "A unit of data that has a specific and precise meaning." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240116191-eng" ] }, { "term": "Data Governance", "definition": "The structures and standards (policies & legal frameworks) necessary to coordinate and manage the data journey from collection, storage, sharing, analysis to use to produce trusted, secure and quality data for decision making", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "The structures and standards (policies & legal frameworks) necessary to coordinate and manage the data journey from collection, storage, sharing, analysis to use to produce trusted, secure and quality data" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Data Object", "definition": "A defined unit of structured data used or produced by an application component.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "A defined unit of structured data used or produced by an application component." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Data owner (body, ch. 02)", "definition": "Data owner: responsible for the overall strategy, governance, and quality of the product master data.", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-026", "pages": "26", "quote": "Data owner: responsible for the overall strategy, governance, and quality of the product master data." } ], "conflictsWith": [], "kind": "body", "definedIn": [ "9789240116191-eng" ] }, { "term": "Data steward (body, ch. 02)", "definition": "Data steward: responsible for the day-to-day management, maintenance, and quality control of the product master data.", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-026", "pages": "26", "quote": "Data steward: responsible for the day-to-day management, maintenance, and quality control of the product master data." } ], "conflictsWith": [], "kind": "body", "definedIn": [ "9789240116191-eng" ] }, { "term": "Decision support logic", "definition": "A set of decision rules for standard and exceptional cases that is utilized for a decision task within a business process. This helps to reduce the complexity of the business process without losing the detail necessary for coding the rules needed for system functionality (7).", "status": "overlaps:smart-base/docs/artifact/StructureDefinition-DecisionSupportLogic.md", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "8", "quote": "A set of decision rules for standard and exceptional cases that is utilized for a decision task within a business process. This helps to reduce the complexity of the business" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Decision support system", "definition": "A digital job aid that combines an individual’s health information with the health worker’s knowledge and clinical protocols, to assist health workers in making diagnosis and treatment decisions (8).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "8", "quote": "A digital job aid that combines an individual’s health information with the health worker’s knowledge and clinical protocols, to assist health workers in making diagnosis and treatment decisions (8)." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Decision-support table", "definition": "A structured way to depict a discrete decision that will need to be embedded into the PCPOSS. There can be multiple decision-support tables (9).", "status": "overlaps:cat-harness/methodologies/dmn.md", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "8", "quote": "A structured way to depict a discrete decision that will need to be embedded into the PCPOSS. There can be multiple decision-support tables (9)." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Deploy", "definition": "Make the software available for use beyond testing purposes.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "8", "quote": "Make the software available for use beyond testing purposes." }, { "libraryId": "9789240101197-eng", "sectionId": "page-008", "pages": "8", "quote": "Making a software system available for use beyond testing purposes." } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-008", "term": "deployment", "definition": "Making a software system available for use beyond testing purposes.", "severity": "wording", "difference": "Wording differs (automatic comparison; not reviewed as substantive)." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng" ] }, { "term": "DevSecOps", "definition": "Short for “development, security and operations”. Engineers working in DevSecOps are responsible for ensuring that the system is up and running according to plan, for ensuring it is deployed in a secure environment, and for monitoring bugs and server-side issues.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "8", "quote": "Short for “development, security and operations”. Engineers working in DevSecOps are responsible for ensuring that the system is up and running according to plan, for ensuring it is deployed in" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Digital adaptation kits (DAKs)", "definition": "Operational, software-neutral, standardized documentation that distil clinical, public health and data use guidance into a format that can be transparently incorporated into digital systems. DAKs are designed to facilitate the accurate reflection of WHO’s clinical, public health and data use guidelines within the digital systems countries are adopting (8). This is knowledge layer 2, or L2, of the “SMART Guidelines” framework (10).", "status": "overlaps:smart-base/docs/artifact/StructureDefinition-DAK.md", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "Operational, software-neutral, standardized documentation that distil clinical, public health and data use guidance into a format that can be transparently incorporated into digital systems. DAKs are designed to facilitate the" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Digital health", "definition": "Digital health is the systematic application of information and communications technologies, computer science, and data to support informed decision-making by individuals, the health workforce, and health systems, to strengthen resilience to disease and improve health and wellness (11).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "Digital health is the systematic application of information and communications technologies, computer science, and data to support informed decision-making by individuals, the health workforce, and health systems, to strengthen resilience" }, { "libraryId": "9789240101197-eng", "sectionId": "page-008", "pages": "8", "quote": "The systematic application of information and communications technologies, computer science and data to support informed decision-making by individuals, the health workforce and health systems, to strengthen resilience to disease and" }, { "libraryId": "9789240101197-eng", "sectionId": "page-012", "pages": "12", "quote": "digital health refers to “the field of knowledge and practice associated with the development and use of digital technologies to improve health.”" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "The systematic application of information and communications technologies, computer science, and data to support informed decision-making by individuals, the health workforce, and health systems, to strengthen resilience to disease and" } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-008", "term": "digital health", "definition": "The systematic application of information and communications technologies, computer science and data to support informed decision-making by individuals, the health workforce and health systems, to strengthen resilience to disease and improve health and wellness (1, 2).", "severity": "wording", "difference": "Near-identical: differs only in phrasing, punctuation or citation markers." }, { "libraryId": "9789240101197-eng", "sectionId": "page-012", "term": "digital health (body, quoting the Global Strategy)", "definition": "digital health refers to “the field of knowledge and practice associated with the development and use of digital technologies to improve health.”", "severity": "internal", "difference": "PHC, SC and RA glossaries agree; the SC introduction body quotes a different Global Strategy definition, \"the field of knowledge and practice associated with the development and use of digital technologies to improve health\"." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "term": "Digital Health", "definition": "The systematic application of information and communications technologies, computer science, and data to support informed decision-making by individuals, the health workforce, and health systems, to strengthen resilience to disease and improve health and wellness.", "severity": "wording", "difference": "Near-identical: differs only in phrasing, punctuation or citation markers." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Digital health intervention", "definition": "A discrete capability of digital technology to achieve health sector objectives.", "status": "overlaps:smart-base/docs/artifact/CodeSystem-CDHIv2.md", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "A discrete capability of digital technology to achieve health sector objectives." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "digital health supply chain (DHSC) (body)", "definition": "Digital health supply chain refers to the knowledge and practice of adopting digital technologies to improve health supply chains and enable the delivery of quality-assured health products to individuals when and where they need them (Fig. 3).", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-012", "pages": "12", "quote": "Digital health supply chain refers to the knowledge and practice of adopting digital technologies to improve health supply chains and enable the delivery of quality-assured health products to individuals when" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "9789240101197-eng" ] }, { "term": "digital health supply chain intervention", "definition": "An intervention that involves the use of digital technologies to improve the management and operation of health supply chains. It aims to enhance the efficiency and effectiveness of health supply chain processes such as planning, procurement, distribution and warehouse management.", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-008", "pages": "8", "quote": "An intervention that involves the use of digital technologies to improve the management and operation of health supply chains. It aims to enhance the efficiency and effectiveness of health supply" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240101197-eng" ] }, { "term": "Digital Infrastructure", "definition": "Infrastructures in the digital domain are digital resources, such as systems and specifications, built as shared means to achieve many ends", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "Infrastructures in the digital domain are digital resources, such as systems and specifications, built as shared means to achieve many ends" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Digital Public Infrastructure (DPI)", "definition": "A set of shared digital systems that should be secure and interoperable, and can be built on open standards and specifications to deliver and provide equitable access to public and/or private services at societal scale and are governed by applicable legal frameworks and enabling rules to drive development, inclusion, innovation, trust, and competition, while respecting human rights and fundamental freedoms. (G20/UNDP)", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "A set of shared digital systems that should be secure and interoperable, and can be built on open standards and specifications to deliver and provide equitable access to public and/or" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-001-112-understanding-digital-public-infrastructure", "pages": "19-21", "quote": "DPI is an approach to digitalization focused on creating" } ], "conflictsWith": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-001-112-understanding-digital-public-infrastructure", "term": "DPI (body, §1.1.2, World Bank)", "definition": "DPI is an approach to digitalization focused on creating “foundational, digital building blocks designed for the public benefit.”", "severity": "wording", "difference": "Glossary uses the G20 definition; section 1.1.2 also gives the World Bank framing (\"an approach to digitalization\")." } ], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "One or more non-primary definitions verified with line-number lines removed" }, { "term": "Digital transformation", "definition": "The process of digitally optimizing and driving systems-level changes by leveraging innovation, analytics and feedback mechanisms to improve person-centred health systems. Digital technologies are used to fundamentally change and improve how health services are delivered and accessed across all health programme areas (12,14,15).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "The process of digitally optimizing and driving systems-level changes by leveraging innovation, analytics and feedback mechanisms to improve person-centred health systems. Digital technologies are used to fundamentally change and improve" }, { "libraryId": "9789240101197-eng", "sectionId": "page-008", "pages": "8", "quote": "In the health context, using digital technologies to fundamentally change and improve how health services are delivered and accessed across all health programme areas (3, 4, 5). The process involves" }, { "libraryId": "9789240116191-eng", "sectionId": "page-008", "pages": "8", "quote": "The process of digitally optimizing and driving systems-level changes by leveraging innovation, analytics, and feedback mechanisms to improve person centred health systems. Digital technologies are used to fundamentally change and" } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-008", "term": "digital transformation", "definition": "In the health context, using digital technologies to fundamentally change and improve how health services are delivered and accessed across all health programme areas (3, 4, 5). The process involves using innovation, analytics and feedback mechanisms to achieve systems-level changes.", "severity": "wording", "difference": "SC reorders the same content and prefixes \"In the health context\"; PC writes \"person centred\"." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "9789240116191-eng" ] }, { "term": "Digitalization", "definition": "The process of digitally automating and simplifying processes to streamline individual health programmes and reduce manual efforts for greater efficiency (12,13).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "The process of digitally automating and simplifying processes to streamline individual health programmes and reduce manual efforts for greater efficiency (12,13)." }, { "libraryId": "9789240101197-eng", "sectionId": "page-008", "pages": "8", "quote": "In the health context, the process of digitally automating and simplifying processes to streamline individual health programmes and reduce manual efforts for greater efficiency. Digitalization is the second step in" }, { "libraryId": "9789240116191-eng", "sectionId": "page-008", "pages": "8", "quote": "The process of digitally automating and simplifying processes to streamline individual health programmes and reducing manual efforts for greater efficiency. Digitalization is the second step towards digital transformation.3, 4" } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-008", "term": "digitalization", "definition": "In the health context, the process of digitally automating and simplifying processes to streamline individual health programmes and reduce manual efforts for greater efficiency. Digitalization is the second step in digital transformation (3, 6).", "severity": "substantive", "difference": "SC and PC add the claim that digitalization is \"the second step\" in/towards digital transformation; PHC does not." }, { "libraryId": "9789240116191-eng", "sectionId": "page-008", "term": "Digitalization", "definition": "The process of digitally automating and simplifying processes to streamline individual health programmes and reducing manual efforts for greater efficiency. Digitalization is the second step towards digital transformation.3, 4", "severity": "substantive", "difference": "SC and PC add the claim that digitalization is \"the second step\" in/towards digital transformation; PHC does not." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "9789240116191-eng" ] }, { "term": "Digitization", "definition": "The process of converting and organizing data from paper records into a digital format for easier entry, storage and retrieval (12,16).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "The process of converting and organizing data from paper records into a digital format for easier entry, storage and retrieval (12,16)." }, { "libraryId": "9789240101197-eng", "sectionId": "page-008", "pages": "8", "quote": "The process of converting and organizing data from manual paper records into a digital format for easier entry, storage and retrieval. Digitization is the initial step in digital transformation (3," }, { "libraryId": "9789240116191-eng", "sectionId": "page-008", "pages": "8", "quote": "The process of converting and organizing data from paper records into a digital format for easier entry, storage and retrieval. Digitization is the initial step towards digital transformation.1, 2" } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-008", "term": "digitization", "definition": "The process of converting and organizing data from manual paper records into a digital format for easier entry, storage and retrieval. Digitization is the initial step in digital transformation (3, 7).", "severity": "substantive", "difference": "SC and PC add a sequencing claim (digitization is the initial step in/towards digital transformation) that PHC does not make; SC also adds \"manual\"." }, { "libraryId": "9789240116191-eng", "sectionId": "page-008", "term": "Digitization", "definition": "The process of converting and organizing data from paper records into a digital format for easier entry, storage and retrieval. Digitization is the initial step towards digital transformation.1, 2", "severity": "substantive", "difference": "SC and PC add a sequencing claim (digitization is the initial step in/towards digital transformation) that PHC does not make; SC also adds \"manual\"." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "9789240116191-eng" ] }, { "term": "Electronic health record system", "definition": "A secure, online system that holds health service user health records, which include information about people’s health and clinical care. This system is managed by health workers. Also referred to as an “electronic medical record system” (6).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "A secure, online system that holds health service user health records, which include information about people’s health and clinical care. This system is managed by health workers. Also referred to" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "End-user", "definition": "People who will be using the digital system(s).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "People who will be using the digital system(s)." }, { "libraryId": "9789240101197-eng", "sectionId": "page-008", "pages": "8", "quote": "People who will be using the digital systems." }, { "libraryId": "9789240116191-eng", "sectionId": "page-008", "pages": "8", "quote": "People who will be using the digital system(s)." } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-008", "term": "end users", "definition": "People who will be using the digital systems.", "severity": "wording", "difference": "Wording differs (automatic comparison; not reviewed as substantive)." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "9789240116191-eng" ] }, { "term": "Enterprise architecture", "definition": "A blueprint of business processes, data, systems and technologies used to help planners, software developers and managers design increasingly complex systems to support the workflow and roles of people in a large enterprise, such as a health system (11).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "A blueprint of business processes, data, systems and technologies used to help planners, software developers and managers design increasingly complex systems to support the workflow and roles of people in" }, { "libraryId": "9789240101197-eng", "sectionId": "page-008", "pages": "8", "quote": "A blueprint of business processes, data, systems and technologies that helps planners, software developers and managers design increasingly complex systems to support the workflow and roles of people in a" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "The organising logic for business processes and IT infrastructure reflecting the integration and standardisation requirements of the organisation's operating model. [Under review]" } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-008", "term": "enterprise architecture", "definition": "A blueprint of business processes, data, systems and technologies that helps planners, software developers and managers design increasingly complex systems to support the workflow and roles of people in a large enterprise such as a health system (1).", "severity": "wording", "difference": "Near-identical: differs only in phrasing, punctuation or citation markers." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "term": "Enterprise Architecture", "definition": "The organising logic for business processes and IT infrastructure reflecting the integration and standardisation requirements of the organisation's operating model. [Under review]", "severity": "substantive", "difference": "PHC and SC: \"a blueprint of business processes, data, systems and technologies\"; RA: \"the organising logic for business processes and IT infrastructure\" reflecting the operating model, marked [Under review]." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Fast Healthcare Interoperability Resources (FHIR)", "definition": "FHIR is a standard for healthcare data exchange, published by HL7®", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "FHIR is a standard for healthcare data exchange, published by HL7®" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Features", "definition": "The characteristics of a system that include look and feel as well as what the system can do (e.g. “reporting” can be a feature of a PCPOSS).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "The characteristics of a system that include look and feel as well as what the system can do (e.g. “reporting” can be a feature of a PCPOSS)." }, { "libraryId": "9789240101197-eng", "sectionId": "page-008", "pages": "8", "quote": "The characteristics of a system that include look and feel as well as what the system can do (e.g., “order processing” can be a feature of an order management solution)." }, { "libraryId": "9789240116191-eng", "sectionId": "page-008", "pages": "8", "quote": "The characteristics of your system that include look and feel as well as what the system can do (e.g., “approval workflow” can be a feature of a product master data" } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-008", "term": "features", "definition": "The characteristics of a system that include look and feel as well as what the system can do (e.g., “order processing” can be a feature of an order management solution).", "severity": "wording", "difference": "Domain examples differ; PC says \"your system\"." }, { "libraryId": "9789240116191-eng", "sectionId": "page-008", "term": "Features", "definition": "The characteristics of your system that include look and feel as well as what the system can do (e.g., “approval workflow” can be a feature of a product master data management solution).", "severity": "wording", "difference": "Domain examples differ; PC says \"your system\"." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "9789240116191-eng" ] }, { "term": "Flag", "definition": "In a PCPOSS, a “flag” consists of symbols, colours, shapes and/or text formatting changes used to draw attention to a particular health service user(s) for specific reasons based on documented criteria (e.g. high-risk pregnancy, vaccination default).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "In a PCPOSS, a “flag” consists of symbols, colours, shapes and/or text formatting changes used to draw attention to a particular health service user(s) for specific reasons based on documented" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "foundational components (body, DHSC architecture)", "definition": "These components provide system capabilities for organizing and managing master data such as product, facility and supplier data.", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-035", "pages": "35", "quote": "These components provide system capabilities for organizing and managing master data such as product, facility and supplier data." } ], "conflictsWith": [], "kind": "body", "definedIn": [ "9789240101197-eng" ] }, { "term": "Functional application", "definition": "Functional applications are application components that deliver a specific operational function within a defined domain. They are context-specific, reflecting the operational requirements of a programme, scheme, or institution that procures them.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "Functional applications are application components that deliver a specific operational function within a defined domain. They are context-specific, reflecting the operational requirements of a programme, scheme, or institution that procures" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Functional requirements", "definition": "Description of what the digital system needs to do to support the tasks that make up the health system process and address the identified health system challenges (e.g. a PCPOSS must be able to remind health workers which health service users to follow-up with).", "status": "overlaps:smart-base/docs/artifact/StructureDefinition-FunctionalRequirement.md", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "Description of what the digital system needs to do to support the tasks that make up the health system process and address the identified health system challenges (e.g. a PCPOSS" }, { "libraryId": "9789240101197-eng", "sectionId": "page-008", "pages": "8", "quote": "A description of what the digital system needs to do to support the tasks that make up the business process and address the identified challenges." }, { "libraryId": "9789240116191-eng", "sectionId": "page-008", "pages": "8", "quote": "Description of what the digital system needs to do to support the tasks that make up the health system process and address the identified challenges (e.g., a product master data" } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-008", "term": "functional requirements", "definition": "A description of what the digital system needs to do to support the tasks that make up the business process and address the identified challenges.", "severity": "wording", "difference": "PHC/PC: tasks of \"the health system process\"; SC: tasks of \"the business process\"." }, { "libraryId": "9789240116191-eng", "sectionId": "page-008", "term": "Functional requirements", "definition": "Description of what the digital system needs to do to support the tasks that make up the health system process and address the identified challenges (e.g., a product master data management solution must be able to define categories and attributes to organize product information).", "severity": "wording", "difference": "PHC/PC: tasks of \"the health system process\"; SC: tasks of \"the business process\"." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "9789240116191-eng" ] }, { "term": "Functions", "definition": "Functions in a system are how features are implemented (e.g. “calculating aggregate data” and “displaying feedback in the form of diagrams” are functions of the “reporting” feature of a PCPOSS).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "Functions in a system are how features are implemented (e.g. “calculating aggregate data” and “displaying feedback in the form of diagrams” are functions of the “reporting” feature of a PCPOSS)." }, { "libraryId": "9789240101197-eng", "sectionId": "page-008", "pages": "8", "quote": "Business processes within a system that help the system perform (e.g., “receiving inventory” and “picking inventory” are functions of the “warehousing” feature of a warehouse management system)." } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-008", "term": "functions", "definition": "Business processes within a system that help the system perform (e.g., “receiving inventory” and “picking inventory” are functions of the “warehousing” feature of a warehouse management system).", "severity": "substantive", "difference": "PHC: functions are \"how features are implemented\"; SC: functions are \"Business processes within a system that help the system perform\"." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng" ] }, { "term": "Generic product or product information", "definition": "In this handbook, the terms ‘generic product,’ ‘product,’ or ‘product information’ pertain to the general identifying details of a health product, excluding any manufacturer-specific information.", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-008", "pages": "8", "quote": "In this handbook, the terms ‘generic product,’ ‘product,’ or ‘product information’ pertain to the general identifying details of a health product, excluding any manufacturer-specific information." }, { "libraryId": "9789240116191-eng", "sectionId": "page-028", "pages": "28", "quote": "Generic products can be described as generic items that conceal the brand or manufacturer information." } ], "conflictsWith": [ { "libraryId": "9789240116191-eng", "sectionId": "page-028", "term": "Generic product (body, ch. 02)", "definition": "Generic products can be described as generic items that conceal the brand or manufacturer information.", "severity": "wording", "difference": "Glossary: identifying details \"excluding any manufacturer-specific information\"; body: items \"that conceal the brand or manufacturer information\"." } ], "kind": "glossary", "definedIn": [ "9789240116191-eng" ] }, { "term": "Goal", "definition": "A high-level statement of intent, direction, or desired state for an organisation and its stakeholders.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "A high-level statement of intent, direction, or desired state for an organisation and its stakeholders." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "governance (body, health supply chain)", "definition": "In the context of the health supply chain, governance is the process of establishing and implementing policies, procedures and mechanisms to ensure that the supply chain processes and the systems to manage those processes are managed effectively, ethically and in alignment with established objectives and stakeholders’ interests.", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-045", "pages": "45", "quote": "In the context of the health supply chain, governance is the process of establishing and implementing policies, procedures and mechanisms to ensure that the supply chain processes and the systems" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-028-341-purpose-and-framing", "pages": "64-65", "quote": "Governance is the set of arrangements through which decision authority is distributed," } ], "conflictsWith": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-028-341-purpose-and-framing", "term": "Governance (body, §3.4.1)", "definition": "Governance is the set of arrangements through which decision authority is distributed, exercised and accounted for across all those who depend upon, contribute to, or are served by the shared infrastructure.", "severity": "substantive", "difference": "SC (supply chain): \"the process of establishing and implementing policies, procedures and mechanisms\"; RA: \"the set of arrangements through which decision authority is distributed, exercised and accounted for\"." } ], "kind": "body", "definedIn": [ "9789240101197-eng", "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "One or more non-primary definitions verified with line-number lines removed" }, { "term": "Health Digital Public Infrastructure (DPI-H)", "definition": "Health Digital Public Infrastructure (DPI-H) refers to digital resources that are built as a shared means for fulfilling multiple health agency functions.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "Health Digital Public Infrastructure (DPI-H) refers to digital resources that are built as a shared means for fulfilling multiple health agency functions." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-001-112-understanding-digital-public-infrastructure", "pages": "19-21", "quote": "Health Digital Public Infrastructure (DPI-H) refers to digital resources that are built as a shared means for fulfilling multiple health agency functions." } ], "conflictsWith": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-001-112-understanding-digital-public-infrastructure", "term": "Health Digital Public Infrastructure (body, §1.1.2)", "definition": "Health Digital Public Infrastructure (DPI-H) refers to digital resources that are built as a shared means for fulfilling multiple health agency functions. These digital resources for health — encompassing both systems and specifications — leverage foundational DPI, are interoperable, reusable, publicly governed and built on open standards.", "severity": "wording", "difference": "Body adds the systems-and-specifications sentence." } ], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "One or more non-primary definitions verified with line-number lines removed" }, { "term": "Health Facility Registry", "definition": "The Health Facility Registry is the national authoritative source of identity, location, and classification data for all facilities, locations, and organisations through which health services are delivered or that are of direct relevance to the Ministry of Health’s mandate.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-091-health-facility-registry", "pages": "135-146", "quote": "The Health Facility Registry is the national authoritative source of identity, location, and classification data" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Health Information Exchange", "definition": "[To be included before publication]", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "[To be included before publication]" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Health Management Information System (HMIS)", "definition": "The Health Management Information System is a governed, sharedapplication component responsible for the systematic collection, aggregation, analysis, and dissemination of population-level and facility-level health data", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-102-health-management-information-system", "pages": "221-229", "quote": "The Health Management Information System is a governed, sharedapplication component responsible for" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Health Programme", "definition": "Health programmes are structured and coordinated interventions and services, delivered to defined populations or patient groups, to prevent disease, promote health, and address specific health needs.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "Health programmes are structured and coordinated interventions and services, delivered to defined populations or patient groups, to prevent disease, promote health, and address specific health needs." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Health service users", "definition": "Also known as patients, clients or beneficiaries, these are individuals who receive formal and/or informal health services.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "Also known as patients, clients or beneficiaries, these are individuals who receive formal and/or informal health services." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Health service user’s health records", "definition": "The record of health information, including health services, clinical observations, diagnosis and any other interactions between a health service user and the health worker or community health worker. The record may be retained by the health-care facility or by the health service user.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "The record of health information, including health services, clinical observations, diagnosis and any other interactions between a health service user and the health worker or community health worker. The record" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "health supply chain information system", "definition": "A paper-based or software tool that supports the management and/or operations of the health supply chain. Such software tools (e.g., for order management or warehouse management) are also commonly referred to as electronic logistics management information systems.", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-008", "pages": "8", "quote": "A paper-based or software tool that supports the management and/or operations of the health supply chain. Such software tools (e.g., for order management or warehouse management) are also commonly referred" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240101197-eng" ] }, { "term": "Health Workforce Registry", "definition": "The Health Workforce Registry is the national authoritative record of identity, credential, and classification data for all health workers recognised as part of the national health workforce", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-092-health-workforce-registry", "pages": "146-156", "quote": "The Health Workforce Registry is the national authoritative record of identity, credential, and classification" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Input", "definition": "The input entry in a decision-support table is a “condition” for the rule to be met. There can be more than one input for the rule.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "The input entry in a decision-support table is a “condition” for the rule to be met. There can be more than one input for the rule." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Integration", "definition": "Bespoke capability of connecting one application component to another [Under review]", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "Bespoke capability of connecting one application component to another [Under review]" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Interoperability", "definition": "Ability of different applications to access, exchange, integrate and use data in a coordinated and consistent manner through the use of shared application interfaces, value sets, concepts and standards, within and across organizational, regional and national boundaries, to provide timely and seamless portability of information and optimize health outcomes.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "9", "quote": "Ability of different applications to access, exchange, integrate and use data in a coordinated and consistent manner through the use of shared application interfaces, value sets, concepts and standards, within" }, { "libraryId": "9789240093362-eng", "sectionId": "sec-023-44-design-system-architecture", "pages": "56-60", "quote": "Interoperability is the ability of different applications to access, exchange, integrate and use data in a coordinated manner through the use of shared application interfaces and standards, which should be" }, { "libraryId": "9789240101197-eng", "sectionId": "page-008", "pages": "8", "quote": "The ability of different applications to access, exchange, integrate and use data in a coordinated and consistent manner, through the use of shared application interfaces, value sets, concepts and standards" }, { "libraryId": "9789240116191-eng", "sectionId": "page-008", "pages": "8", "quote": "Ability of different applications to access, exchange, integrate and use data in a coordinated and consistent manner through the use of shared application interfaces, value sets, concepts and standards, within" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "Interoperability is the standards-based capability of heterogeneous information systems to communicate, exchange data, and use the exchanged information to execute functions effectively." } ], "conflictsWith": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-023-44-design-system-architecture", "term": "Interoperability (body, §4.4)", "definition": "Interoperability is the ability of different applications to access, exchange, integrate and use data in a coordinated manner through the use of shared application interfaces and standards, which should be defined by the EA and independent of a particular solution’s system architecture (22).", "severity": "internal", "difference": "PHC/PC glossaries agree; SC adds \"safe\" and \"help ensure good health outcomes\"; PHC section 4.4 body drops \"value sets, concepts\" and says standards \"should be defined by the EA\"; RA: \"the standards-based capability of heterogeneous information systems to communicate, exchange data, and use the exchanged information to execute functions\"." }, { "libraryId": "9789240101197-eng", "sectionId": "page-008", "term": "interoperability", "definition": "The ability of different applications to access, exchange, integrate and use data in a coordinated and consistent manner, through the use of shared application interfaces, value sets, concepts and standards within and across organizational, regional and national boundaries. In the health context, this provides timely, safe and seamless portability of information to help ensure good health outcomes (1).", "severity": "substantive", "difference": "PHC/PC glossaries agree; SC adds \"safe\" and \"help ensure good health outcomes\"; PHC section 4.4 body drops \"value sets, concepts\" and says standards \"should be defined by the EA\"; RA: \"the standards-based capability of heterogeneous information systems to communicate, exchange data, and use the exchanged information to execute functions\"." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "term": "Interoperability", "definition": "Interoperability is the standards-based capability of heterogeneous information systems to communicate, exchange data, and use the exchanged information to execute functions effectively.", "severity": "substantive", "difference": "PHC/PC glossaries agree; SC adds \"safe\" and \"help ensure good health outcomes\"; PHC section 4.4 body drops \"value sets, concepts\" and says standards \"should be defined by the EA\"; RA: \"the standards-based capability of heterogeneous information systems to communicate, exchange data, and use the exchanged information to execute functions\"." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "9789240116191-eng", "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "interoperability layer (body, DHSC architecture)", "definition": "This component facilitates the exchange of data across various systems as well as across levels of the health system.", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-035", "pages": "35", "quote": "This component facilitates the exchange of data across various systems as well as across levels of the health system." } ], "conflictsWith": [], "kind": "body", "definedIn": [ "9789240101197-eng" ] }, { "term": "Legacy system", "definition": "An outdated system or technology that is still in use. The system still meets the needs it was originally designed for but does not meet the current needs or allow room for growth. It may be a paper-based system or a digital system.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "10", "quote": "An outdated system or technology that is still in use. The system still meets the needs it was originally designed for but does not meet the current needs or allow" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Lifelong Health Record (LHR)", "definition": "The Lifelong Health Record (LHR) is one or more governed data repositories, whether physically consolidated or virtually federated, that collectively maintain a longitudinal, person-centred record of an individual's health and healthcare-related data in computable, standards-based format.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-094-lifelong-health-record", "pages": "166-175", "quote": "The Lifelong Health Record (LHR) is one or more governed data repositories, whether physically" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Logical Information Model Repository (LIMR)", "definition": "The Logical Information Model Repository is a governed, publicly accessible repository and management platform for computable clinical and administrative information models that define the logical structure, semantics, and constraints of health data, independently of any specific technology implementation.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-096-logical-information-model-repository", "pages": "183-191", "quote": "The Logical Information Model Repository is a governed, publicly accessible repository and management" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Logical Observation Identifiers Names and Codes (LOINC)", "definition": "LOINC is a common language (a set of identifiers, names, and codes) for identifying health measurements, observations, and documents.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "LOINC is a common language (a set of identifiers, names, and" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "Definition reassembled across a page break in the RA glossary table; each part verified separately" }, { "term": "Longitudinal tracking [of a health service user]", "definition": "Ongoing and systematic collection and analysis of data related to a health service user’s health or medical condition over an extended period of time.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "10", "quote": "Ongoing and systematic collection and analysis of data related to a health service user’s health or medical condition over an extended period of time." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Mapping (country-to-reference)", "definition": "Under mapping, a country that already has an established architecture keeps its own terminology and structure and provides an explicit correspondence to the reference elements,", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-051-375-validating-goals-and-adoption", "pages": "96-97", "quote": "Under mapping, a country that already has an established architecture keeps its own" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Minimum viable product (MVP)", "definition": "A product that satisfies the minimum requirements of the end-users and can function accordingly.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "10", "quote": "A product that satisfies the minimum requirements of the end-users and can function accordingly." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Mock-up", "definition": "Graphic design and descriptive documentation that closely depicts the look and feel (including colour scheme and design themes) of the finished product (see section 4.3).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "10", "quote": "Graphic design and descriptive documentation that closely depicts the look and feel (including colour scheme and design themes) of the finished product (see section 4.3)." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "National digital architect", "definition": "the national digital architect — an individual or small team embedded in government, with the authority to define architectural standards, evaluate conformance, and enforce coordination across programmes and ministries —", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-060-424-the-role-of-the-national-digital-architect", "pages": "104-105", "quote": "architect — an individual or small team embedded in government, with the authority to define" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "National digital health architecture roadmap", "definition": "a living document that maps the current state, the target direction, the gap between them, and the sequenced investments required to close it.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-055-412-assessing-where-you-are", "pages": "99-100", "quote": "a living document that maps the current state, the target direction, the gap between" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Non-functional requirements", "definition": "General attributes and features of the digital system to ensure usability and overcome technical and physical constraints. Examples of non-functional requirements include ability to work offline, multiple language settings, and password protection (see section 3.8).", "status": "overlaps:smart-base/docs/artifact/StructureDefinition-NonFunctionalRequirement.md", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "10", "quote": "General attributes and features of the digital system to ensure usability and overcome technical and physical constraints. Examples of non-functional requirements include ability to work offline, multiple language settings, and" }, { "libraryId": "9789240101197-eng", "sectionId": "page-008", "pages": "8", "quote": "A description of how the digital system needs to operate and perform in order to support the tasks that make up the business process." }, { "libraryId": "9789240116191-eng", "sectionId": "page-008", "pages": "8", "quote": "Description of the attributes and constraints that the system must have to ensure its quality and performance. These requirements do not specify what the system should do, but rather how" } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-008", "term": "nonfunctional requirements", "definition": "A description of how the digital system needs to operate and perform in order to support the tasks that make up the business process.", "severity": "substantive", "difference": "PHC: attributes and features \"to ensure usability and overcome technical and physical constraints\"; SC: \"how the digital system needs to operate and perform\" for business-process tasks; PC: \"attributes and constraints ... to ensure its quality and performance\"." }, { "libraryId": "9789240116191-eng", "sectionId": "page-008", "term": "Non-functional requirements", "definition": "Description of the attributes and constraints that the system must have to ensure its quality and performance. These requirements do not specify what the system should do, but rather how the system should perform its functions.", "severity": "substantive", "difference": "PHC: attributes and features \"to ensure usability and overcome technical and physical constraints\"; SC: \"how the digital system needs to operate and perform\" for business-process tasks; PC: \"attributes and constraints ... to ensure its quality and performance\"." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "9789240116191-eng" ] }, { "term": "NPC (national product catalogue tool) (body, ch. 03)", "definition": "A widely used term for such a tool is the NPC, which many countries implement to oversee product master data.", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-035", "pages": "35", "quote": "A widely used term for such a tool is the NPC, which many countries implement to oversee product master data." } ], "conflictsWith": [], "kind": "body", "definedIn": [ "9789240116191-eng" ] }, { "term": "Open source", "definition": "Open-source software is software with source code that is published and made freely available to the public, enabling anyone to inspect, modify and enhance the code (18).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "10", "quote": "Open-source software is software with source code that is published and made freely available to the public, enabling anyone to inspect, modify and enhance the code (18)." }, { "libraryId": "9789240101197-eng", "sectionId": "page-008", "pages": "8", "quote": "Software with source code that is published and made freely available to the public so anyone can inspect, modify and enhance the code within set guidelines (8)." }, { "libraryId": "9789240116191-eng", "sectionId": "page-008", "pages": "8", "quote": "Open-source software is software with source code that is published and made freely available to the public, enabling anyone to inspect, modify and enhance the code.8" } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-008", "term": "open-source software", "definition": "Software with source code that is published and made freely available to the public so anyone can inspect, modify and enhance the code within set guidelines (8).", "severity": "wording", "difference": "Wording differs (automatic comparison; not reviewed as substantive)." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "9789240116191-eng" ] }, { "term": "Open standards", "definition": "Standards that are documented and made freely available to the public, which are developed, approved and maintained via a collaborative and consensus-driven process. Open standards facilitate interoperability and data exchange and are intended for widespread adoption (20).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "10", "quote": "Standards that are documented and made freely available to the public, which are developed, approved and maintained via a collaborative and consensus-driven process. Open standards facilitate interoperability and data exchange" }, { "libraryId": "9789240101197-eng", "sectionId": "page-009", "pages": "9", "quote": "Standards that are documented and made freely available to the public. Open standards are developed, approved and maintained via a collaborative and consensus-driven process. Open standards facilitate interoperability and data" }, { "libraryId": "9789240116191-eng", "sectionId": "page-008", "pages": "8", "quote": "Standards that are documented and made freely available to the public, which are developed, approved, and maintained via a collaborative and consensus driven process. Open standards facilitate interoperability and data" } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-009", "term": "open standards", "definition": "Standards that are documented and made freely available to the public. Open standards are developed, approved and maintained via a collaborative and consensus-driven process. Open standards facilitate interoperability and data exchange and are intended for widespread adoption (10).", "severity": "wording", "difference": "Near-identical: differs only in phrasing, punctuation or citation markers." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "9789240116191-eng" ] }, { "term": "Operational governance", "definition": "Operational governance manages the day-to-day integrity and performance of the shared infrastructure within the mandate established by strategic governance.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-031-344-operational-governance", "pages": "67-68", "quote": "Operational governance manages the day-to-day integrity and performance of the shared" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "order management", "definition": "The planning, directing, monitoring and controlling of the processes related to customer or requisition orders. Order management includes order promising; order entry; order pick, pack and ship; billing; and reconciliation of the customer account (11).", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-009", "pages": "9", "quote": "The planning, directing, monitoring and controlling of the processes related to customer or requisition orders. Order management includes order promising; order entry; order pick, pack and ship; billing; and reconciliation" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240101197-eng" ] }, { "term": "order management system", "definition": "A paper-based or software tool that supports the processes for fulfilling requisition orders (e.g., a software tool that supports entry and processing of requisition orders from health facilities to regional or central warehouses to replenish inventory).", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-009", "pages": "9", "quote": "A paper-based or software tool that supports the processes for fulfilling requisition orders (e.g., a software tool that supports entry and processing of requisition orders from health facilities to regional" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240101197-eng" ] }, { "term": "organogram", "definition": "A visual representation of an organization’s structure that shows the hierarchy of various roles and reporting relationships.", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-009", "pages": "9", "quote": "A visual representation of an organization’s structure that shows the hierarchy of various roles and reporting relationships." }, { "libraryId": "9789240116191-eng", "sectionId": "page-008", "pages": "8", "quote": "A visual representation of the organization structure showing the hierarchy of various roles and their reporting relationships" } ], "conflictsWith": [ { "libraryId": "9789240116191-eng", "sectionId": "page-008", "term": "Organogram", "definition": "A visual representation of the organization structure showing the hierarchy of various roles and their reporting relationships", "severity": "wording", "difference": "Wording differs (automatic comparison; not reviewed as substantive)." } ], "kind": "glossary", "definedIn": [ "9789240101197-eng", "9789240116191-eng" ] }, { "term": "Outcome", "definition": "An end result or consequence of a set of activities; an outcome is often measurable and signals progress towards a goal.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "An end result or consequence of a set of activities; an outcome is often measurable and signals progress towards a goal." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-025-31-the-architecture-description-approach", "pages": "52-59", "quote": "An achieved, and often measurable, result that signals progress towards a goal." } ], "conflictsWith": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-025-31-the-architecture-description-approach", "term": "Outcome (Table 3.1)", "definition": "An achieved, and often measurable, result that signals progress towards a goal.", "severity": "wording", "difference": "RA glossary: \"An end result or consequence of a set of activities\"; RA Table 3.1: \"An achieved, and often measurable, result\"." } ], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Output", "definition": "In the context of requirements gathering or decision support logic, for each combination of input entries, the output is what will result in the conditions of the rule being met.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "10", "quote": "In the context of requirements gathering or decision support logic, for each combination of input entries, the output is what will result in the conditions of the rule being met." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Pain point", "definition": "A real or perceived problem that end-users experience.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "10", "quote": "A real or perceived problem that end-users experience." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Person-centred", "definition": "In the context of person-centred health services, person-centred refers to prioritizing the comprehensive needs of individuals (i.e. persons, clients, patients, health service users) at the centre of health systems.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "10", "quote": "In the context of person-centred health services, person-centred refers to prioritizing the comprehensive needs of individuals (i.e. persons, clients, patients, health service users) at the centre of health systems." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Person-centred point of service system (PCPOSS)", "definition": "Person-centred point of service system (PCPOSS) are digital systems that facilitate the provision and delivery of health services to individuals (i.e. persons, clients, patients, health service users) at the point of service or point of care.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "10", "quote": "Person-centred point of service system (PCPOSS) are digital systems that facilitate the provision and delivery of health services to individuals (i.e. persons, clients, patients, health service users) at the point" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Point-of-service applications", "definition": "Point-of-service applications are end-user application components (IT systems or software tools) used by individuals directly engaged in healthcare—such as clinicians, community health workers, and patients—that enable interaction with the broader healthcare ecosystem. [Under review]", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "Point-of-service applications are end-user application components (IT systems or software tools) used by individuals directly engaged in healthcare—such as clinicians, community health workers, and patients—that enable interaction with the broader" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Pop-up message", "definition": "A small message that appears on the screen after a triggering event. It can automatically go away after a pre-set time limit or it can be closed by clicking a button. Also sometimes referred to as a “toast message” or “toast notification”.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "10", "quote": "A small message that appears on the screen after a triggering event. It can automatically go away after a pre-set time limit or it can be closed by clicking a" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Product", "definition": "A concrete offering, bundling services and data, that is made available to stakeholders.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "A concrete offering, bundling services and data, that is made available to stakeholders." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-025-31-the-architecture-description-approach", "pages": "52-59", "quote": "A coherent offering that bundles services and data for use by stakeholders." } ], "conflictsWith": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-025-31-the-architecture-description-approach", "term": "Product (Table 3.1)", "definition": "A coherent offering that bundles services and data for use by stakeholders.", "severity": "wording", "difference": "RA glossary \"A concrete offering\" vs Table 3.1 \"A coherent offering\". HOMONYM WARNING: unrelated to \"product\" in the PC handbook (a health product / generic product)." } ], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Product master data (body)", "definition": "Product master data consists of standardized information that accurately describes a health product’s characteristics. This data remains consistent across all instances of a product.", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-010", "pages": "10", "quote": "Product master data consists of standardized information that accurately describes a health product’s characteristics. This data remains consistent across all instances of a product." } ], "conflictsWith": [], "kind": "body", "definedIn": [ "9789240116191-eng" ] }, { "term": "Product Registry", "definition": "The Product Registry is the national authoritative source of core identity and classification data for health products — medicines, vaccines, medical devices, diagnostics, and health commodities — recognised for use within the national health system.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-093-product-registry", "pages": "156-166", "quote": "The Product Registry is the national authoritative source of core identity and classification data for health" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Prototype", "definition": "Prototypes have high fidelity to the end product with options and functionalities that can be tested (see section 4.3).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "10", "quote": "Prototypes have high fidelity to the end product with options and functionalities that can be tested (see section 4.3)." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Public Health Surveillance Platform (PHSP)", "definition": "The Public Health Surveillance Platform is a governed, shared application component for the systematic, ongoing collection, analysis, interpretation, and dissemination of health data to detect, monitor, and respond to public health threats at local, national, and international levels.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-103-public-health-surveillance-platform", "pages": "229-240", "quote": "The Public Health Surveillance Platform is a governed, shared application component for the systematic," } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Realises (relationship)", "definition": "Realises — a capability is realised by the components and services that provide it;", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-025-31-the-architecture-description-approach", "pages": "52-59", "quote": "Realises — a capability is realised by the components and services that provide it;" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Reference Architecture", "definition": "A technology-neutral blueprint that captures the common building blocks, relationships, and design principles of a technical environment.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "A technology-neutral blueprint that captures the common building blocks, relationships, and design principles of a technical environment." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-000-111-what-is-a-reference-architecture-and-why-doe", "pages": "19", "quote": "A reference architecture is a technology-neutral blueprint that captures the common building" } ], "conflictsWith": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-000-111-what-is-a-reference-architecture-and-why-doe", "term": "reference architecture (body, §1.1.1)", "definition": "A reference architecture is a technology-neutral blueprint that captures the common building blocks, relationships, and design principles of a technical environment, so that organisations do not have to start from a blank page.", "severity": "wording", "difference": "Body adds the purpose clause." } ], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "One or more non-primary definitions verified with line-number lines removed" }, { "term": "Reference software", "definition": "Reference software, or applications, provide executable examples of best practices and serve as a starting point containing the software, its documentation, operating manuals, source code, and platform and architecture specifications.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "10", "quote": "Reference software, or applications, provide executable examples of best practices and serve as a starting point containing the software, its documentation, operating manuals, source code, and platform and architecture specifications." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Register", "definition": "In the context of health care, a list of health service users compiled for the purposes of tracking care, aggregating activities or health outcomes, or identifying health service users who need specific interventions.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "11", "quote": "In the context of health care, a list of health service users compiled for the purposes of tracking care, aggregating activities or health outcomes, or identifying health service users who" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Registry", "definition": "A governed, authoritative and centralized information system that captures, stores and maintains the unique attributes and identifiers of health-care facilities, health service users, products and/or health workforce using a predefined canonical minimum data set.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "11", "quote": "A governed, authoritative and centralized information system that captures, stores and maintains the unique attributes and identifiers of health-care facilities, health service users, products and/or health workforce using a predefined" }, { "libraryId": "9789240101197-eng", "sectionId": "page-009", "pages": "9", "quote": "A governed, authoritative and centralized information system that captures, stores and maintains the unique attributes and identifiers of health facilities, health service users, health products and/or the health workforce using" }, { "libraryId": "9789240116191-eng", "sectionId": "page-009", "pages": "9", "quote": "A governed, authoritative and centralized information system that captures, stores, and maintains the unique attributes and identifiers of health facilities, health service users, products and/or health workforce using a predefined" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "A governed, authoritative and centralized information system that captures, stores and maintains the unique attributes and identifiers of health facilities, health service users, health products and/or the health workforce using" } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-009", "term": "registry", "definition": "A governed, authoritative and centralized information system that captures, stores and maintains the unique attributes and identifiers of health facilities, health service users, health products and/or the health workforce using a predefined canonical minimum data set.", "severity": "wording", "difference": "Near-identical: differs only in phrasing, punctuation or citation markers." }, { "libraryId": "9789240116191-eng", "sectionId": "page-009", "term": "Registry", "definition": "A governed, authoritative and centralized information system that captures, stores, and maintains the unique attributes and identifiers of health facilities, health service users, products and/or health workforce using a predefined canonical minimum data set.", "severity": "wording", "difference": "Near-identical: differs only in phrasing, punctuation or citation markers." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "term": "Registry", "definition": "A governed, authoritative and centralized information system that captures, stores and maintains the unique attributes and identifiers of health facilities, health service users, health products and/or the health workforce using a predefined canonical minimum data set. [Under review]", "severity": "wording", "difference": "Near-identical: differs only in phrasing, punctuation or citation markers." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "9789240116191-eng", "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Regulated Trade Item (body, ch. 02)", "definition": "A Regulated Trade Item represents an authorization of a Trade item within a given jurisdiction under a Product Authorization.", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-028", "pages": "28", "quote": "A Regulated Trade Item represents an authorization of a Trade item within a given jurisdiction under a Product Authorization." } ], "conflictsWith": [], "kind": "body", "definedIn": [ "9789240116191-eng" ] }, { "term": "Resilient Essential Data and Digital Health Infrastructure (REDDHI)", "definition": "It is a condition of self- sustaining national digital health maturity that continues to evolve as needs and technology change — one in which the foundational capabilities every health programme depends upon are shared, interoperable, and governed in the public interest rather than duplicated in silos.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-020-22-resilient-essential-data-and-digital-health-i", "pages": "38-39", "quote": "It is a condition of self-" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Rule", "definition": "In the context of a decision-support table, each rule contains input and output entries. The input entries are the condition, and the output entries are the conclusion of the rule.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "11", "quote": "In the context of a decision-support table, each rule contains input and output entries. The input entries are the condition, and the output entries are the conclusion of the rule." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Semantic Governance Infrastructure (SGI)", "definition": "it is the cross-cutting capability that keeps the metadata registry components accurate, consistent and trustworthy, so that the semantic consistency they are intended to provide does not degrade as the health digital ecosystem grows.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-032-345-semantic-governance-infrastructure", "pages": "68-73", "quote": "it is the cross-cutting capability that keeps the metadata registry components accurate," } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Serves (relationship)", "definition": "Serves — a service serves the stakeholders and other elements that use it; and", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-025-31-the-architecture-description-approach", "pages": "52-59", "quote": "Serves — a service serves the stakeholders and other elements that use it; and" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "SMART Guidelines", "definition": "Standards-based, Machine-readable, Adaptive, Requirements-based, and Testable Guidelines are recommended digital capabilities, health and data content aligned with normative recommendations.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "11", "quote": "Standards-based, Machine-readable, Adaptive, Requirements-based, and Testable Guidelines are recommended digital capabilities, health and data content aligned with normative recommendations." }, { "libraryId": "9789240101197-eng", "sectionId": "page-009", "pages": "9", "quote": "The WHO guidelines for developing Standards-based, Machine-readable, Adaptive, Requirements-based and Testable components for implementing digital health capabilities. The components include interoperability standards, code libraries, algorithms, and technical and operational specifications." }, { "libraryId": "9789240116191-eng", "sectionId": "page-009", "pages": "9", "quote": "WHO standards-based, machine-readable, adaptive, requirements-based, and testable Guidelines are recommended digital capabilities, health and data content. They represent a comprehensive set of reusable digital health components (e.g., interoperability standards, code" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "Standards-based, Machine-readable, Adaptive, Requirements-based, Testable Guidelines are a comprehensive set of reusable digital health components (e.g., interoperability standards, code libraries, algorithms, technical and operational specifications) that transform the guideline adaptation" } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-009", "term": "SMART Guidelines", "definition": "The WHO guidelines for developing Standards-based, Machine-readable, Adaptive, Requirements-based and Testable components for implementing digital health capabilities. The components include interoperability standards, code libraries, algorithms, and technical and operational specifications.", "severity": "substantive", "difference": "PHC: \"recommended digital capabilities, health and data content aligned with normative recommendations\"; SC: \"The WHO guidelines for developing\" SMART components; PC and RA: \"a comprehensive set of reusable digital health components\" with a five-step pathway." }, { "libraryId": "9789240116191-eng", "sectionId": "page-009", "term": "SMART Guidelines", "definition": "WHO standards-based, machine-readable, adaptive, requirements-based, and testable Guidelines are recommended digital capabilities, health and data content. They represent a comprehensive set of reusable digital health components (e.g., interoperability standards, code libraries, algorithms, technical and operational specifications) that transform the guideline adaptation and implementation process to preserve fidelity and accelerate uptake.", "severity": "substantive", "difference": "PHC: \"recommended digital capabilities, health and data content aligned with normative recommendations\"; SC: \"The WHO guidelines for developing\" SMART components; PC and RA: \"a comprehensive set of reusable digital health components\" with a five-step pathway." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "term": "SMART Guidelines", "definition": "Standards-based, Machine-readable, Adaptive, Requirements-based, Testable Guidelines are a comprehensive set of reusable digital health components (e.g., interoperability standards, code libraries, algorithms, technical and operational specifications) that transform the guideline adaptation and implementation process to preserve fidelity and accelerate uptake. SMART Guidelines provide a five-step pathway to advance the adoption of best clinical and data practices, even if a country is not yet fully digital.", "severity": "substantive", "difference": "PHC: \"recommended digital capabilities, health and data content aligned with normative recommendations\"; SC: \"The WHO guidelines for developing\" SMART components; PC and RA: \"a comprehensive set of reusable digital health components\" with a five-step pathway." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "9789240116191-eng", "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "SNOMED CT", "definition": "Systematized Nomenclature of Medicine Clinical Terms is a structured clinical terminology standard for use in electronic health records.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "Systematized Nomenclature of Medicine Clinical Terms is a structured clinical terminology standard for use in electronic health records." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "SNOMED GPS", "definition": "Systematized Nomenclature of Medicine – Global Patient Set is a list of basic clinical terms. It is an open and freely accessible subset of SNOMED CT terms that represents the breadth of concepts included in the SNOMED CT International Edition.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "Systematized Nomenclature of Medicine – Global Patient Set is a list of basic clinical terms. It is an open and freely accessible subset of SNOMED CT terms that represents the" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Software platform", "definition": "A software platform is a type of software in which multiple software “products” can be built, and it is advantageous to a software product because it allows for growth in functionality and usability in a more affordable and integrated manner.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "11", "quote": "A software platform is a type of software in which multiple software “products” can be built, and it is advantageous to a software product because it allows for growth in" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Solution Architecture", "definition": "The design of a specific application component or HDPI expressed through specifications and diagrams [Under review]", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "The design of a specific application component or HDPI expressed through specifications and diagrams [Under review]" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "stakeholder", "definition": "In the context of digital health transformation, anyone who is affected by or interested in the consequences of the efforts, including the planning team, end users, beneficiaries and funders.", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-009", "pages": "9", "quote": "In the context of digital health transformation, anyone who is affected by or interested in the consequences of the efforts, including the planning team, end users, beneficiaries and funders." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "An individual, role, or organisation with an interest in the outcomes of the architecture." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-025-31-the-architecture-description-approach", "pages": "52-59", "quote": "An individual, role, or organisation with an interest in the architecture and its outcomes." } ], "conflictsWith": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "term": "Stakeholder", "definition": "An individual, role, or organisation with an interest in the outcomes of the architecture.", "severity": "substantive", "difference": "SC: \"anyone who is affected by or interested in the consequences of the efforts\"; RA glossary: \"An individual, role, or organisation with an interest in the outcomes of the architecture\"; RA Table 3.1: \"...in the architecture and its outcomes\"." }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-025-31-the-architecture-description-approach", "term": "Stakeholder (Table 3.1)", "definition": "An individual, role, or organisation with an interest in the architecture and its outcomes.", "severity": "substantive", "difference": "SC: \"anyone who is affected by or interested in the consequences of the efforts\"; RA glossary: \"An individual, role, or organisation with an interest in the outcomes of the architecture\"; RA Table 3.1: \"...in the architecture and its outcomes\"." } ], "kind": "glossary", "definedIn": [ "9789240101197-eng", "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Strategic governance", "definition": "Strategic governance provides the authoritative direction for the shared infrastructure.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-030-343-strategic-governance", "pages": "65-67", "quote": "Strategic governance provides the authoritative direction for the shared infrastructure." } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Subsidiarity (governance principle)", "definition": "Subsidiarity. Decision authority should sit at the lowest level at which it can be exercised effectively.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-029-342-governance-principles", "pages": "65", "quote": "Subsidiarity. Decision authority should sit at the lowest level at which it can be exercised" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Supplier Registry", "definition": "The Supplier Registry is the authoritative master data source for identity, classification, and regulatory status of suppliers engaged in the health supply chain", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-099-supplier-registry", "pages": "202-210", "quote": "The Supplier Registry is the authoritative master data source for identity, classification, and regulatory" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Systems architecture", "definition": "The technical framework of the system depicted in a conceptual model that defines how the system is structured and how its elements are connected.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "11", "quote": "The technical framework of the system depicted in a conceptual model that defines how the system is structured and how its elements are connected." }, { "libraryId": "9789240093362-eng", "sectionId": "sec-023-44-design-system-architecture", "pages": "56-60", "quote": "A system architecture is a conceptual model that depicts how the PCPOSS will be structured and how it functions and includes all the software and hardware components that comprise the" }, { "libraryId": "9789240101197-eng", "sectionId": "page-009", "pages": "9", "quote": "A technical framework based on a conceptual model that defines how the system should be structured and how its elements should be connected." } ], "conflictsWith": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-023-44-design-system-architecture", "term": "System architecture (body, §4.4)", "definition": "A system architecture is a conceptual model that depicts how the PCPOSS will be structured and how it functions and includes all the software and hardware components that comprise the system.", "severity": "wording", "difference": "PHC: \"how the system is structured\"; SC: \"how the system should be structured\"; PHC section 4.4 body widens it to \"all the software and hardware components\"." }, { "libraryId": "9789240101197-eng", "sectionId": "page-009", "term": "systems architecture", "definition": "A technical framework based on a conceptual model that defines how the system should be structured and how its elements should be connected.", "severity": "wording", "difference": "PHC: \"how the system is structured\"; SC: \"how the system should be structured\"; PHC section 4.4 body widens it to \"all the software and hardware components\"." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng" ] }, { "term": "Technical Debt", "definition": "Technical debt in software development and systems architecture describes the risk of taking shortcuts and making short-term fixes, which later require costly revisions and add-ons; rather than investing in carefully designed, robust solutions, which may cost more upfront, but have lower maintenance and feature development costs over time (11).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "11", "quote": "Technical debt in software development and systems architecture describes the risk of taking shortcuts and making short-term fixes, which later require costly revisions and add-ons; rather than investing in carefully" } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Terminology Service", "definition": "The Terminology Service is a governed, publicly accessible service that manages, publishes, and provides access to the standardised terminologies, code systems, value sets, and concept maps used across the digital health ecosystem.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-095-terminology-service", "pages": "175-183", "quote": "The Terminology Service is a governed, publicly accessible service that manages, publishes, and provides" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "To-be", "definition": "The determined future state (also see as-is).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "11", "quote": "The determined future state (also see as-is)." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "total cost of ownership", "definition": "The resources required to support a digital health intervention throughout its life cycle.", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-009", "pages": "9", "quote": "The resources required to support a digital health intervention throughout its life cycle." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240101197-eng" ] }, { "term": "traceability", "definition": "The ability to trace something. In some cases, it is interpreted as the ability to verify the history, location or application of an item by means of documented identification (14).", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-009", "pages": "9", "quote": "The ability to trace something. In some cases, it is interpreted as the ability to verify the history, location or application of an item by means of documented identification (14)." }, { "libraryId": "9789240101197-eng", "sectionId": "page-054", "pages": "54", "quote": "The global standards organization GS1 describes traceability as the ability “to see the movement of health products across the supply chain” (25)." } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-054", "term": "traceability (body, GS1)", "definition": "The global standards organization GS1 describes traceability as the ability “to see the movement of health products across the supply chain” (25).", "severity": "internal", "difference": "SC glossary: \"The ability to trace something\" (verify history, location or application); SC Chapter 4 body quotes GS1: the ability \"to see the movement of health products across the supply chain\"." } ], "kind": "glossary", "definedIn": [ "9789240101197-eng" ] }, { "term": "traceability models (centralized, semi-centralized, distributed)", "definition": "The centralized model involves a single database or repository for storing all traceability data. In a semi- centralized model, the traceability data are spread across multiple databases or repositories. In the distributed model, traceability data are maintained separately by each supply chain partner.", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-054", "pages": "54", "quote": "The centralized model involves a single database or repository for storing all traceability data. In a semi- centralized model, the traceability data are spread across multiple databases or repositories. In" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "9789240101197-eng" ] }, { "term": "Trade item", "definition": "Products or services that are priced, ordered or invoiced at any point in the supply chain.13", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-009", "pages": "9", "quote": "Products or services that are priced, ordered or invoiced at any point in the supply chain.13" }, { "libraryId": "9789240116191-eng", "sectionId": "page-028", "pages": "28", "quote": "Trade items are manufacturer-specific branded health products that are identifiable and unique to a particular brand or manufacturer." } ], "conflictsWith": [ { "libraryId": "9789240116191-eng", "sectionId": "page-028", "term": "Trade item (body, ch. 02)", "definition": "Trade items are manufacturer-specific branded health products that are identifiable and unique to a particular brand or manufacturer.", "severity": "internal", "difference": "PC glossary (GS1): \"Products or services that are priced, ordered or invoiced\"; PC Chapter 02 body: \"manufacturer-specific branded health products\"." } ], "kind": "glossary", "definedIn": [ "9789240116191-eng" ] }, { "term": "Transaction", "definition": "A transaction — a fully specified machine-to-machine protocol exchange, with defined trigger events, message semantics, and expected actions — is one kind of Application Interaction: its precise, specifiable subset.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-048-372-the-model", "pages": "90-94", "quote": "A transaction — a fully specified machine-to-machine protocol exchange, with defined trigger" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ], "definitionNote": "RA draft interleaves a line number on its own line; the definition is verbatim with those number-only lines removed" }, { "term": "Transactional data (body)", "definition": "In contrast, transactional data—such as batch numbers, manufacturing dates, and serial numbers—varies with each specific instance of the product.", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-010", "pages": "10", "quote": "In contrast, transactional data—such as batch numbers, manufacturing dates, and serial numbers—varies with each specific instance of the product." } ], "conflictsWith": [], "kind": "body", "definedIn": [ "9789240116191-eng" ] }, { "term": "Trigger event", "definition": "An event recorded in the system that will start the execution of relevant subsequent operations.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "11", "quote": "An event recorded in the system that will start the execution of relevant subsequent operations." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Triggering (relationship)", "definition": "A causal \"leads to\" between behaviours", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-048-372-the-model", "pages": "90-94", "quote": "A causal \"leads to\" between behaviours" } ], "conflictsWith": [], "kind": "body", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "Use case", "definition": "A use case is an example scenario of how the end-user will use the system.", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "11", "quote": "A use case is an example scenario of how the end-user will use the system." }, { "libraryId": "9789240101197-eng", "sectionId": "page-009", "pages": "9", "quote": "An example scenario of how the end user will use a system." } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-009", "term": "use case", "definition": "An example scenario of how the end user will use a system.", "severity": "wording", "difference": "Wording differs (automatic comparison; not reviewed as substantive)." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240101197-eng" ] }, { "term": "User acceptance testing", "definition": "User acceptance testing (UAT) is conducted to see whether the end-users are satisfied with the end product (24).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "11", "quote": "User acceptance testing (UAT) is conducted to see whether the end-users are satisfied with the end product (24)." }, { "libraryId": "9789240116191-eng", "sectionId": "page-009", "pages": "9", "quote": "UAT is done to see whether the end-users are satisfied with the end product.14" } ], "conflictsWith": [ { "libraryId": "9789240116191-eng", "sectionId": "page-009", "term": "User acceptance testing (UAT)", "definition": "UAT is done to see whether the end-users are satisfied with the end product.14", "severity": "wording", "difference": "Wording differs (automatic comparison; not reviewed as substantive)." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng", "9789240116191-eng" ] }, { "term": "User persona", "definition": "A generic or archetypical profile of an end-user that is representative of a single type of end-user.", "status": "overlaps:smart-base/docs/artifact/StructureDefinition-GenericPersona.md", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "11", "quote": "A generic or archetypical profile of an end-user that is representative of a single type of end-user." }, { "libraryId": "9789240093362-eng", "sectionId": "sec-013-32-get-to-know-the-users", "pages": "33-35", "quote": "A user persona is a generic depiction of a relevant stakeholder, or end-user of the system who would be interacting with the PCPOSS." } ], "conflictsWith": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-013-32-get-to-know-the-users", "term": "User persona (body, §3.2.1)", "definition": "A user persona is a generic depiction of a relevant stakeholder, or end-user of the system who would be interacting with the PCPOSS.", "severity": "wording", "difference": "Glossary: profile \"of an end-user\"; section 3.2.1: depiction \"of a relevant stakeholder, or end-user\"." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "User story", "definition": "Captures a long list of features from an end-user’s perspective. It describes who the end-user is, with their feature wants or needs, and the reason for that want or need (see section 3.2.3).", "status": "overlaps:folio-assistant-core/glossary/cat-harness.glossary.json", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "11", "quote": "Captures a long list of features from an end-user’s perspective. It describes who the end-user is, with their feature wants or needs, and the reason for that want or need" } ], "conflictsWith": [ { "repository": "folio-assistant-core/glossary/cat-harness.glossary.json", "term": "user story", "definition": "What a reader acting in a Role is trying to do, told as that role: as a , I want , so that . (truncated)", "severity": "wording", "difference": "Compatible template; PHC binds the story to a user PERSONA (\"As a... [user persona]\"), the platform to a Role." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Value", "definition": "The benefit or utility a stakeholder gains from using a service, product, or capability.", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "The benefit or utility a stakeholder gains from using a service, product, or capability." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "warehouse management system", "definition": "A computer application that manages and optimizes workflows and the storage of goods within a warehouse. It often interfaces with automated data capture and enterprise resource planning systems (11).", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-009", "pages": "9", "quote": "A computer application that manages and optimizes workflows and the storage of goods within a warehouse. It often interfaces with automated data capture and enterprise resource planning systems (11)." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240101197-eng" ] }, { "term": "Wireframes", "definition": "Low fidelity outlines that depict the overall design ideas and flow of the final product (see section 4.3).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "11", "quote": "Low fidelity outlines that depict the overall design ideas and flow of the final product (see section 4.3)." } ], "conflictsWith": [], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "Workflow", "definition": "The sequence of activities from one task to another (see section 3.3).", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-002-glossary", "pages": "11", "quote": "The sequence of activities from one task to another (see section 3.3)." }, { "libraryId": "9789240093362-eng", "sectionId": "sec-014-33-map-business-processes-and-workflows", "pages": "35-39", "quote": "Workflows are a visual representation of the progression of activities (tasks, events, interactions) performed within a business process (45)." } ], "conflictsWith": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-014-33-map-business-processes-and-workflows", "term": "Workflow (body, §3.3)", "definition": "Workflows are a visual representation of the progression of activities (tasks, events, interactions) performed within a business process (45).", "severity": "internal", "difference": "PHC glossary: \"The sequence of activities from one task to another\"; PHC section 3.3 body: \"a visual representation of the progression of activities\" within a business process." } ], "kind": "glossary", "definedIn": [ "9789240093362-eng" ] }, { "term": "AEFI", "definition": "Adverse effects following immunisation", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "AEFI Adverse effects following immunisation" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "AI", "definition": "Artificial Intelligence", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "AI Artificial Intelligence" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "AIDC", "definition": "Automatic identification and data capture", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "AIDC Automatic identification and data capture" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "ANC", "definition": "antenatal care", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "ANC antenatal care" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "API", "definition": "application programming interface", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "API application programming interface" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "ATC", "definition": "Anatomical therapeutic chemical classification system", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "ATC Anatomical therapeutic chemical classification system" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "BPMN", "definition": "Business Process Model and Notation", "status": "overlaps:cat-harness/skills/process/workflow/bpmn-authoring.md", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "BPMN Business Process Model and Notation" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "CRDM", "definition": "Collaborative Requirements Development Methodology", "status": "overlaps:cat-harness/skills/sdlc/crdm/crdm-requirements-workflow.md", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "CRDM Collaborative Requirements Development Methodology" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "DAK", "definition": "Digital adaptation kit", "status": "overlaps:smart-base/docs/artifact/StructureDefinition-DAK.md", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "DAK Digital adaptation kit" }, { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "DAK Digital adaptation kit" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng", "9789240116191-eng" ] }, { "term": "DBP", "definition": "diastolic blood pressure", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "DBP diastolic blood pressure" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "DH&I", "definition": "Digital health and interoperability", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "DH&I Digital health and interoperability" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "DH&I WG", "definition": "Digital Health and Interoperability Working Group", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "DH&I WG Digital Health and Interoperability Working Group" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng" ] }, { "term": "DHA", "definition": "Digital Health Atlas", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "DHA Digital Health Atlas" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "DHSC", "definition": "digital health supply chain", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "DHSC digital health supply chain" }, { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "DHSC Digital health supply chain" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng", "9789240116191-eng" ] }, { "term": "DICOM", "definition": "Digital Imaging and Communications in Medicine", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "DICOM Digital Imaging and Communications in Medicine" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "DIIG", "definition": "Digital Implementation Investment Guide", "status": "overlaps:smart-base/methodologies/diig.md", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "DIIG Digital Implementation Investment Guide" }, { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "DIIG Digital Implementation Investment Guide" }, { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "DIIG Digital implementation investment guide" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "DIIG Digital Implementation Investment Guide" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "9789240116191-eng", "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "DPI", "definition": "Digital Public Infrastructure", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "DPI Digital Public Infrastructure" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "DPI-F", "definition": "Foundational Digital Public Infrastructure", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "DPI-F Foundational Digital Public Infrastructure" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "DPI-H", "definition": "Health Digital Public Infrastructure", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "DPI-H Health Digital Public Infrastructure" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "EA", "definition": "enterprise architecture", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "EA enterprise architecture" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "eLMIS", "definition": "Electronic logistic management information system", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "eLMIS Electronic logistic management information system" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "eRIS", "definition": "Electronic Regulatory Information System", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "eRIS Electronic Regulatory Information System" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng" ] }, { "term": "ERP", "definition": "enterprise resource planning", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "ERP enterprise resource planning" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng" ] }, { "term": "FDA", "definition": "Food and Drugs Authority", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "FDA Food and Drugs Authority" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "FHIR", "definition": "Fast Healthcare Interoperability Resources", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "FHIR Fast Healthcare Interoperability Resources" }, { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "FHIR Fast Healthcare Interoperability Resources®" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng", "9789240116191-eng" ] }, { "term": "FTE", "definition": "full-time equivalent", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "FTE full-time equivalent" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng" ] }, { "term": "GDSN", "definition": "Global Data Synchronisation Network", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "GDSN Global Data Synchronisation Network" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "GFPVAN", "definition": "Global Family Planning Visibility and Analytics Network", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "GFPVAN Global Family Planning Visibility and Analytics Network" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng" ] }, { "term": "GHSC-PSM", "definition": "Global Health Supply Chain Program–Procurement and Supply Management", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "GHSC-PSM Global Health Supply Chain Program–Procurement and Supply Management" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng" ] }, { "term": "GTIN", "definition": "Global trade item number", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "GTIN Global trade item number" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "HL7", "definition": "Health Level Seven", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "HL7 Health Level Seven" }, { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "HL7 Health Level Seven®" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng", "9789240116191-eng" ] }, { "term": "HL7 FHIR®", "definition": "Health Level Seven Fast Healthcare Interoperability Resources", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "HL7 FHIR® Health Level Seven Fast Healthcare Interoperability Resources" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "HRP", "definition": "UNDP-UNFPA-UNICEF-WHO-World Bank Special Programme of Research, Development and Research Training in Human Reproduction", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "HRP UNDP-UNFPA-UNICEF-WHO-World Bank Special Programme of Research, Development and Research Training in Human Reproduction" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "HSCIS", "definition": "health supply chain information system", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "HSCIS health supply chain information system" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng" ] }, { "term": "HTSS", "definition": "Health Technical Support Services", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "HTSS Health Technical Support Services" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng" ] }, { "term": "ICD-11", "definition": "International Classification of Diseases, 11th Revision", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "ICD-11 International Classification of Diseases, 11th Revision" }, { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "ICD-11 International classification of diseases, 11th Revision" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "ICD-11 International Classification of Diseases 11th Revision" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng", "9789240116191-eng", "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "ICF", "definition": "International Classification of Functioning, Disability and Health", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "ICF International Classification of Functioning, Disability and Health" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "ICHI", "definition": "International Classification of Health Interventions", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "ICHI International Classification of Health Interventions" }, { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "ICHI International classification of health interventions" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng", "9789240116191-eng" ] }, { "term": "ICT", "definition": "information and communications technology", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "ICT information and communications technology" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng" ] }, { "term": "ICVP", "definition": "International Certificate of Vaccination or Prophylaxis", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "ICVP International Certificate of Vaccination or Prophylaxis" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "ID", "definition": "identity/identification", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "ID identity/identification" }, { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "ID Identity/identification" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng", "9789240116191-eng" ] }, { "term": "IDMP", "definition": "Identification of medicinal products – a suite of five standards developed within the International Organization for Standardization (ISO) to facilitate the unique identification of medicinal products", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "IDMP Identification of medicinal products – a suite of five standards developed within the International Organization for Standardization (ISO) to facilitate the unique identification of medicinal products" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "IHE", "definition": "Integrating the Healthcare Enterprise", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "IHE Integrating the Healthcare Enterprise" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "INN", "definition": "International non-proprietary name", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "INN International non-proprietary name" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "IPS", "definition": "International Patient Summary", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "IPS International Patient Summary" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "IT", "definition": "information technology", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "IT information technology" }, { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "IT information technology" }, { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "IT Information technology" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "9789240116191-eng" ] }, { "term": "ITU", "definition": "International Telecommunications Union", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "ITU International Telecommunications Union" }, { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "ITU International Telecommunication Union" } ], "conflictsWith": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "term": "ITU", "definition": "International Telecommunication Union", "severity": "wording", "difference": "PHC \"Telecommunications\" vs SC \"Telecommunication\" (the organisation's own name is singular)." } ], "kind": "abbreviation", "definedIn": [ "9789240093362-eng", "9789240101197-eng" ] }, { "term": "JSON", "definition": "JavaScript Object Notation", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "JSON JavaScript Object Notation" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "KPI", "definition": "key performance indicator", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "KPI key performance indicator" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng" ] }, { "term": "LMIC", "definition": "Low-and-Middle-Income Country", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "LMIC Low-and-Middle-Income Country" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "LOINC", "definition": "Logical Observation Identifiers Names and Codes", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "LOINC Logical Observation Identifiers Names and Codes" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "LOINC Logical Observation Identifiers Names and Codes" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng", "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "MAPS", "definition": "mHealth assessment and planning for scale", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "MAPS mHealth assessment and planning for scale" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "MOH", "definition": "ministry of health", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "MOH ministry of health" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng" ] }, { "term": "MVP", "definition": "minimum viable product", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "MVP minimum viable product" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "NAFDAC", "definition": "National Agency for Food and Drug Administration and Control", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "NAFDAC National Agency for Food and Drug Administration and Control" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "NGO", "definition": "Non-governmental organisation", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "NGO Non-governmental organisation" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "NPC", "definition": "National Product Catalog", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "NPC National Product Catalog" }, { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "NPC National product catalog" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng", "9789240116191-eng" ] }, { "term": "NRA", "definition": "National Regulatory Authority", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "NRA National Regulatory Authority" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "NSCA", "definition": "National Supply Chain Assessment", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "NSCA National Supply Chain Assessment" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng" ] }, { "term": "OpenHIE", "definition": "Open Health Information Exchange", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "OpenHIE Open Health Information Exchange" }, { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "OpenHIE Open Health Information Exchange" }, { "libraryId": "9789240116191-eng", "sectionId": "page-006", "pages": "6", "quote": "OpenHIE Open Health Information Exchange" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "OpenHIE Open Health Information Exchange" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "9789240116191-eng", "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "PCMT", "definition": "Product catalog management tool", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "PCMT Product catalog management tool" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "PCPOSS", "definition": "Person-centred point of service system", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "PCPOSS Person-centred point of service system" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "PHC", "definition": "primary health care", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "PHC primary health care" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "POS", "definition": "point of service", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "POS point of service" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "QA", "definition": "quality assurance", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "QA quality assurance" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng" ] }, { "term": "REDDHI", "definition": "Resilient Essential Data and Digital Health Infrastructure", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "REDDHI Resilient Essential Data and Digital Health Infrastructure" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "RFP", "definition": "request for proposal", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "RFP request for proposal" }, { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "RFP Request for proposal" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng", "9789240116191-eng" ] }, { "term": "RFQ", "definition": "request for quotation", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "RFQ request for quotation" }, { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "RFQ Request for quote" } ], "conflictsWith": [ { "libraryId": "9789240116191-eng", "sectionId": "page-007", "term": "RFQ", "definition": "Request for quote", "severity": "wording", "difference": "SC \"request for quotation\" vs PC \"Request for quote\"." } ], "kind": "abbreviation", "definedIn": [ "9789240101197-eng", "9789240116191-eng" ] }, { "term": "RMS", "definition": "Rwanda Medical Supply Ltd.", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "RMS Rwanda Medical Supply Ltd." } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "SBP", "definition": "systolic blood pressure", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "SBP systolic blood pressure" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "SCISMM", "definition": "Supply Chain Information System Maturity Model", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "SCISMM Supply Chain Information System Maturity Model" }, { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "SCISMM Supply chain information systems maturity model" } ], "conflictsWith": [ { "libraryId": "9789240116191-eng", "sectionId": "page-007", "term": "SCISMM", "definition": "Supply chain information systems maturity model", "severity": "wording", "difference": "SC \"Supply Chain Information System Maturity Model\" vs PC \"Supply chain information systems maturity model\"." } ], "kind": "abbreviation", "definedIn": [ "9789240101197-eng", "9789240116191-eng" ] }, { "term": "SCSA", "definition": "Supply Chain Systems Architecture", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "SCSA Supply Chain Systems Architecture" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng" ] }, { "term": "SDG", "definition": "Sustainable Development Goals", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "SDG Sustainable Development Goals" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "SDG Sustainable Development Goal" } ], "conflictsWith": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "term": "SDG", "definition": "Sustainable Development Goal", "severity": "wording", "difference": "PHC plural \"Goals\" vs RA singular \"Goal\"." } ], "kind": "abbreviation", "definedIn": [ "9789240093362-eng", "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "SMART", "definition": "Standards-based, Machine-readable, Adaptive, Requirements-based and Testable", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "SMART Standards-based, Machine-readable, Adaptive, Requirements-based and Testable" }, { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "SMART Standards-based, machine-readable, adaptive, requirements-based and testable" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng", "9789240116191-eng" ] }, { "term": "SMART Guidelines", "definition": "Standards-based, Machine-readable, Adaptive, Requirements-based, Testable Guidelines", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "SMART Guidelines Standards-based, Machine-readable, Adaptive, Requirements-based, Testable Guidelines" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "SNOMED CT", "definition": "Systematized Nomenclature of Medicine - Clinical Terms", "status": "new", "sources": [ { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "SNOMED CT Systematized Nomenclature of Medicine - Clinical Terms" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "SNOMED-GPS", "definition": "Systematized Nomenclature of Medicine-Global Patient Set", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "SNOMED-GPS Systematized Nomenclature of Medicine-Global Patient Set" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "SNOMED GPS Systematized Nomenclature of Medicine – Global Patient Set" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng", "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "SOP", "definition": "Standard operating procedure", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "SOP Standard operating procedure" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "SWG", "definition": "Small working group", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "SWG Small working group" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "TOGAF", "definition": "The Open Group Architecture Framework", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "TOGAF The Open Group Architecture Framework" }, { "libraryId": "who-dpi-h-reference-architecture-draft-v1", "sectionId": "sec-front-matter", "pages": "1-19", "quote": "TOGAF The Open Group Architecture Framework" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng", "who-dpi-h-reference-architecture-draft-v1" ] }, { "term": "TOR", "definition": "Terms of reference", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "TOR Terms of reference" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "TSS", "definition": "Target Software Standards", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "TSS Target Software Standards" }, { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "TSS Target Software Standards" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng", "9789240116191-eng" ] }, { "term": "TWG", "definition": "technical working group", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "TWG technical working group" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng" ] }, { "term": "UAT", "definition": "user acceptance testing", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "UAT user acceptance testing" }, { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "UAT User acceptance testing" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng", "9789240116191-eng" ] }, { "term": "UI", "definition": "user interface", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "UI user interface" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "UMC", "definition": "Uppsala Monitoring Centre", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "UMC Uppsala Monitoring Centre" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "USAID", "definition": "United States Agency for International Development", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "USAID United States Agency for International Development" }, { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "USAID United States Agency for International Development" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng", "9789240116191-eng" ] }, { "term": "USAID GHSC-PSM", "definition": "USAID Global Health Supply Chain Program-Procurement and Supply Management", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "USAID GHSC-PSM USAID Global Health Supply Chain Program-Procurement and Supply Management" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "WHO", "definition": "World Health Organization", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "WHO World Health Organization" }, { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "WHO World Health Organization" }, { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "WHO World Health Organization" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng", "9789240101197-eng", "9789240116191-eng" ] }, { "term": "WHO-FIC", "definition": "WHO Family of International Classifications and Terminologies", "status": "new", "sources": [ { "libraryId": "9789240093362-eng", "sectionId": "sec-001-abbreviations", "pages": "7-8", "quote": "WHO-FIC WHO Family of International Classifications and Terminologies" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240093362-eng" ] }, { "term": "WHODrug", "definition": "International reference for medicinal product information, maintained by the Swedish foundation, UMC", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "WHODrug International reference for medicinal product information, maintained by the Swedish foundation, UMC" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "WMS", "definition": "warehouse management system", "status": "new", "sources": [ { "libraryId": "9789240101197-eng", "sectionId": "page-007", "pages": "7", "quote": "WMS warehouse management system" }, { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "WMS Warehouse management system" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240101197-eng", "9789240116191-eng" ] }, { "term": "ZAMMSA", "definition": "Zambia Medicines and Medical Supplies Agency", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "ZAMMSA Zambia Medicines and Medical Supplies Agency" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] }, { "term": "ZAMRA", "definition": "Zambia Medicines Regulatory Authority", "status": "new", "sources": [ { "libraryId": "9789240116191-eng", "sectionId": "page-007", "pages": "7", "quote": "ZAMRA Zambia Medicines Regulatory Authority" } ], "conflictsWith": [], "kind": "abbreviation", "definedIn": [ "9789240116191-eng" ] } ], "notes": "CANDIDATE LIST ONLY - nothing has been authored. Built 2026-10-02 from the ingested library entries in smart-base/library (9789240093362-eng PHC handbook, section-granular; 9789240101197-eng supply-chain handbook and 9789240116191-eng product-catalogue handbook, both PAGE-granular so sectionId is page-NNN and pages is that PDF page; who-dpi-h-reference-architecture-draft-v1, a DRAFT V1.0, section-granular). pages are PDF page numbers taken from each section file's front matter (PHC glossary terms are refined to the single PDF page, 8-11). Every quote was verified programmatically as a whitespace-normalised substring of its section file and is <=30 words; typographic quotes/dashes were matched leniently and then replaced by the exact source characters. The RA draft carries a line number on its own line between every text line, so RA quotes are kept within one source line (some therefore start or end mid-sentence); multi-line RA definitions are verbatim with those number-only lines removed (flagged per entry in definitionNote). The RA glossary is inside sec-front-matter (pages 1-19 as a whole). Counts: 16 methodologies, 24 processes, 241 glossary entries (94 abbreviations, 100 glossary-section terms, 47 body-defined terms, mostly from the RA); 40 entries carry conflictsWith, 14 of them substantive or internal. Glossary entries are merged by term across handbooks: definition is the first source in the order PHC, SC, PC, RA; every other differing definition is in conflictsWith with a severity (substantive = different meaning or an added claim; internal = one handbook defines it two ways; wording = paraphrase). Extra fields beyond the requested shape: glossary kind/definedIn/definitionNote; process notes; step objects carry n/name and, for supply-chain and product-catalogue steps, inputs/tasks/outputs as the handbooks tabulate them. Status rules: overlaps: = an existing repo artefact covers the same ground (not a copy); extends: = the source declares itself built on that artefact's method. Key repo findings: (1) dth-dhsc-challenge-prioritization (SC Annex 3) SUMS three 1-3 scores to rank bottlenecks - the exact arithmetic smart-base/methodologies/diig.md adopts the criteria of and REFUSES; (2) the seven-phase \"planning and implementing a digital health enterprise\" figure is reproduced by all three handbooks and is a DIIG view that diig.md does not render; (3) PHC Chapter 3 maps almost one-to-one onto smart-base/processes/l2-dak-authoring.bpmn (personas, BPMN, data dictionary, DMN, indicators/requirements) and touches CRDM; (4) RA \"actor\" (abstract role realised by systems) collides with the platform glossary's \"actor\" (concrete participant that takes on roles). Source defects recorded: SC Chapter 1 says \"five steps\" but has four; PC chapter 04 title differs between contents and body, and PC chapter numbering differs between contents (01-08) and \"How to use\" (1-7); PC Chapter 05 Step 3 repeats Step 2 rows; RA glossary leaves \"Health Information Exchange\" and \"Repository\" undefined and marks several terms [Under review]; RA section 1.5 footnote points to \"Annex [X]\". Out of scope and not listed: the DAK clinical workflows reproduced as figures (ANC registration, ANC contact), which are DAK content, not handbook processes; country examples; the RA Appendix C functional-requirement tables (component-level requirements, not processes). Figures are vector text; where a step list came only from a figure it is marked as such." }