Glossary: dpi-h-ra
The glossaries dpi-h-ra owns: Acronyms used in the DPI-H reference architecture (18 terms, SKOS) · Glossary of the Reference Architecture and Guidance for DPI-H (178 terms, SKOS) · Full-STAC: open Standards, Technologies, Architectures and Content (10 terms, SKOS). Every other instance’s terms, the counts and the sources are on the glossary index.
Size: this page holds 206 terms and is 339 KB before compression, within its budget of 1.0 MB. There is no search index: the filter below runs over this page, and the A–Z bar jumps within it.
206 shown
A
-
Access Point
APcandidate -
A participating organisation's own connection point in a distributed model.
Expanded and defined in the legend of Table 3.6 (Illustrative health information exchange mechanisms). A candidate until the RA editors adopt it through the public review.
- Actor (Conformance Model) candidate
-
An Actor is an abstract, well-bounded role in the health information ecosystem that is defined entirely by the information-processing responsibilities it assumes and the interactions it participates in. An Actor is neither a software product nor an organisational unit.
Defined in RA §3.7.2 (library/who-dpi-h-reference-architecture-draft-v1/sections/sec-050-372-the-model.md, p. 111–116). Substantive distinction from the platform's `actor` concept in folio-assistant-core/glossary/cat-harness.glossary.json ("A concrete participant, human, agentic or mechanical, that persists across every process and takes on roles"): the RA's conformance-model Actor is an abstract information-processing role realised by concrete systems, closer to IHE's Actor or the platform's Role (smart-ra#133 S1).
-
Adverse Events Following Immunization
AEFIcandidate -
Adverse effects following immunisation
Recorded per smart-ra#142 item 4: the PC handbook abbreviations list (who-iris/library/9789240116191-eng/sections/page-006.md, p. 6) expands AEFI as "Adverse effects following immunisation", whereas standard WHO immunization terminology expands AEFI as "Adverse events following immunization" (an 'event' is any untoward medical occurrence following immunization and does not presuppose a causal 'effect'). Both expansions are recorded as candidates; neither is silently altered.
-
Aggregate Data Exchange
ADXcandidate -
No definition yet.
Used in Appendix C (Health Management Information System, HMISF-4) for the IHE QRPH Aggregate Data Exchange (ADX) profile. Expansion supplied; check in context. A candidate: no definition has been written.
-
Anatomical Therapeutic Chemical Classification
ATCcandidate -
No definition yet.
Expanded in Appendix C (Terminology Service and Product Registry) as the WHO classification system for active substances of medicines. Shared with dth-pc and dth-sfp. A candidate: no definition has been written.
-
Antenatal Care
ANCcandidate -
No definition yet.
Used in Appendix C (Health Facility Registry) and shared across the Digital Transformation Handbooks. Expansion supplied; check in context. A candidate: no definition has been written.
- Application Component candidate
-
A deployable, modular piece of software that provides a defined set of functionality and holds the data it manages, exposing both through services.
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Application Component ; views: Metamodel, Metamodel vs EIRA, Testing
-
Application Programming Interface
APIcandidate -
No definition yet.
Used throughout the RA draft and Digital Transformation Handbooks for machine-readable service interfaces. Expansion supplied; check in context. A candidate: no definition has been written.
- Application Service candidate
-
An explicitly defined unit of application behaviour. Anch application service exposes the functionality of an application component to its environment.
The RA draft's own glossary wording, verbatim (folio/dpi-h-ra/glossary/t-glossary-lead-a31853.md). Wording alternative in RA Table 3.1 (library/who-dpi-h-reference-architecture-draft-v1/sections/sec-026-31-the-architecture-description-approach.md): "An externally visible unit of functionality provided by one or more components, exposed through well-defined interfaces." Both are recorded as candidates; neither is chosen (smart-ra#133 S1).
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Application Service ; views: Metamodel, Metamodel vs EIRA, Testing
- ArchiMate candidate
-
An open enterprise architecture modelling language, published by The Open Group, for describing and visualising an architecture across business, application and technology layers. The models in this guidance are written in ArchiMate.
Added to the RA glossary table in CS-001 (smart-ra#185, public comments No. 136 and No. 327), per committee feedback (CL). A candidate until the RA editors adopt it through the public review.
-
Artificial Intelligence
AIcandidate -
No definition yet.
-
Artificial Intelligence
AIcandidate -
No definition yet.
Named in the RA draft's Acronyms table, which gives the expansion used as prefLabel. Discussed in Section 5.2 (AI and DPI-H). A candidate: no definition has been written.
B
-
Benefits Package Registry
BPRcandidate -
The Benefits Package Registry is the national authoritative record of all health benefit packages offered within a country's health financing ecosystem. It holds the definitive description of what each package covers, who is eligible in general terms, which scheme or schemes offer it, and under what rules and conditions benefits may be accessed.
Verbatim lead sentences from Appendix C (Benefits Package Registry, 1 What It Is). Abbreviated BPR in the Appendix C comparison table. A candidate until the RA editors adopt it through the public review.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Benefits Package Registry ; views: DPI-H Reference Architecture — Integrated View (Fig. 3.2), DPI-H Reference Architecture — DPI-H layers (Fig. 3.5)
- Business Domain candidate
-
A specific focus area or subsystem within a broader business system, characterized by its own essential attributes
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review. The draft marks this entry [Under review].
- Business Process candidate
-
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).
PHC handbook glossary wording, verbatim (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 8). Wording alternative in SFP handbook glossary (who-iris/library/9789240120747-eng/sections/page-009.md, p. 9, citing DIIG): "A set of related activities or tasks performed together to achieve the objectives of the health programme area, such as registration, counselling and referrals (3)." Both are recorded as candidates; neither is chosen.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Business Process ; views: Metamodel vs EIRA
- Business Services Layer candidate
-
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.
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review.
C
- Capability candidate
-
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.
The RA draft's own glossary wording, verbatim (folio/dpi-h-ra/glossary/t-glossary-lead-a31853.md). Wording alternative in RA Table 3.1 (library/who-dpi-h-reference-architecture-draft-v1/sections/sec-026-31-the-architecture-description-approach.md): "An ability that an organisation, person, or system possesses — expressed in terms of what can be done, not how or by whom." Both are recorded as candidates; neither is chosen (smart-ra#133 S1).
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Capability ; views: Metamodel, Metamodel vs EIRA, Testing
-
Care Services Directory
CSDcandidate -
No definition yet.
Expanded in Appendix C (Health Workforce Registry, HWRF-5) for the IHE Care Services Directory (CSD) standard alongside FHIR R4 Practitioner/PractitionerRole and mCSD. A candidate: no definition has been written.
-
Civil Registration and Vital Statistics
CRVScandidate -
No definition yet.
Used in Chapter 3 and Appendix C (Client Registry and Public Health Surveillance Platform) for foundational civil registration and vital statistics systems. Expansion supplied; check in context. A candidate: no definition has been written.
- Client candidate
-
Members of the public who are potential or current users of health services, including health prevention and wellness activities.
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review.
-
Client Registry
CRcandidate -
The Client Registry is the national authoritative source of health-specific person identity. It is the foundational health-sector component that maintains a unique, verifiable identity record for every person who accesses or is eligible to access health services within a jurisdiction.
Verbatim lead sentence from Appendix C (Client Registry, 1 What It Is). Also abbreviated CR in the OpenHIE requirement identifiers (CRF-*, CRWF-*) and downstream Digital Transformation Handbooks. A candidate until the RA editors adopt it through the public review.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Client Registry , Client Registry ; views: TPHR Sub-goal #1 Layered View (Fig. 3.3), TPHR High Level Layered View (Fig. 3.4), Q&CC Sub-goal #1 Layered View (Fig. 3.5)
-
Clinical Decision Support
CDScandidate -
No definition yet.
Used in Chapter 3 and Appendix C (Computable Decision Support Engine). A candidate: no standalone definition has been written.
-
Clinical Document Architecture
CDAcandidate -
No definition yet.
Used in Appendix C (Lifelong Health Record, SHRF-3) for HL7 Clinical Document Architecture alongside FHIR resources. Expansion supplied; check in context. A candidate: no definition has been written.
-
Clinical Quality Language
CQLcandidate -
No definition yet.
'HL7 Clinical Quality Language (CQL), a human-readable query language to encode calculations for computing indicators and clinical logic to drive decision support.' Defined by HL7, so link to the HL7 specification rather than defining it here.
-
Common Geo-Registry
CGRcandidate -
No definition yet.
Expanded in Appendix C (Health Facility Registry and Public Health Surveillance Platform) as a cross-sectoral foundational geospatial registry component holding administrative boundaries and geographic features. A candidate: no standalone glossary definition has been written.
-
Computable Decision Support Engine
CDSEcandidate -
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 and knowledge artefacts to person-specific health data.
Verbatim lead sentence from Appendix C (Computable Decision Support Engine, 1 What It Is). Abbreviated CDSE throughout the RA draft. A candidate until the RA editors adopt it through the public review.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Computable Decision Support Engine ; views: DPI-H Reference Architecture — Integrated View (Fig. 3.2), DPI-H Reference Architecture — DPI-H layers (Fig. 3.5), CDS
-
Continuing Professional Development
CPDcandidate -
No definition yet.
Used in Appendix C (Health Workforce Registry) and shared with dth-hrh. Expansion supplied; check in context. A candidate: no definition has been written.
-
Contract and Benefits Management System
CBMScandidate -
No definition yet.
Distinguished from the Benefits Package Registry (BPR) and Beneficiary Registry in the Appendix C comparison table as an operational financial-domain functional application managing payer-provider contracts, empanelment agreements, claims, and adjudication. A candidate: no standalone glossary definition has been written.
D
- Data Dictionary candidate
-
A singular storage location for information about the data elements, detailing their type and definition, relationships, origin and use.
PHC handbook glossary wording, verbatim (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 8). Wording alternative in SFP handbook §4.4 body (who-iris/library/9789240120747-eng/sections/sec-025-44-outline-data-requirements.md, page-042.md, p. 30): "A data dictionary is a repository of information about the data elements such as description, data type and other characteristics." Both are recorded as candidates; neither is chosen (smart-ra#133 S1, dth-sfp#1 P2).
- Data Element candidate
-
A unit of data that has a specific and precise meaning.
Identical wording in PHC handbook glossary (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 8), PC handbook glossary (who-iris/library/9789240116191-eng/sections/page-008.md, p. 8), and SFP handbook glossary (who-iris/library/9789240120747-eng/sections/page-009.md, p. 9, citing ref. 4). Recorded as a shared candidate concept (smart-ra#133 S1).
- Data Governance candidate
-
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
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Data Governance ; views: TPHR High Level Layered View (Fig. 3.4)
- Data Object candidate
-
A defined unit of structured data used or produced by an application component.
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Data Object ; views: Metamodel, Metamodel vs EIRA, Testing
- Deploy candidate
-
Make the software available for use beyond testing purposes.
PHC handbook glossary wording under 'Deploy' (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 8). Wording alternative in SC handbook glossary under 'deployment' (who-iris/library/9789240101197-eng/sections/page-008.md, p. 8): "Making a software system available for use beyond testing purposes." Both are recorded as candidates; neither is chosen (smart-ra#133 S1).
- DHIS2 candidate
-
No definition yet.
Described in Appendix D.1 (Health Management Information System) as a widely deployed open-source health management information application providing aggregate reporting, indicator calculation, dashboards, and tracker modules. Shared with dth-hrh, dth-phc, and dth-sc. A candidate: no standalone glossary definition has been adopted.
-
Digital Adaptation Kit
DAKcandidate -
No definition yet.
WHO SMART Guidelines L2 operational and functional package (health interventions, personas, user scenarios, business processes, core data elements, and decision-support logic). Shared across the reference architecture and Digital Transformation Handbooks. A candidate: no standalone definition has been adopted in the RA glossary.
- Digital Health candidate
-
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.
The RA draft's own glossary wording, verbatim (folio/dpi-h-ra/glossary/t-glossary-lead-a31853.md). Substantive and wording alternatives across the DTH corpus (smart-ra#133 S1, smart-ra#140): (1) PHC handbook glossary (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 8, citing WHO Global Strategy on Digital Health 2020–2025): "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)." (2) SC handbook glossary (who-iris/library/9789240101197-eng/sections/page-008.md, p. 8, citing DIIG and Global Strategy): "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)." (3) SC handbook Introduction (who-iris/library/9789240101197-eng/sections/page-012.md, p. 12, quoting the WHO Global Strategy on Digital Health 2020–2025, same source cited by dth-hrh): "the field of knowledge and practice associated with the development and use of digital technologies to improve health". All are recorded as candidates; none is chosen.
-
Digital Health and Interoperability
DISIcandidate -
No definition yet.
Used across the WHO Digital Transformation Handbooks (abbreviated DISI or DH&I) for the digital health and interoperability domain and working group. A candidate: no definition has been written.
- Digital Health Governance candidate
-
Digital health governance defines who, what and how to govern to achieve health service impact.
The paper cites Marcelo et al. 2018 (ADB) for this sentence, so the definition is that source's, as quoted here.
-
Digital Health Platform
DHPcandidate -
No definition yet.
Expanded in Section 1.1.3 in reference to the 2020 WHO-ITU Digital Health Platform (DHP) Handbook. A candidate: no standalone definition has been written.
-
Digital Health Supply Chain
DHSCcandidate -
No definition yet.
Used in Appendix C (Supplier Registry) in reference to the WHO Digital Transformation Handbook for Health Supply Chain Architecture (dth-sc). A candidate: no standalone definition has been written here.
-
Digital Imaging and Communications in Medicine
DICOMcandidate -
No definition yet.
Used in Section 3.6.2 as the medical imaging standard alongside HL7 FHIR. Expansion supplied; check in context. A candidate: no definition has been written.
-
Digital Implementation Investment Guide
DIIGcandidate -
No definition yet.
-
Digital Implementation Investment Guide
DIIGcandidate -
No definition yet.
Named in the RA draft's Acronyms table, which gives the expansion used as prefLabel, and across all five Digital Transformation Handbooks. A candidate: no definition has been written.
- Digital Infrastructure candidate
-
Infrastructures in the digital domain are digital resources, such as systems and specifications, built as shared means to achieve many ends
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review.
-
Digital Public Infrastructure
DPIcandidate -
No definition yet.
-
Digital Public Infrastructure
DPIcandidate -
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)
The RA draft's own glossary wording, verbatim (folio/dpi-h-ra/glossary/t-glossary-lead-a31853.md). Wording alternative in RA §1.1.2 body (library/who-dpi-h-reference-architecture-draft-v1/sections/sec-002-112-understanding-digital-public-infrastructure.md): "Digital Public Infrastructure (DPI) refers to shared digital systems that are secure and interoperable, 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 and respect human rights and fundamental freedoms." (Glossary reads "interoperable, and can be built"; body reads "interoperable, built".) Both are recorded as candidates; neither is chosen (smart-ra#133 S1).
- Digital Transformation candidate
-
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).
PHC handbook glossary wording, verbatim (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 8); identical wording (with minor punctuation/citation differences) in PC handbook glossary (who-iris/library/9789240116191-eng/sections/page-008.md, p. 8) and SFP handbook glossary (who-iris/library/9789240120747-eng/sections/page-009.md, p. 9). Wording alternative in SC handbook glossary (who-iris/library/9789240101197-eng/sections/page-008.md, p. 8), which inverts the two sentences: "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." All are recorded as candidates; none is chosen (smart-ra#133 S1).
- Digitalization candidate
-
The process of digitally automating and simplifying processes to streamline individual health programmes and reduce manual efforts for greater efficiency (12,13).
PHC handbook glossary wording, verbatim (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 8). Wording alternatives across the DTH corpus (smart-ra#133 S1): (1) SC handbook glossary (who-iris/library/9789240101197-eng/sections/page-008.md, p. 8): "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)." (2) PC handbook glossary (who-iris/library/9789240116191-eng/sections/page-008.md, p. 8) and SFP handbook glossary (who-iris/library/9789240120747-eng/sections/page-009.md, p. 9): "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." All are recorded as candidates; none is chosen.
- Digitization candidate
-
The process of converting and organizing data from paper records into a digital format for easier entry, storage and retrieval (12,16).
PHC handbook glossary wording, verbatim (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 8). Wording alternatives across the DTH corpus (smart-ra#133 S1): (1) SC handbook glossary (who-iris/library/9789240101197-eng/sections/page-008.md, p. 8): "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)." (2) PC handbook glossary (who-iris/library/9789240116191-eng/sections/page-008.md, p. 8) and SFP handbook glossary (who-iris/library/9789240120747-eng/sections/page-009.md, p. 9): "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." All are recorded as candidates; none is chosen.
E
-
Electronic Health Record
EHRcandidate -
No definition yet.
Expanded in Appendix C (Lifelong Health Record, Terminology and Scope), which contrasts Electronic Medical Record (EMR), Electronic Health Record (EHR), and Shared Health Record (SHR) with the Lifelong Health Record (LHR). Also used across the Digital Transformation Handbooks. A candidate: no standalone glossary definition has been adopted.
-
Electronic Integrated Disease Surveillance and Response
eIDSRcandidate -
No definition yet.
Expanded in Appendix C (Public Health Surveillance Platform, Terminology and Scope). A candidate: no definition has been written.
-
Electronic Medical Record
EMRcandidate -
An electronic record of health-related information that can be created, gathered, managed, and consulted by authorised clinicians and staff within one health care organisation.
Defined in Appendix C (Lifelong Health Record, Terminology and Scope) citing the ONC/NAHIT definition, and contrasted with EHR, SHR, and LHR. Also used across the Digital Transformation Handbooks. A candidate until the RA editors adopt it through the public review.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Electronic Medical Record ; views: Q&CC Sub-goal #1 Layered View (Fig. 3.5)
- Enabling Environment candidate
-
Attitudes, actions, policies and practices that stimulate and support effective and efficient functioning of organizations, individuals and programmes. The enabling environment includes legal, regulatory and policy frameworks and political, sociocultural, institutional and economic factors (3).
SFP handbook glossary wording, verbatim (who-iris/library/9789240120747-eng/sections/sec-002-glossary.md, page-009.md, p. 9, citing DIIG), matching DIIG Annex 1.1 Glossary (who-iris/library/9789240010567-eng/sections/page-139.md, p. 127). Shared DIIG Phase 1 concept across DTHs (smart-ra#133 S1, dth-sfp#1 §2.1 Cluster B1); recorded as a candidate.
- End-User candidate
-
People who will be using the digital system(s).
Identical wording in PHC handbook glossary ('End-user', who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 8), PC handbook glossary ('End user', who-iris/library/9789240116191-eng/sections/page-008.md, p. 8), and SFP handbook glossary ('End user', who-iris/library/9789240120747-eng/sections/page-009.md, p. 9). Wording alternative in SC handbook glossary ('end users', who-iris/library/9789240101197-eng/sections/page-008.md, p. 8): "People who will be using the digital systems." All are recorded as candidates; none is chosen (smart-ra#133 S1).
-
Enterprise Architecture
EAcandidate -
The organising logic for business processes and IT infrastructure reflecting the integration and standardisation requirements of the organisation's operating model.
The RA draft's own glossary wording, verbatim (folio/dpi-h-ra/glossary/t-glossary-lead-a31853.md); the draft marks this entry [Under review]. Substantive alternatives across the DTH corpus (smart-ra#133 S1, smart-ra#139, smart-ra#140): (1) PHC handbook glossary (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 9, citing DIIG): "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)." (2) SC handbook glossary (who-iris/library/9789240101197-eng/sections/page-008.md, p. 8, citing DIIG): "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)." (3) SFP handbook glossary (who-iris/library/9789240120747-eng/sections/page-009.md, p. 9, citing DIIG): "A blueprint of business processes, data, systems and technologies used to help implementers design increasingly complex systems to support the workflow and roles of people in a large enterprise, such as a health system (3)." All four are recorded as candidates; none is chosen.
-
Enterprise Master Patient Index
EMPIcandidate -
No definition yet.
Expanded in Appendix C (Client Registry). A candidate: no definition has been written.
- Evaluation candidate
-
The systematic and objective assessment of an ongoing or completed intervention with the aim of determining the fulfilment of objectives, efficiency, effectiveness, impact and sustainability (8).
SFP handbook glossary wording, verbatim (who-iris/library/9789240120747-eng/sections/sec-002-glossary.md, page-009.md, p. 9, citing Monitoring and evaluating digital health interventions, WHO 2016). Wording alternative in DIIG Annex 1.1 Glossary (who-iris/library/9789240010567-eng/sections/page-140.md, p. 128, citing WHO evaluation practice handbook, 2013): "The systematic assessment of an ongoing or completed intervention to determine whether the intervention is fulfilling its objectives and to demonstrate an effect on health outcomes." Also contrasted with monitoring in SFP §6.1 (who-iris/library/9789240120747-eng/sections/sec-029-61-develop-a-monitoring-and-evaluation-plan.md, page-051.md, p. 39, quoting Pritchett et al. 2013): "Evaluation asks whether the project is doing the right things, while monitoring asks whether the project is doing things right." Both definitions are recorded as candidates; neither is chosen (smart-ra#133 S1, dth-sfp#1 §2.1 Cluster B1).
-
Event Information System
EIScandidate -
No definition yet.
Expanded in Appendix C (Public Health Surveillance Platform) for the WHO Event Information System (EIS) operational standards. A candidate: no definition has been written.
F
-
Fast Healthcare Interoperability Resources
FHIRcandidate -
FHIR is a standard for healthcare data exchange, published by HL7®
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review.
- Features candidate
-
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).
PHC handbook glossary wording, verbatim (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 9). Wording alternatives across the DTH corpus, differing only in domain example and 'a system' vs 'your system' (smart-ra#133 S1): (1) SC handbook glossary (who-iris/library/9789240101197-eng/sections/page-008.md, p. 8): "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)." (2) PC handbook glossary (who-iris/library/9789240116191-eng/sections/page-008.md, p. 8) and SFP handbook glossary (who-iris/library/9789240120747-eng/sections/page-009.md, p. 9): "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)." All are recorded as candidates; none is chosen.
-
Finance and Insurance Service
FIScandidate -
No definition yet.
Expanded in Appendix C (Benefits Package Registry) for the OpenHIE Finance and Insurance Service (FIS) specification (FISF-*). A candidate: no definition has been written.
-
Foundational Digital Public Infrastructure
DPI-Fcandidate -
No definition yet.
-
Foundational Digital Public Infrastructure
DPI-Fcandidate -
Foundational Digital Public Infrastructure (DPI-F) is the digital public infrastructure, such as identity, payments and data exchange, upon which the health sector can build. DPI-H is distinct from DPI-F and builds on it.
Added to the RA glossary table in CS-001 (smart-ra#185, public comments No. 136 and No. 327), per committee feedback (CL). A candidate until the RA editors adopt it through the public review. Named in the RA draft's Acronyms table, which gives the expansion used as prefLabel, and in Section 1.2.3 on cross-sectoral foundational DPI (digital identity, payments, data exchange).
- Full-STAC candidate
-
An ecosystem specifying open standards, open technologies, open architectures, and open content (full-STAC).
Cites Mehl et al. 2023 (library/mehl-2023-full-stac-oqad018/, glossary/full-stac.glossary.json) in RA §2.2.2 (library/who-dpi-h-reference-architecture-draft-v1/sections/sec-022-222-the-enabling-conditions-for-reddhi.md). Linked via exactMatch to the full-STAC scheme (smart-ra#143).
- Full-STAC candidate
-
Together, open Standards, open Technologies, open Architectures and open Content represent a next-generation ‘full-STAC’ remedy for digital health transformation.
Quoted from the abstract. The paper calls it both an approach and a remedy, and names the four as 'four factors'. The DPI-H RA draft (sec-022, footnote 14) cites this paper and presents the four as 'the enabling conditions for REDDHI'.
Uses: Open Standards, Open Technologies, Open Architectures, Open Content
-
Full-Time Equivalent
FTEcandidate -
No definition yet.
Expanded in Appendix C (Health Workforce Registry) and shared with dth-hrh and dth-sc. A candidate: no definition has been written.
- Functional Application candidate
-
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.
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review.
- Functional Requirements candidate
-
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).
PHC handbook glossary wording, verbatim (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 9). Wording and substantive alternatives across the DTH corpus (smart-ra#133 S1): (1) SC handbook glossary (who-iris/library/9789240101197-eng/sections/page-008.md, p. 8): "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." (2) PC handbook glossary (who-iris/library/9789240116191-eng/sections/page-008.md, p. 8): "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)." (3) SFP handbook glossary (who-iris/library/9789240120747-eng/sections/page-009.md, p. 9): "Capabilities the system must have to meet the end users’ needs and achieve tasks within the business process." All four are recorded as candidates; none is chosen.
- Functions candidate
-
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).
PHC handbook glossary wording, verbatim (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 9). Substantive alternative in SC handbook glossary (who-iris/library/9789240101197-eng/sections/page-008.md, p. 8): "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)." (PHC defines functions as "how features are implemented"; SC defines them as "Business processes within a system that help the system perform".) Both are recorded as candidates; neither is chosen (smart-ra#133 S1).
G
- Generic Product candidate
-
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.
PC handbook glossary wording, verbatim (who-iris/library/9789240116191-eng/sections/page-008.md, p. 8), identical in SFP handbook glossary (who-iris/library/9789240120747-eng/sections/sec-002-glossary.md, page-010.md, p. 10). Internal wording alternative in PC handbook Ch. 2 body (who-iris/library/9789240116191-eng/sections/page-028.md, p. 28): "Generic products can be described as generic items that conceal the brand or manufacturer information." Distinct from the RA's architectural `product` concept; both wordings are recorded as candidates and neither is chosen (smart-ra#133 S1, smart-ra#139, smart-ra#142).
-
Geographic Information System
GIScandidate -
No definition yet.
Used in Appendix C (Health Facility Registry and Public Health Surveillance Platform) and shared with dth-sc. Expansion supplied; check in context. A candidate: no definition has been written.
-
Global Data Synchronisation Network
GDSNcandidate -
No definition yet.
Expanded in Appendix C (Product Registry) as the GS1 network for synchronising product master data. Shared with dth-pc and dth-sfp. A candidate: no definition has been written.
-
Global Digital Health Certification Network
GDHCNcandidate -
No definition yet.
Expanded in Section 3.6.4 (The WHO Global Digital Health Certification Network (GDHCN)) as the WHO-operated global trust network through which member states verify the authenticity of digitally signed health documents and credentials across borders. A candidate: no standalone glossary definition has been written.
-
Global Health Facilities Database
GHFDcandidate -
No definition yet.
Used in Appendix C (Health Facility Registry) for the WHO Global Health Facilities Database initiative. Expansion supplied; check in context. A candidate: no definition has been written.
-
Global Location Number
GLNcandidate -
No definition yet.
Expanded in Appendix C (Supplier Registry) as the GS1 standard identifier for parties and physical/functional locations. Shared with dth-sc, dth-pc, and dth-sfp. A candidate: no definition has been written.
-
Global Product Classification
GPCcandidate -
No definition yet.
Used in Appendix C (Product Registry) as the GS1 classification standard alongside ATC and UNSPSC. Shared with dth-pc. Expansion supplied; check in context. A candidate: no definition has been written.
-
Global Trade Item Number
GTINcandidate -
No definition yet.
Expanded in Appendix C (Product Registry) and shared across the supply chain, product catalogue, and substandard/falsified medical products handbooks. A candidate: no standalone definition has been written here.
- Goal candidate
-
A high-level statement of intent, direction, or desired state for an organisation and its stakeholders.
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Goal ; views: Metamodel, Metamodel vs EIRA, Testing
- Governance candidate
-
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.
RA §3.4.1 body wording, verbatim (library/who-dpi-h-reference-architecture-draft-v1/sections/sec-029-341-purpose-and-framing.md, p. 64–65). Substantive alternative in SC handbook Ch. 3 boxed definition (who-iris/library/9789240101197-eng/sections/page-045.md, p. 45): "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." (RA defines governance as the distribution, exercise, and accountability of decision authority across shared infrastructure; SC defines it as the process of establishing and implementing policies, procedures, and mechanisms for supply chain processes and systems.) Also related to `digital-health-governance` in Mehl et al. 2023 (glossary/full-stac.glossary.json, smart-ra#143 P8). Also framed in SFP handbook §2.3 (who-iris/library/9789240120747-eng/sections/sec-015-23-establish-governance-and-leadership.md, page-028.md, p. 16) as a structure for coordinating multiple stakeholders, defining clear roles and responsibilities, enhancing transparency, and creating a stable platform for decision-making. Both definitions are recorded as candidates; neither is chosen (smart-ra#133 S1, smart-ra#140, dth-sfp#1 P2).
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Governance ; views: DPI-H architecture design principles (Fig. 2.3)
-
Government-to-Person
G2Pcandidate -
No definition yet.
Expanded in Section 1.2.3 for foundational payment transfer mechanisms. A candidate: no definition has been written.
H
-
Health Digital Public Infrastructure
DPI-Hcandidate -
No definition yet.
-
Health Digital Public Infrastructure
DPI-Hcandidate -
Health Digital Public Infrastructure (DPI-H) refers to digital resources that are built as a shared means for fulfilling multiple health agency functions.
The RA draft's own glossary wording, verbatim (folio/dpi-h-ra/glossary/t-glossary-lead-a31853.md). Wording alternative in RA §1.1.2 body (library/who-dpi-h-reference-architecture-draft-v1/sections/sec-002-112-understanding-digital-public-infrastructure.md), which adds a second defining sentence: "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." Both are recorded as candidates; neither is chosen (smart-ra#133 S1).
-
Health Facility Registry
FRcandidate -
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 otherwise relevant to health system operations.
Verbatim lead sentence from Appendix C (Health Facility Registry, 1 What It Is). Abbreviated FR in the OpenHIE Facility Registry specification references (FRF-*, FRWF-*) and FR / HFR across the Digital Transformation Handbooks. A candidate until the RA editors adopt it through the public review.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Health Facility Registry ; views: DPI-H Reference Architecture — Integrated View (Fig. 3.2), DPI-H Reference Architecture — DPI-H layers (Fig. 3.5), REDDHI and its full-STAC foundations (Fig. 2.2), ALL High Level - Health Workforce, 1. Central Health Workforce Registry, SUB-GOAL 1. Central Health Workforce Registry
-
Health Information Exchange
HIEcould-not-extract -
The draft lists the term with no definition.
The draft marks this entry [To be included before publication].
Depicted in ArchiMate dpi-h-ra 0.2.0-draft.3: Health Information Exchange
-
Health Information System
HIScandidate -
A system that integrates data collection, processing, reporting, and use of the information necessary for improving health service effectiveness and efficiency through better management at all levels of health services.
DIIG Annex 1.1 Glossary wording, verbatim (who-iris/library/9789240010567-eng/sections/page-140.md, p. 128, citing WHO 2004 Developing health management information systems; also abbreviated in DIIG page-011.md and HRH handbook who-iris/library/9789240062627-eng/sections/page-006.md). The PHC handbook (who-iris/library/9789240093362-eng) has no HIS abbreviation or definition; a wording earlier attributed to it here is not in its text and was removed (smart-ra#200). Referenced in SFP handbook glossary under SMART Guidelines (who-iris/library/9789240120747-eng/sections/sec-002-glossary.md, page-011.md, p. 11) and Ch. 4 (who-iris/library/9789240120747-eng/sections/sec-021-4-determine-the-requirements.md, page-035.md, p. 23). The definition is recorded as a candidate (smart-ra#133 S1, dth-sfp#1 P2).
-
Health Level Seven Fast Healthcare Interoperability Resources
HL7 FHIR®candidate -
No definition yet.
-
Health Management Information System
HMIScandidate -
The Health Management Information System is a governed, shared application component responsible for the systematic collection, aggregation, analysis, and dissemination of population-level and facility-level health data to support health system planning, performance monitoring, resource allocation, and policy decision-making.
Lead sentence from Appendix C (Health Management Information System, 1 What It Is). Abbreviated HMIS throughout the RA draft and downstream Digital Transformation Handbooks. A candidate until the RA editors adopt it through the public review.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Health Management Information System ; views: DPI-H Reference Architecture — Integrated View (Fig. 3.2), DPI-H Reference Architecture — DPI-H layers (Fig. 3.5), DHSC Architecture Framework (DTH SC Fig. 14)
- Health Programme candidate
-
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.
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review.
-
Health Unique Identifier
HUIDcandidate -
No definition yet.
Expanded in Appendix C (Client Registry) as a nationally unique, non-intelligent health identifier assigned and managed by the Client Registry for each registered person. A candidate: no standalone glossary definition has been written.
-
Health Workforce Registry
HWRcandidate -
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 — including licensed or certified clinical professionals, community health workers, allied health personnel, and administrative and management staff in health-related roles.
Verbatim lead sentence from Appendix C (Health Workforce Registry, 1 What It Is). Also called Health Worker Registry (HWR) in OpenHIE alignment notes and downstream Digital Transformation Handbooks. A candidate until the RA editors adopt it through the public review.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Health Workforce Registry ; views: DPI-H Reference Architecture — Integrated View (Fig. 3.2), DPI-H Reference Architecture — DPI-H layers (Fig. 3.5), REDDHI and its full-STAC foundations (Fig. 2.2), ALL High Level - Health Workforce, 1. Central Health Workforce Registry, SUB-GOAL 1. Central Health Workforce Registry
-
Human Resources
HRcandidate -
No definition yet.
Used in Appendix C (Health Workforce Registry) and shared across the Digital Transformation Handbooks. Expansion supplied; check in context. A candidate: no definition has been written.
-
Human Resources for Health
HRHcandidate -
No definition yet.
Used in Appendix C (Health Facility Registry) and as the subject of the WHO Digital Transformation Handbook for Human Resources for Health (dth-hrh). Expansion supplied; check in context. A candidate: no standalone definition has been written here.
-
Human Resources Information System
HRIScandidate -
No definition yet.
Expanded in Appendix C (Health Workforce Registry) and shared with dth-hrh. A candidate: no standalone definition has been written here.
I
-
Identification of Medicinal Products
IDMPcandidate -
No definition yet.
Used in Appendix C (Product Registry) and shared with dth-pc and dth-sfp for the ISO IDMP suite of standards. Expansion supplied; check in context. A candidate: no definition has been written.
-
Implementation Guide
IGcandidate -
No definition yet.
Used in Chapter 3 and Appendix F (Table F: SGI Capability Details) for FHIR Implementation Guides (IGs). Expansion supplied; check in context. A candidate: no definition has been written.
-
Information and Communications Technology
ICTcandidate -
No definition yet.
Used in Chapter 4 (Section 4.2.2) and shared across all five Digital Transformation Handbooks. Expansion supplied; check in context. A candidate: no definition has been written.
-
Information Technology
ITcandidate -
No definition yet.
Used across the RA draft and listed in the abbreviations tables of all five Digital Transformation Handbooks. A candidate: no definition has been written.
-
Integrated Disease Surveillance and Response
IDSRcandidate -
No definition yet.
Expanded in Appendix C (Public Health Surveillance Platform) for the WHO Integrated Disease Surveillance and Response technical guidelines. A candidate: no definition has been written.
-
Integrating the Healthcare Enterprise
IHEcandidate -
No definition yet.
Used throughout Chapter 3 (Section 3.7) and Appendix C for IHE integration profiles (PMIR, PIX, mCSD, CSD, SVCM, ADX). Expansion supplied; check in context. A candidate: no definition has been written.
- Integration candidate
-
Bespoke capability of connecting one application component to another
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review. The draft marks this entry [Under review].
-
International Certificate of Vaccination or Prophylaxis
ICVPcandidate -
No definition yet.
-
International Certificate of Vaccination or Prophylaxis
ICVPcandidate -
No definition yet.
Named in the RA draft's Acronyms table, which gives the expansion used as prefLabel. A candidate: no definition has been written.
-
International Classification of Diseases 11th Revision
ICD-11candidate -
No definition yet.
-
International Classification of Diseases 11th Revision
ICD-11candidate -
No definition yet.
Named in the RA draft's Acronyms table, which gives the expansion used as prefLabel, and throughout the terminology sections. A candidate: no definition has been written.
-
International Classification of Functioning, Disability and Health
ICFcandidate -
No definition yet.
Expanded in Appendix C (Terminology Service, 1 What It Is) as one of the international clinical terminologies and classifications managed and published by the Terminology Service. A candidate: no definition has been written.
-
International Classification of Health Interventions
ICHIcandidate -
No definition yet.
One of the three reference classifications of the WHO Family of International Classifications (WHO-FIC) alongside ICD-11 and ICF, used across the terminology service and Digital Transformation Handbooks. A candidate: no definition has been written.
-
International Classification of Primary Care
ICPCcandidate -
No definition yet.
Expanded in Appendix C (Terminology Service, 1 What It Is) among the international clinical terminologies and classifications managed by a Terminology Service. A candidate: no definition has been written.
-
International Health Regulations
IHRcandidate -
No definition yet.
Used in Appendix C (Public Health Surveillance Platform) for WHO's International Health Regulations (2005) reporting obligations. Expansion supplied; check in context. A candidate: no definition has been written.
-
International Patient Summary
IPScandidate -
No definition yet.
-
International Patient Summary
IPScandidate -
No definition yet.
Named in the RA draft's Acronyms table, which gives the expansion used as prefLabel, and in Section 3.6 and Appendix C (Lifelong Health Record). A candidate: no definition has been written.
-
International Standard Classification of Occupations (ISCO-08)
ISCO-08candidate -
No definition yet.
Referenced in Appendix C (Health Workforce Registry) as the ILO occupational classification framework on which the WHO health worker classification is based. Shared with dth-hrh. A candidate: no definition has been written.
-
International Telecommunication Union
ITUcandidate -
International Telecommunication Union
Singular 'Telecommunication' (the official UN agency name) in SC abbreviations (who-iris/library/9789240101197-eng/sections/page-007.md, p. 7), PC (who-iris/library/9789240116191-eng/sections/page-013.md, "ITU = International Telecommunication Union"), and RA front matter (library/who-dpi-h-reference-architecture-draft-v1/sections/sec-front-matter.md). Wording variant in PHC abbreviations (who-iris/library/9789240093362-eng/sections/sec-001-abbreviations.md, pp. 7-8): "International Telecommunications Union" (plural). Recorded per smart-ra#133 S1 and smart-ra#200.
- Interoperability candidate
-
Interoperability is the standards-based capability of heterogeneous information systems to communicate, exchange data, and use the exchanged information to execute functions effectively.
The RA draft's own glossary wording, verbatim (folio/dpi-h-ra/glossary/t-glossary-lead-a31853.md). Substantive and internal alternatives across the DTH corpus (smart-ra#133 S1, smart-ra#139, smart-ra#140, smart-ra#142): (1) PHC handbook glossary (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 9), PC handbook glossary (who-iris/library/9789240116191-eng/sections/page-008.md, p. 8), and SFP handbook glossary (who-iris/library/9789240120747-eng/sections/page-010.md, p. 10): "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." (2) SC handbook glossary (who-iris/library/9789240101197-eng/sections/page-008.md, p. 8, citing DIIG): "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)." (3) PHC handbook §4.4 body (who-iris/library/9789240093362-eng/sections/sec-023-44-design-system-architecture.md, §4.4, pp. 56-60): "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)." (4) PHC handbook §4.4.2 body (who-iris/library/9789240093362-eng/sections/sec-023-44-design-system-architecture.md, pp. 56-60): "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 data representation standards, within and across organizational, regional and national boundaries, to provide timely and seamless portability of information and optimize health outcomes." All are recorded as candidates; none is chosen.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Interoperability , Interoperability ; views: Components draft, Components, Interoperability Layer, DPI-H architecture design principles (Fig. 2.3)
L
-
Learning Management System
LMScandidate -
No definition yet.
Expanded in Appendix C (Health Workforce Registry). A candidate: no definition has been written.
-
Lifelong Health Record
LHRcandidate -
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 key health information across care settings and over their lifetime.
Verbatim lead sentence from Appendix C (Lifelong Health Record, 1 What It Is). Abbreviated LHR throughout the RA draft. A candidate until the RA editors adopt it through the public review.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Lifelong Health Record ; views: DPI-H Reference Architecture — Integrated View (Fig. 3.2), DPI-H Reference Architecture — DPI-H layers (Fig. 3.5), REDDHI and its full-STAC foundations (Fig. 2.2), TPHR Sub-goal #1 Layered View (Fig. 3.3), TPHR High Level Layered View (Fig. 3.4), Q&CC Sub-goal #1 Layered View (Fig. 3.5), SHR
-
Logical Information Model Repository
LIMRcandidate -
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 terminology bindings of health data objects across a national digital health ecosystem.
Verbatim lead sentence from Appendix C (Logical Information Model Repository, 1 What It Is). Abbreviated LIMR throughout the RA draft. A candidate until the RA editors adopt it through the public review.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Logical Information Model Repository ; views: DPI-H Reference Architecture — Integrated View (Fig. 3.2), DPI-H Reference Architecture — DPI-H layers (Fig. 3.5), Semantic Governance Infrastructure (Fig. 3.4.1), LMIR Overview, Interoperability Layer
-
Logical Observation Identifiers Names and Codes
LOINCcandidate -
No definition yet.
-
Logical Observation Identifiers Names and Codes
LOINCcandidate -
LOINC is a common language (a set of identifiers, names, and codes) for identifying health measurements, observations, and documents.
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review.
- Longitudinal Health Record could-not-extract
-
Described by what it supports, not defined.
'a standards-based longitudinal health record that supports the patient over time and across places where interactions with the health system occurs' (cites Kay 2021 on the International Patient Summary). A use, not a definition.
-
Low-and-Middle-Income Country
LMICcandidate -
No definition yet.
-
Low-and-Middle-Income Country
LMICcandidate -
No definition yet.
Named in the RA draft's Acronyms table, which gives the expansion used as prefLabel. A candidate: no definition has been written.
M
-
Master Facility List
MFLcandidate -
No definition yet.
Expanded in Appendix C (Health Facility Registry) in connection with the WHO/USAID Master Facility List (MFL) Resource Package. A candidate: no standalone glossary definition has been written.
-
Master Patient Index
MPIcandidate -
No definition yet.
Expanded in Appendix C (Client Registry, Terminology and Scope). A candidate: no definition has been written.
-
Ministry of Health
MoHcandidate -
No definition yet.
Expanded in Appendix C (Benefits Package Registry, Governance) and shared across all five Digital Transformation Handbooks. A candidate: no definition has been written.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Ministry of Health ; views: DPI-H Reference Architecture — Integrated View (Fig. 3.2), 1. Central Health Workforce Registry, ALL HRH Conceptual View - Stakeholder, SUB-GOAL 1. Central Health Workforce Registry , Health Supply Chain Partners and Processes (DTH SC Figs. 1-3), National Product Catalogue (DTH PC Fig. 2, Ch. 2-3)
-
Mobile Care Services Discovery
mCSDcandidate -
No definition yet.
Expanded in Appendix C (Health Facility Registry and Health Workforce Registry) as the IHE ITI profile for querying organisations, facilities, jurisdictions, and health workers across registries. A candidate: no definition has been written.
-
Model Context Protocol
MCPcandidate -
No definition yet.
Expanded in Section 5.2 (AI and DPI-H). A candidate: no definition has been written.
- Monitoring candidate
-
The continuous process of collecting and analysing data to compare how well an intervention is being implemented against expected results (8).
SFP handbook glossary wording, verbatim (who-iris/library/9789240120747-eng/sections/sec-002-glossary.md, page-010.md, p. 10, citing Monitoring and evaluating digital health interventions, WHO 2016). Wording alternative in DIIG Annex 1.1 Glossary (who-iris/library/9789240010567-eng/sections/page-141.md, p. 129, citing WHO evaluation practice handbook, 2013): "The process of collecting and analysing routinely collected data to compare how well an intervention is being implemented against expected results and measure changes in performance over time." Both definitions are recorded as candidates; neither is chosen (smart-ra#133 S1, dth-sfp#1 §2.1 Cluster B1).
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Monitoring ; views: Semantic governance capabilities, roles and tools (Fig. A.1), Metadata Registry Governance
N
-
National Health Data Dictionary
NHDDcandidate -
No definition yet.
Expanded in Figure 3.4.3 caption (OpenHIE National Health Data Dictionary (NHDD) framework). A candidate: no definition has been written.
-
National Health Workforce Accounts
NHWAcandidate -
No definition yet.
Expanded in Appendix C (Health Workforce Registry) as the WHO framework and indicator system through which countries progressively improve the availability, quality, and use of data on human resources for health. Shared with dth-hrh. A candidate: no standalone glossary definition has been written.
-
Non-Functional Requirements
NFRcandidate -
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).
PHC handbook glossary wording, verbatim (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 10), identical (without section cross-reference) in SFP handbook glossary (who-iris/library/9789240120747-eng/sections/page-010.md, p. 10). Substantive alternatives across the DTH corpus (smart-ra#133 S1): (1) SC handbook glossary ('nonfunctional requirements', who-iris/library/9789240101197-eng/sections/page-008.md, p. 8): "A description of how the digital system needs to operate and perform in order to support the tasks that make up the business process." (2) PC handbook glossary ('Non-functional requirements', who-iris/library/9789240116191-eng/sections/page-008.md, p. 8): "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. (e.g., a product master data management solution must be able to support offline mode when network connectivity is not available)" All are recorded as candidates; none is chosen.
-
Non-Governmental Organization
NGOcandidate -
No definition yet.
Used in Appendix C (Supplier Registry and Health Facility Registry) and listed in the abbreviations tables of the Digital Transformation Handbooks. A candidate: no definition has been written.
O
- Open Architectures candidate
-
Open architectures refer to high-level specifications of technical designs that provide blueprints for creating open ecosystems structured into reusable and shareable components.
RA §2.2.2 body wording, verbatim (library/who-dpi-h-reference-architecture-draft-v1/sections/sec-022-222-the-enabling-conditions-for-reddhi.md, p. 35–39), citing Mehl et al. 2023 (library/mehl-2023-full-stac-oqad018/, glossary/full-stac.glossary.json: "High-level specifications of technical designs that provide blueprints for creating open ecosystems structured into reusable and shareable components, such as within a health information exchange."). Linked via exactMatch to the full-STAC scheme (smart-ra#133 S1, smart-ra#143).
- Open Architectures candidate
-
Documentation, using open standards, of reusable enterprise architecture patterns for health systems, describing the diverse digital interconnections of systems and capabilities (including trust networks, services, registries, access controls). Open architectures are designed to be instantiable via open technologies; provide a core infrastructure that fosters an ecosystem of digital health tools; are developed and maintained through collaborative, consensus-driven processes; and are freely available for use and adaptation without license restrictions.
Transcribed from Figure 1 (p. 2). The figure's text is drawn as outlines, so the ingest could not extract it (vector-figures.json: vfig-p002 unrendered); the transcription was read off a 220 dpi render of the page on 2026-10-31 and needs a person to confirm it. Example given in the figure: the OpenHIE Architecture.
Uses: Open Standards, Open Technologies
-
Open Client Registry
OpenCRcandidate -
No definition yet.
Expanded in Appendix D.1 (Client Registry) as an open-source Client Registry from the OpenHIE community providing configurable deterministic and probabilistic record linkage. A candidate: no standalone glossary definition has been written.
- Open Content candidate
-
Open content refers to domain ideas and synthesized knowledge clearly documented without restrictions inhibiting readability or usage.
RA §2.2.2 body wording, verbatim (library/who-dpi-h-reference-architecture-draft-v1/sections/sec-022-222-the-enabling-conditions-for-reddhi.md, p. 35–39), citing Mehl et al. 2023 (library/mehl-2023-full-stac-oqad018/, glossary/full-stac.glossary.json: "Domain ideas and synthesized knowledge clearly documented without restrictions inhibiting readability or usage, such as health guidelines, workflows, core data elements, terminology mappings, and test cases aligned to standards."). Linked via exactMatch to the full-STAC scheme (smart-ra#133 S1, smart-ra#143).
- Open Content candidate
-
Representations of public health, health system, or clinical knowledge, which are developed to meet the business needs described by an open architecture, and which describe, using open standards, assets such as minimum datasets, decision-support logic, care protocols, performance metrics, workflows, and reporting templates. Open content is developed, validated, and maintained through expert communities, and is freely available for use and adaptation without license restrictions.
Transcribed from Figure 1 (p. 2). The figure's text is drawn as outlines, so the ingest could not extract it (vector-figures.json: vfig-p002 unrendered); the transcription was read off a 220 dpi render of the page on 2026-10-31 and needs a person to confirm it. Example given in the figure: a WHO SMART Guidelines FHIR Implementation Guide.
Uses: Open Standards, Open Architectures
-
Open Health Information Exchange
OpenHIEcandidate -
No definition yet.
- Open Source candidate
-
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). While the source code is open to everyone, this does not mean that implementation of software is necessarily without costs. An open-source software must have a license approved by the Open Source Initiative (19).
PHC handbook glossary wording, verbatim (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 10), identical (with minor punctuation/citation differences) in PC handbook glossary (who-iris/library/9789240116191-eng/sections/page-008.md, p. 8) and SFP handbook glossary (who-iris/library/9789240120747-eng/sections/page-010.md, p. 10). Wording alternative in SC handbook glossary under 'open-source software' (who-iris/library/9789240101197-eng/sections/page-008.md, p. 8), which adds "within set guidelines": "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). While the source code is open to everyone, the implementation of the software is not necessarily without costs. Open-source software must have a license approved by the Open Source Initiative (9)." All are recorded as candidates; none is chosen (smart-ra#133 S1).
- Open Standards candidate
-
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).
PHC handbook glossary wording, verbatim (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 10), identical (with minor punctuation/citation differences) in PC handbook glossary (who-iris/library/9789240116191-eng/sections/page-008.md, p. 8) and SFP handbook glossary (who-iris/library/9789240120747-eng/sections/page-010.md, p. 10), and near-identical (two sentences) in SC handbook glossary (who-iris/library/9789240101197-eng/sections/page-009.md, p. 9): "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)." Substantive/complementary alternative in RA §2.2.2 (library/who-dpi-h-reference-architecture-draft-v1/sections/sec-022-222-the-enabling-conditions-for-reddhi.md, p. 35–39), citing Mehl et al. 2023 (library/mehl-2023-full-stac-oqad018/, linked via exactMatch to glossary/full-stac.glossary.json): "Open standards are validated and vetted specifications, repeatedly reusableacross contexts, that address common requirements, processes, and interactions and enable fidelity metrics." All are recorded as candidates; none is chosen (smart-ra#133 S1, smart-ra#139, smart-ra#142 item 3, smart-ra#143).
- Open Standards candidate
-
Semantic and syntactic models for data representation, exchange, and processing that ensure the precise meaning of exchanged information is unambiguously interpretable by any other system, service, or user. Open standards are developed and maintained through collaborative, consensus-driven processes, and are freely available for use and adaptation without license restrictions.
Transcribed from Figure 1 (p. 2). The figure's text is drawn as outlines, so the ingest could not extract it (vector-figures.json: vfig-p002 unrendered); the transcription was read off a 220 dpi render of the page on 2026-10-31 and needs a person to confirm it. Example given in the figure: shared FHIR profiles with standard ontologies. The body text also says: 'OPEN STANDARDS refers to a common schema for health data, calculations and information exchange.'
- Open Technologies candidate
-
Open technologies denote components of configurable and extensible source code — often curated as digital public goods — that perform distinct functions while adhering to open standards.
RA §2.2.2 body wording, verbatim (library/who-dpi-h-reference-architecture-draft-v1/sections/sec-022-222-the-enabling-conditions-for-reddhi.md, p. 35–39), citing Mehl et al. 2023 (library/mehl-2023-full-stac-oqad018/, glossary/full-stac.glossary.json: "Components of configurable and extensible source code, often curated as 'global goods' or 'digital public goods', that perform a distinct function while adhering to open standards."). Linked via exactMatch to the full-STAC scheme (smart-ra#133 S1, smart-ra#143).
- Open Technologies candidate
-
Modular, standards-based, and accessible software tools that help developers and users to collect, store, transmit, or analyze data represented in open standards. Open technologies are developed and maintained through transparent, community-based processes, and are licensed under an open-source software license.
Transcribed from Figure 1 (p. 2). The figure's text is drawn as outlines, so the ingest could not extract it (vector-figures.json: vfig-p002 unrendered); the transcription was read off a 220 dpi render of the page on 2026-10-31 and needs a person to confirm it. Example given in the figure: the Open Health Stack Android FHIR SDK. The body adds: 'Open technologies are open-source and use open standards.'
Uses: Open Standards
- OpenCDS candidate
-
No definition yet.
Named in Appendix D.1 (Computable Decision Support Engine) as an open-source inference engine that executes clinical rules independently of the calling EHR. A candidate: no definition has been written.
- OpenELIS candidate
-
No definition yet.
Named in Appendix D.1 (Public Health Surveillance Platform) as an open-source public-health laboratory information system feeding confirmed diagnostic results to surveillance platforms through FHIR. A candidate: no definition has been written.
- OpenMRS candidate
-
No definition yet.
Named in Appendix D.1 (Computable Decision Support Engine) as an open-source point-of-care electronic medical record platform. Shared with dth-phc. A candidate: no definition has been written.
- Organogram candidate
-
A visual representation of an organization’s structure that shows the hierarchy of various roles and reporting relationships.
SC handbook glossary wording, verbatim (who-iris/library/9789240101197-eng/sections/page-009.md, p. 9). Wording alternative in PC handbook glossary (who-iris/library/9789240116191-eng/sections/page-008.md, p. 8) and SFP handbook glossary (who-iris/library/9789240120747-eng/sections/sec-002-glossary.md, page-010.md, p. 10): "A visual representation of the organization structure showing the hierarchy of various roles and their reporting relationships." Both are recorded as candidates; neither is chosen (smart-ra#133 S1).
- Outcome candidate
-
An end result or consequence of a set of activities; an outcome is often measurable and signals progress towards a goal.
The RA draft's own glossary wording, verbatim (folio/dpi-h-ra/glossary/t-glossary-lead-a31853.md). Wording alternative in RA Table 3.1 (library/who-dpi-h-reference-architecture-draft-v1/sections/sec-026-31-the-architecture-description-approach.md): "An achieved, and often measurable, result that signals progress towards a goal." Both are recorded as candidates; neither is chosen (smart-ra#133 S1).
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Outcome ; views: Metamodel, Metamodel vs EIRA
P
-
Patient Identifier Cross-Referencing
PIXcandidate -
No definition yet.
Used in Appendix C (Client Registry) for the IHE ITI Patient Identifier Cross-Referencing profile. Expansion supplied; check in context. A candidate: no definition has been written.
-
Patient Master Identity Registry
PMIRcandidate -
No definition yet.
Used in Appendix C (Client Registry) for the IHE ITI Patient Master Identity Registry (PMIR) integration profile. Expansion supplied; check in context. A candidate: no definition has been written.
- Person-focused Health could-not-extract
-
The paper uses the phrase but never states what it is.
The centre of Figure 1, which the four factors surround. The paper does not define it; the nearest statements are the vision of health data that 'travels with them' and a 'standards-based longitudinal health record that supports the patient over time'. Recorded so the RA can decide whether it matches its own person-centred terms.
-
Personal Health Record
PHRcandidate -
No definition yet.
Described in Appendix C (Lifelong Health Record, Terminology and Scope) as the person-facing application (such as a Digital Health Wallet) through which individuals access, view, and contribute to their health data, distinct from the underlying LHR data infrastructure. A candidate: no standalone glossary definition has been written.
- Point Solution could-not-extract
-
Characterised by origin and funding only; no defining sentence.
Used for tools 'developed for vertical health programs and financed through vertical funding allocations'. That describes how they arise, not what they are, so no definition is recorded.
-
Point-of-Service Applications
POScandidate -
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.
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review. The draft marks this entry [Under review]. Also categorized in SFP handbook §3.2 Fig. 3 (who-iris/library/9789240120747-eng/sections/sec-020-32-link-to-the-enterprise-architecture.md, page-034.md, p. 22, citing DIIG) into reused POS applications and unique POS applications.
- Product candidate
-
A concrete offering, bundling services and data, that is made available to stakeholders.
The RA draft's own glossary wording, verbatim (folio/dpi-h-ra/glossary/t-glossary-lead-a31853.md). Wording alternative in RA Table 3.1 (library/who-dpi-h-reference-architecture-draft-v1/sections/sec-026-31-the-architecture-description-approach.md): "A coherent offering that bundles services and data for use by stakeholders." Note: in the PC (9789240116191-eng) and SFP (9789240120747-eng) handbooks, the bare word 'product' is used as a synonym for `generic-product` (a health product / medicine); per owner decision 2026-10-31 (smart-ra#142), `product-master-data` and `generic-product` are separate concepts and no homonym split is needed on Product Master Data.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Product ; views: Metamodel, Metamodel vs EIRA
-
Product Catalogue Management Tool
PCMTcandidate -
No definition yet.
Distinguished from the Product Registry in the Appendix C comparison table as the functional application through which an operationally enriched health product catalogue is authored, governed, and published. A candidate: no standalone glossary definition has been written.
-
Product Master Data
PMDcandidate -
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.
PC handbook Introduction wording, verbatim (who-iris/library/9789240116191-eng/sections/page-010.md, p. 10). Shared concept across PC (9789240116191-eng), SC (9789240101197-eng), and SFP (9789240120747-eng). Per owner decision 2026-10-31 (smart-ra#141, smart-ra#142): one concept, with no homonym split needed against the RA's architectural `product` concept.
-
Product Registry
PRcandidate -
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 a jurisdiction.
Verbatim lead sentence from Appendix C (Product Registry, 1 What It Is). Also abbreviated PR across the Digital Transformation Handbooks. A candidate until the RA editors adopt it through the public review.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Product Registry , Product Registry ; views: DPI-H Reference Architecture — Integrated View (Fig. 3.2), DPI-H Reference Architecture — DPI-H layers (Fig. 3.5), REDDHI and its full-STAC foundations (Fig. 2.2), Components draft, Components, DHSC Architecture Framework (DTH SC Fig. 14), TPHR Sub-goal #1 Layered View (Fig. 3.3), Q&CC Sub-goal #1 Layered View (Fig. 3.5)
-
Public Financial Management
PFMcandidate -
No definition yet.
Expanded in Section 1.2.3 and Appendix C (Benefits Package Registry). A candidate: no definition has been written.
Depicted in ArchiMate dpi-h-ra 0.2.0-draft.3: Public Financial Management ; views: High Level View - Health Financing
-
Public Health Surveillance Platform
PHSPcandidate -
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 and events.
Verbatim lead sentence from Appendix C (Public Health Surveillance Platform, 1 What It Is). Abbreviated PHSP throughout the RA draft. A candidate until the RA editors adopt it through the public review.
-
Public Key Infrastructure
PKIcandidate -
No definition yet.
Expanded in Appendix C (Client Registry) and Section 3.6.4 (GDHCN). A candidate: no definition has been written.
R
-
Reference Architecture
RAcandidate -
A technology-neutral blueprint that captures the common building blocks, relationships, and design principles of a technical environment.
The RA draft's own glossary wording, verbatim (folio/dpi-h-ra/glossary/t-glossary-lead-a31853.md). Wording alternative in RA §1.1.1 body (library/who-dpi-h-reference-architecture-draft-v1/sections/sec-001-111-what-is-a-reference-architecture-and-why-doe.md): "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." Both are recorded as candidates; neither is chosen (smart-ra#133 S1).
- Registry candidate
-
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.
The RA draft's own glossary wording, verbatim (folio/dpi-h-ra/glossary/t-glossary-lead-a31853.md); the draft marks this entry [Under review]. Near-identical wording alternatives across the DTH corpus (smart-ra#133 S1, smart-ra#139, smart-ra#142): (1) PHC handbook glossary (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 11): "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." (2) SC handbook glossary (who-iris/library/9789240101197-eng/sections/page-009.md, p. 9): "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." (3) PC handbook glossary (who-iris/library/9789240116191-eng/sections/page-009.md, p. 9): "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." (4) SFP handbook glossary (who-iris/library/9789240120747-eng/sections/page-010.md, p. 10, truncated in source PDF): "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 predefined canonical minimum data etc." All five are recorded as candidates; none is chosen.
- Repository could-not-extract
-
The draft lists the term with no definition.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Repository ; views: Semantic governance capabilities, roles and tools (Fig. A.1), Metadata Registry Governance
-
Request for Quotation
RFQcandidate -
Request for quotation
SC handbook abbreviations expansion ('request for quotation', who-iris/library/9789240101197-eng/sections/page-007.md, p. 7). The PHC handbook abbreviations list (who-iris/library/9789240093362-eng/sections/sec-001-abbreviations.md) has no RFQ entry (checked for smart-ra#200).
-
Resilient Essential Data and Digital Health Infrastructure
REDDHIcandidate -
No definition yet.
-
Resilient Essential Data and Digital Health Infrastructure
REDDHIcandidate -
No definition yet.
Named in the RA draft's Acronyms table, which gives the expansion used as prefLabel, and introduced in Chapter 2 as the health-sector framing of DPI-H. A candidate: no standalone glossary definition has been written.
-
Routine Health Information System
RHIScandidate -
No definition yet.
Expanded in Appendix C (Health Management Information System, Terminology and Scope) as a common alternative name for a Health Management Information System (HMIS). A candidate: no standalone definition has been written.
S
-
Semantic Governance Infrastructure
SGIcandidate -
The Semantic Governance Infrastructure (SGI) 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.
Introduced in Section 3.4.5 and detailed in Appendix F (Table F: SGI Capability Details). A candidate until the RA editors adopt it through the public review.
-
No definition yet.
Expanded in Appendix C (Lifelong Health Record, Terminology and Scope), where the OpenHIE Shared Health Record (SHR) specification (SHRF-*, SHRWF-*) is aligned with and extended by the DPI-H Lifelong Health Record (LHR). A candidate: no standalone glossary definition has been written.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Shared Health Record ; views: SHR
-
Sharing Value Sets, Codes, and Maps
SVCMcandidate -
No definition yet.
Expanded in Appendix C (Terminology Service) as the IHE ITI profile used by the OpenHIE Terminology Service specification. A candidate: no definition has been written.
-
SMART Guidelines
SMARTcandidate -
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.
The RA draft's own glossary wording, verbatim (folio/dpi-h-ra/glossary/t-glossary-lead-a31853.md). Substantive and wording alternatives across the DTH corpus (smart-ra#133 S1, smart-ra#139, smart-ra#140, smart-ra#142): (1) PHC handbook glossary (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 11) and SFP handbook glossary (who-iris/library/9789240120747-eng/sections/page-011.md, p. 11): "Standards-based, Machine-readable, Adaptive, Requirements-based, and Testable Guidelines are recommended digital capabilities, health and data content aligned with normative recommendations. They represent packages of comprehensive documentation and reusable digital health components (e.g. health content, interoperability standards, code libraries, algorithms, technical and operational specifications) that facilitate country adaptation and adoption of clinical and public health protocols, health systems strengthening recommendations, and data and interoperability standards into digital health information systems with fidelity. SMART Guidelines serve as a starting point and as foundational specifications to advance the development of robust person-centred digital systems. These specifications are software-agnostic, context-agnostic, and are applicable to all levels of digital maturity (10,23)." (2) SC handbook glossary (who-iris/library/9789240101197-eng/sections/page-009.md, p. 9): "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. The 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 (12, 13)." (3) PC handbook glossary (who-iris/library/9789240116191-eng/sections/page-009.md, p. 9): "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. 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.11, 12" All are recorded as candidates; none is chosen.
-
SMART Health Links
SHLcandidate -
No definition yet.
Used in the WHO SMART Guidelines and Global Digital Health Certification Network (GDHCN) ecosystem for verifiable, patient-mediated sharing of health summaries and links. Shared across the reference architecture and Digital Transformation Handbooks. A candidate: no definition has been written.
- SNOMED CT candidate
-
Systematized Nomenclature of Medicine Clinical Terms is a structured clinical terminology standard for use in electronic health records.
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review.
-
SNOMED GPS
SNOMED-GPScandidate -
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.
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review. Expanded in PHC handbook Abbreviations (who-iris/library/9789240093362-eng/sections/sec-001-abbreviations.md, pp. 7-8) as "SNOMED-GPS" = "Systematized Nomenclature of Medicine-Global Patient Set" and cited in SFP handbook §4.4 (who-iris/library/9789240120747-eng/sections/sec-025-44-outline-data-requirements.md, page-042.md, p. 30).
-
No definition yet.
Expanded in Appendix C (Benefits Package Registry). A candidate: no definition has been written.
- Solution Architecture candidate
-
The design of a specific application component or HDPI expressed through specifications and diagrams
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review. The draft marks this entry [Under review].
- Stakeholder candidate
-
An individual, role, or organisation with an interest in the outcomes of the architecture.
The RA draft's own glossary wording, verbatim (folio/dpi-h-ra/glossary/t-glossary-lead-a31853.md). Substantive and wording alternatives across the corpus (smart-ra#133 S1, smart-ra#140): (1) RA Table 3.1 (library/who-dpi-h-reference-architecture-draft-v1/sections/sec-026-31-the-architecture-description-approach.md): "An individual, team, or organisation with interests in, or concerns relative to, the architecture." (2) SC handbook glossary (who-iris/library/9789240101197-eng/sections/page-009.md, p. 9): "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." (4) DIIG Annex 1.1 Glossary (who-iris/library/9789240010567-eng/sections/page-141.md, p. 129): "Any person who is affected by or interested in the consequences of the digital health implementation; stakeholders include the planning team, end-users, beneficiaries and funders." (Also enumerated in SFP handbook §1.1, who-iris/library/9789240120747-eng/sections/sec-009-11-analyse-key-stakeholders.md, page-020.md, p. 8.) All are recorded as candidates; none is chosen.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Stakeholder , Stakeholder ; views: Semantic governance capabilities, roles and tools (Fig. A.1), Metadata Registry Governance, Metamodel, Metamodel vs EIRA
-
Standards Development Organization
SDOcandidate -
No definition yet.
Expanded in Section 1.4 (Open Standards and Specifications) and Section 3.4.5. A candidate: no definition has been written.
-
Standards-based, Machine-readable, Adaptive, Requirements-based, Testable Guidelines
SMART Guidelinescandidate -
No definition yet.
-
Supplier Registry
SRcandidate -
The Supplier Registry is the authoritative master data source for identity, classification, and regulatory status of suppliers engaged in the health supply chain — including manufacturers, distributors, wholesalers, third-party logistics providers, importers, and procurement agents.
Verbatim lead sentence from Appendix C (Supplier Registry, 1 What It Is). A candidate until the RA editors adopt it through the public review.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Supplier Registry ; views: DPI-H Reference Architecture — Integrated View (Fig. 3.2), DPI-H Reference Architecture — DPI-H layers (Fig. 3.5), DHSC Architecture Framework (DTH SC Fig. 14)
-
Supply Chain Information System Maturity Model
SCISMMcandidate -
Supply Chain Information System Maturity Model (USAID)
SC handbook abbreviations expansion (who-iris/library/9789240101197-eng/sections/page-007.md, p. 7). Wording alternative in PC handbook abbreviations (who-iris/library/9789240116191-eng/sections/page-007.md, p. 7): "Supply Chain Information Systems Maturity Model" (plural 'Systems', without '(USAID)'). Both are recorded as candidates; neither is chosen (smart-ra#133 S1).
-
Surveillance Outbreak Response Management and Analysis System
SORMAScandidate -
No definition yet.
Named in Appendix D.1 (Public Health Surveillance Platform) as a mobile-capable surveillance and outbreak-response tool supporting case registration, contact tracing, and laboratory workflows. A candidate: no definition has been written.
-
Sustainable Development Goal
SDGcandidate -
No definition yet.
-
Sustainable Development Goal
SDGcandidate -
Sustainable Development Goal
PHC handbook abbreviations expansion ('Sustainable Development Goal', singular, who-iris/library/9789240093362-eng/sections/sec-001-abbreviations.md, p. 7). Wording alternative in SC handbook abbreviations (who-iris/library/9789240101197-eng/sections/page-007.md, p. 7): "Sustainable Development Goals" (plural). Both are recorded as candidates; neither is chosen (smart-ra#133 S1).
-
Systematized Nomenclature of Medicine - Clinical Terms
SNOMED CTcandidate -
No definition yet.
-
Systematized Nomenclature of Medicine – Global Patient Set
SNOMED GPScandidate -
No definition yet.
- Systems Architecture candidate
-
The technical framework of the system depicted in a conceptual model that defines how the system is structured and how its elements are connected.
PHC handbook glossary wording, verbatim (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 11). Wording alternative in SC handbook glossary (who-iris/library/9789240101197-eng/sections/page-009.md, p. 9): "A technical framework based on a conceptual model that defines how the system should be structured and how its elements should be connected." Internal alternative in PHC handbook §4.4 body under 'system architecture' (who-iris/library/9789240093362-eng/sections/sec-023-44-design-system-architecture.md, pp. 56-60): "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." All are recorded as candidates; none is chosen (smart-ra#133 S1, smart-ra#200).
T
-
Technical Working Group
TWGcandidate -
No definition yet.
Used in Appendix C (Logical Information Model Repository) and listed in the abbreviations tables of the Digital Transformation Handbooks. Expansion supplied; check in context. A candidate: no definition has been written.
-
Terminology Service
TScandidate -
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.
Verbatim lead sentence from Appendix C (Terminology Service, 1 What It Is). Abbreviated TS throughout the RA draft and downstream Digital Transformation Handbooks. A candidate until the RA editors adopt it through the public review.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Terminology Service , Terminology Service ; views: DPI-H Reference Architecture — Integrated View (Fig. 3.2), DPI-H Reference Architecture — DPI-H layers (Fig. 3.5), TPHR High Level Layered View (Fig. 3.4), ALL High Level - Health Workforce, Interoperability Layer, TPHR Sub-goal #1 Layered View (Fig. 3.3)
-
The Open Group Architecture Framework
TOGAFcandidate -
No definition yet.
-
The Open Group Architecture Framework
TOGAFcandidate -
No definition yet.
Named in the RA draft's Acronyms table, which gives the expansion used as prefLabel, and in Chapter 3 and the Digital Transformation Handbooks. A candidate: no definition has been written.
- TOGAF candidate
-
The Open Group Architecture Framework, an enterprise architecture framework and method, published by The Open Group, for developing an enterprise architecture.
Added to the RA glossary table in CS-001 (smart-ra#185, public comments No. 136 and No. 327), per committee feedback (CL). A candidate until the RA editors adopt it through the public review.
-
Total Cost of Ownership
TCOcandidate -
The resources required to support a digital health intervention throughout its life cycle.
SC handbook glossary wording, verbatim (who-iris/library/9789240101197-eng/sections/page-009.md, p. 9). Shared concept across SC (Ch. 3 Fig. 23, p. 49) and SFP (p. 49); recorded as a candidate.
- Traceability candidate
-
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).
SC handbook glossary wording, verbatim (who-iris/library/9789240101197-eng/sections/page-009.md, p. 9, citing the WHO policy paper on traceability of medical products, ref. 14). Internal/substantive alternative in SC handbook Ch. 4 boxed definition (who-iris/library/9789240101197-eng/sections/page-054.md, p. 54, citing GS1): "Traceability is the ability to trace the history, application or location of an object. In a supply chain context, it is the ability to see the movement of health products across the supply chain." Shared across dth-sc, dth-pc, and dth-sfp; both definitions are recorded as candidates and neither is chosen (smart-ra#133 S1, smart-ra#140).
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Traceability , Traceability ; views: Components draft, Health Supply Chain Partners and Processes (DTH SC Figs. 1-3), DHSC Architecture Framework (DTH SC Fig. 14), Track and Trace through DHSC Components (DTH SC Fig. 24)
- Trade Item candidate
-
Trade items are manufacturer-specific branded health products that are identifiable and unique to a particular brand or manufacturer.
Owner decision 2026-10-31 (smart-ra#142 item 1, smart-ra#139): Trade Item is the shared WHO concept with this narrow definition from the Product Catalogue handbook Ch. 2 body (who-iris/library/9789240116191-eng/sections/page-028.md, p. 28). The GS1 trade item is a separate external concept and the WHO term's broadMatch (every WHO Trade Item is a GS1 trade item, not the reverse: GS1's also covers services). The PC handbook glossary (who-iris/library/9789240116191-eng/sections/page-009.md, p. 9) and SFP handbook glossary (who-iris/library/9789240120747-eng/sections/sec-002-glossary.md, page-011.md, p. 11) print the GS1 wording — "Products or services that are priced, ordered or invoiced at any point in the supply chain" — citing GS1 (PC ref. 13, SFP ref. 19); that sentence is recorded here as a note citing GS1, not as the WHO concept's definition.
- broadMatch: www.gs1.org/standards/id-keys/gtin
U
-
Unified Terminology Governance
UTGcandidate -
No definition yet.
Expanded in Section 3.4.5 for HL7's Unified Terminology Governance (UTG) process. A candidate: no definition has been written.
-
Unique Device Identification
UDIcandidate -
No definition yet.
Used in Appendix C (Product Registry) for ISO/regulatory medical device identification. Shared with dth-sfp. Expansion supplied; check in context. A candidate: no definition has been written.
-
United Nations Standard Products and Services Code
UNSPSCcandidate -
No definition yet.
Used in Appendix C (Product Registry) alongside ATC and GPC, and shared with dth-pc and dth-sfp. Expansion supplied; check in context. A candidate: no definition has been written.
- Use Case candidate
-
A use case is an example scenario of how the end-user will use the system.
PHC handbook glossary wording, verbatim (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 11). Wording alternative in SC handbook glossary (who-iris/library/9789240101197-eng/sections/page-009.md, p. 9): "An example scenario of how the end user will use a system." Both are recorded as candidates; neither is chosen (smart-ra#133 S1).
-
User Acceptance Testing
UATcandidate -
User acceptance testing (UAT) is conducted to see whether the end-users are satisfied with the end product (24).
PHC handbook glossary wording, verbatim (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 11). Wording alternatives across the DTH corpus (smart-ra#133 S1): (1) PC handbook glossary ('User acceptance testing (UAT)', who-iris/library/9789240116191-eng/sections/page-009.md, p. 9): "UAT is done to see whether the end-users are satisfied with the end product.14" (2) SFP handbook glossary ('User acceptance testing (UAT)', who-iris/library/9789240120747-eng/sections/page-011.md, p. 11): "User acceptance testing is done to see whether the end users are satisfied with the end product (20)." All three are recorded as candidates; none is chosen.
- User Persona candidate
-
A generic or archetypical profile of an end-user that is representative of a single type of end-user.
PHC handbook glossary wording under 'User persona', verbatim (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 11). Internal and cross-DTH alternatives (smart-ra#133 S1): (1) PHC handbook §3.2.1 body (who-iris/library/9789240093362-eng/sections/sec-013-32-get-to-know-the-users.md, pp. 33-35): "A user persona is a generic depiction of a relevant stakeholder, or end-user of the system who would be interacting with the PCPOSS." (2) SFP handbook glossary under 'Persona' (who-iris/library/9789240120747-eng/sections/page-010.md, p. 10): "A generic aggregate description of a person involved in or benefiting from a health programme." All three are recorded as candidates; none is chosen.
- User Story (Requirements) candidate
-
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).
PHC handbook glossary wording, verbatim (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 11). Internal and platform alternatives (smart-ra#133 S1): (1) PHC handbook §3.2.3 body (who-iris/library/9789240093362-eng/sections/sec-013-32-get-to-know-the-users.md, pp. 33-35): "User stories are the start of generating a long list of requirements, in non-technical terms, that will help the technical team to determine the more specific functional requirements of the system." and the template "“As a… [user persona], I want to… [do what I want to be able to do differently using an electronic system], so that… [reason for wanting that functionality].”" (2) Platform glossary `user-story` (folio-assistant-core/glossary/cat-harness.glossary.json), which binds the story to a Role rather than a user persona: "What a reader acting in a Role is trying to do, told as that role: as a <role>, I want <want>, so that <so that>." Also used as the functional requirements template ("As a … / I want … / So that ...") in SFP handbook §4.5 Table 12 (who-iris/library/9789240120747-eng/sections/sec-026-45-gather-requirements.md, page-043.md, p. 31).
V
- Value candidate
-
The benefit or utility a stakeholder gains from using a service, product, or capability.
The RA draft's own wording, verbatim. A candidate until the RA editors adopt it through the public review.
Depicted in ArchiMate dpi-h-ra 0.3.0-draft.1: Value ; views: Metamodel, Metamodel vs EIRA
W
-
WHO Family of International Classifications
WHO-FICcandidate -
No definition yet.
Named in Appendix C (Terminology Service) as an international terminology authority (alongside SNOMED International and Regenstrief) whose classifications (ICD-11, ICF, ICHI) national terminology services synchronise with. Expansion supplied; check in context. A candidate: no definition has been written.
-
WHODrug Global
WHODrugcandidate -
No definition yet.
Used in Appendix C (Product Registry) for the international reference dictionary of medicinal products maintained by the Uppsala Monitoring Centre (UMC). Shared with dth-pc and dth-sfp. A candidate: no definition has been written.
- Workflow candidate
-
The sequence of activities from one task to another (see section 3.3).
PHC handbook glossary wording, verbatim (who-iris/library/9789240093362-eng/sections/sec-002-glossary.md, p. 11). Internal and cross-DTH alternatives (smart-ra#133 S1): (1) PHC handbook §3.3 body (who-iris/library/9789240093362-eng/sections/sec-014-33-map-business-processes-and-workflows.md, pp. 35-39): "Workflows are a visual representation of the progression of activities (tasks, events, interactions) performed within a business process (45)." (2) SFP handbook glossary (who-iris/library/9789240120747-eng/sections/page-011.md, p. 11, citing DIIG/DAK): "A visual representation of the progression of activities (tasks, events, decision points) in a logical flow illustrating the interactions within the business process (21)." (PHC glossary defines a workflow as the sequence of activities itself; PHC §3.3 and SFP glossary define it as the visual representation of that progression.) All are recorded as candidates; none is chosen.