DTH candidates: methodologies, processes and glossary

Bean 5blc, owner 2026-10-01: the handbooks are “also source of methodologies / processes / glossary”. The bean’s rule is that the owner reviews this list before anything is authored, so this page proposes and authors nothing.

Every row cites its handbook. The full record, with each verbatim quote, section id and the steps, actors, inputs and outputs, is dth-candidates-2026-10-02.json; every one of its 421 quotes was checked programmatically against the ingested section. Sources: PHC = DTH for primary health care (9789240093362), SC = DTH for health supply chain architecture (9789240101197), PC = DTH for health product catalogue (9789240116191), RA = Reference Architecture for DPI-H, DRAFT V1.0. status is new, overlaps:<path> or extends:<path> against what this repository already holds.

Read these first

  1. SC Annex 3 contradicts smart-base/methodologies/diig.md. The annex ranks bottlenecks by summing three 1–3 scores; diig.md adopts the same three criteria and explicitly refuses the arithmetic. Adopting the annex as written would reverse that refusal (dth-dhsc-challenge-prioritization).
  2. All three DTHs reproduce the DIIG’s seven-phase figure, which diig.md does not model (it renders the nine chapters). Recorded in #1830 too.
  3. PHC Chapter 3 maps almost one-to-one onto smart-base/processes/l2-dak-authoring.bpmn — personas, workflows, data dictionary, decision logic, indicators and requirements. PHC also prescribes BPMN drawing rules worth checking against the bpmn-authoring skill.
  4. “Actor” collides. The RA’s actor is an abstract role a system realises; the platform’s actor is a concrete participant that takes on roles — the RA’s term is the platform’s “role”.
  5. Definitions disagree across the handbooks for enterprise architecture, interoperability (four variants), SMART Guidelines (three framings), functions, non-functional requirements, and digitization/digitalization; three terms are defined two ways inside a single handbook. The table below lists every one.

Source defects found on the way, recorded rather than corrected: SC Chapter 1 announces five steps and lists four; PC chapter 04 has two titles and two chapter numberings; PC Chapter 05 Step 3 repeats Step 2’s rows; the RA leaves “Health Information Exchange” and “Repository” undefined.

Methodologies (16)

idtitlestatussource
dth-phc-stepwise-digitizingStepwise approach to digitizing primary health care (PCPOSS)extends:methodologies/diig.mdPHC p.26-27; PHC p.26-27
dth-digital-health-enterprise-seven-phasesPlanning and implementing a digital health enterprise: seven phases (DIIG-derived figure)overlaps:methodologies/diig.mdPHC p.24-26; SC p.15
dth-phc-requirements-gathering-methodsRequirements-gathering methods (desk review, observation, interviews, workshops)overlaps:processes/crdm-needs.bpmnPHC p.30-33; PHC p.30-33
dth-dhsc-stepwise-approachStepwise approach to digitalizing the health supply chain (DHSC)extends:methodologies/diig.mdSC p.14; SC p.13
dth-dhsc-strategyDefining a holistic DHSC strategy (Chapter 1, Steps 1-4)newSC p.21; SC p.26
dth-dhsc-architectureDefining the DHSC architecture (Chapter 2, Steps 1-3)newSC p.29; SC p.31
dth-dhsc-implementationPlanning for scalable implementation and sustainable operations (Chapter 3, Steps 1-4)overlaps:methodologies/diig.mdSC p.45; SC p.46
dth-dhsc-challenge-prioritizationTemplate for prioritizing DHSC challenges (Annex 3) - bottleneck scoringoverlaps:methodologies/diig.mdSC p.68
dth-npc-stepwise-approachStepwise approach to a national product catalogue (NPC) and product master data management (chapters 01-05)extends:methodologies/diig.mdPC p.17; PC p.12
dth-smart-guidelines-knowledge-layersSMART Guidelines five knowledge layers (L1-L5) as a stepwise pathwayoverlaps:skills/content/authoring-who-smart-guidelines/smart-stack-layering.mdSC p.16; PC p.14
ra-goals-to-dpih-mappingMethodology: mapping health goals to DPI-H (goals-first, TOGAF-based)newRA p.48-49; RA p.49-50
ra-archimate-architecture-descriptionArchitecture description with a typed ArchiMate subset (elements, relationships, views)newRA p.52-59; RA p.52-59
ra-conformance-and-testingConformance and testing across architecture and components (Section 3.7)newRA p.90-94; RA p.95-96
ra-phased-implementation-to-reddhiCharting a path to REDDHI: four entry points and a four-phase implementation approachextends:methodologies/diig.mdRA p.100-101; RA p.101-104
ra-navigating-legacy-systemsNavigating legacy systems (assess, integrate, replace at transition points, stop new silos)newRA p.104; RA p.104
ra-measuring-progress-and-impactMeasuring progress and impact (four dimensions, baselines, process evaluation)newRA p.110-111; RA p.110

Processes (24)

Each could be drawn as BPMN; the JSON carries its steps, actors, inputs and outputs as the handbook states them.

idtitlestatussource
phc-understand-user-requirementsPHC Chapter 3 - Understand user requirementsoverlaps:processes/l2-dak-authoring.bpmnPHC p.27-30; PHC p.47-52
phc-business-process-workflow-mappingPHC 3.3 - Map business processes and workflows (as-is / to-be, BPMN)overlaps:processes/l2-dak-authoring.bpmnPHC p.35-39; PHC p.35-39
phc-streamline-data-and-data-dictionaryPHC 3.4-3.5 - Streamline data collection and indicator reporting into a data dictionaryoverlaps:processes/l2-dak-authoring.bpmnPHC p.39-42; PHC p.42-44
phc-decision-support-logic-and-schedulesPHC 3.6-3.7 - Determine decision-support logic and map health service schedulesoverlaps:processes/l2-dak-authoring.bpmnPHC p.44-47; PHC p.47
phc-gather-and-prioritize-requirementsPHC 3.8 - Gather and prioritize functional and non-functional requirementsoverlaps:processes/crdm-requirements-definition.bpmnPHC p.47-52; PHC p.47-52
phc-design-and-adaptationPHC Chapter 4 - Undertake design and adaptationnewPHC p.47-52; PHC p.60-64
phc-prototype-design-and-testingPHC 4.3 - Develop and test the prototype designoverlaps:processes/wireframe-design-review.bpmnPHC p.53-56; PHC p.53-56
phc-training-testing-rolloutPHC Chapter 5 - Conduct training, testing and roll-outnewPHC p.64-65; PHC p.65-68
phc-deploy-the-systemPHC 5.3 - Deploy the system (ad hoc set of roll-out activities)newPHC p.65; PHC p.65
phc-prepare-for-scale-upPHC Chapter 6 - Prepare for scale-up and phase out paper/legacy systemsnewPHC p.68-71; PHC p.71
dhsc-define-strategyDHSC Chapter 1 - Define a holistic DHSC strategynewSC p.22; SC p.25
dhsc-define-architectureDHSC Chapter 2 - Define the DHSC architecturenewSC p.32; SC p.42
dhsc-implement-interventionsDHSC Chapter 3 - Plan, budget and implement each DHSC interventionoverlaps:methodologies/diig.mdSC p.47; SC p.51
dhsc-traceability-event-flowDHSC Chapter 4 - Track, trace and verify a health product (centralized traceability model)newSC p.55; SC p.56
npc-01-regulatory-policiesNPC 01 - Establish regulatory policies to promote product master data standardizationnewPC p.21; PC p.23
npc-02-data-management-governanceNPC 02 - Institute data management and governance policiesnewPC p.25; PC p.32
npc-03-deploy-technologyNPC 03 - Deploy appropriate technology to manage product master datanewPC p.36; PC p.37
npc-04-manage-changeNPC 04 - Manage change to institutionalize standardized product master datanewPC p.39; PC p.40
npc-05-build-capacityNPC 05 - Build capacity to sustainably manage the NPCnewPC p.43; PC p.44
ra-national-architecture-assessmentRA 4.1 - National digital health architecture assessment -> roadmapnewRA p.99-100; RA p.99-100
ra-semantic-governance-content-lifecycleRA 3.4.5 - Semantic Governance Infrastructure: governed content lifecycleoverlaps:fhir-harness/skills/content/fhir-ig-authoring/terminology-management.mdRA p.68-73; RA p.68-73
ra-operational-to-strategic-escalationRA 3.4.4 - Escalation from operational to strategic governancenewRA p.67-68; RA p.67-68
ra-component-conformance-testingRA 3.7 / 4.3.5 - Conformance testing of a component in an actor rolenewRA p.90-94; RA p.109
ra-adoption-mapping-and-coverageRA 3.7.5 - Evaluate country adoption of the reference by mapping (coverage and gaps)newRA p.96-97; RA p.96-97

Glossary terms that conflict (40 of 241)

termdefined inconflicts withseveritydifference
Actor (conformance model)RAfolio-assistant-core/glossary/cat-harness.glossary.jsonsubstantiveThe platform’s “actor” is a concrete participant that takes on roles; the RA’s “actor” is an abstract information-processing ROLE realised by concrete systems - closer to the platform’s “role”. Adopting the RA term unqualified would collide.
Application ServiceRARAwordingRA glossary vs Table 3.1 phrasing.
CapabilityRARAwordingRA glossary: “A high-level ability … in order to achieve its goals”; RA Table 3.1: “An ability … expressed independently of how it is implemented”.
DeployPHC, SCSCwordingWording differs (automatic comparison; not reviewed as substantive).
Digital healthPHC, SC, RASCwordingNear-identical: differs only in phrasing, punctuation or citation markers.
Digital healthPHC, SC, RASCinternalPHC, SC and RA glossaries agree; the SC introduction body quotes a different Global Strategy definition, “the field of knowledge and practice associated with the development and use of digital technologies to improve health”.
Digital healthPHC, SC, RARAwordingNear-identical: differs only in phrasing, punctuation or citation markers.
Digital Public Infrastructure (DPI)RARAwordingGlossary uses the G20 definition; section 1.1.2 also gives the World Bank framing (“an approach to digitalization”).
Digital transformationPHC, SC, PCSCwordingSC reorders the same content and prefixes “In the health context”; PC writes “person centred”.
DigitalizationPHC, SC, PCSCsubstantiveSC and PC add the claim that digitalization is “the second step” in/towards digital transformation; PHC does not.
DigitalizationPHC, SC, PCPCsubstantiveSC and PC add the claim that digitalization is “the second step” in/towards digital transformation; PHC does not.
DigitizationPHC, SC, PCSCsubstantiveSC and PC add a sequencing claim (digitization is the initial step in/towards digital transformation) that PHC does not make; SC also adds “manual”.
DigitizationPHC, SC, PCPCsubstantiveSC and PC add a sequencing claim (digitization is the initial step in/towards digital transformation) that PHC does not make; SC also adds “manual”.
End-userPHC, SC, PCSCwordingWording differs (automatic comparison; not reviewed as substantive).
Enterprise architecturePHC, SC, RASCwordingNear-identical: differs only in phrasing, punctuation or citation markers.
Enterprise architecturePHC, SC, RARAsubstantivePHC and SC: “a blueprint of business processes, data, systems and technologies”; RA: “the organising logic for business processes and IT infrastructure” reflecting the operating model, marked [Under review].
FeaturesPHC, SC, PCSCwordingDomain examples differ; PC says “your system”.
FeaturesPHC, SC, PCPCwordingDomain examples differ; PC says “your system”.
Functional requirementsPHC, SC, PCSCwordingPHC/PC: tasks of “the health system process”; SC: tasks of “the business process”.
Functional requirementsPHC, SC, PCPCwordingPHC/PC: tasks of “the health system process”; SC: tasks of “the business process”.
FunctionsPHC, SCSCsubstantivePHC: functions are “how features are implemented”; SC: functions are “Business processes within a system that help the system perform”.
Generic product or product informationPCPCwordingGlossary: identifying details “excluding any manufacturer-specific information”; body: items “that conceal the brand or manufacturer information”.
governance (body, health supply chain)SC, RARAsubstantiveSC (supply chain): “the process of establishing and implementing policies, procedures and mechanisms”; RA: “the set of arrangements through which decision authority is distributed, exercised and accounted for”.
Health Digital Public Infrastructure (DPI-H)RARAwordingBody adds the systems-and-specifications sentence.
InteroperabilityPHC, SC, PC, RAPHCinternalPHC/PC glossaries agree; SC adds “safe” and “help ensure good health outcomes”; PHC section 4.4 body drops “value sets, concepts” and says standards “should be defined by the EA”; RA: “the standards-based capability of heterogeneous information systems to communicate, exchange data, and use the exch
InteroperabilityPHC, SC, PC, RASCsubstantivePHC/PC glossaries agree; SC adds “safe” and “help ensure good health outcomes”; PHC section 4.4 body drops “value sets, concepts” and says standards “should be defined by the EA”; RA: “the standards-based capability of heterogeneous information systems to communicate, exchange data, and use the exch
InteroperabilityPHC, SC, PC, RARAsubstantivePHC/PC glossaries agree; SC adds “safe” and “help ensure good health outcomes”; PHC section 4.4 body drops “value sets, concepts” and says standards “should be defined by the EA”; RA: “the standards-based capability of heterogeneous information systems to communicate, exchange data, and use the exch
Non-functional requirementsPHC, SC, PCSCsubstantivePHC: attributes and features “to ensure usability and overcome technical and physical constraints”; SC: “how the digital system needs to operate and perform” for business-process tasks; PC: “attributes and constraints … to ensure its quality and performance”.
Non-functional requirementsPHC, SC, PCPCsubstantivePHC: attributes and features “to ensure usability and overcome technical and physical constraints”; SC: “how the digital system needs to operate and perform” for business-process tasks; PC: “attributes and constraints … to ensure its quality and performance”.
Open sourcePHC, SC, PCSCwordingWording differs (automatic comparison; not reviewed as substantive).
Open standardsPHC, SC, PCSCwordingNear-identical: differs only in phrasing, punctuation or citation markers.
organogramSC, PCPCwordingWording differs (automatic comparison; not reviewed as substantive).
OutcomeRARAwordingRA glossary: “An end result or consequence of a set of activities”; RA Table 3.1: “An achieved, and often measurable, result”.
ProductRARAwordingRA glossary “A concrete offering” vs Table 3.1 “A coherent offering”. HOMONYM WARNING: unrelated to “product” in the PC handbook (a health product / generic product).
Reference ArchitectureRARAwordingBody adds the purpose clause.
RegistryPHC, SC, PC, RASCwordingNear-identical: differs only in phrasing, punctuation or citation markers.
RegistryPHC, SC, PC, RAPCwordingNear-identical: differs only in phrasing, punctuation or citation markers.
RegistryPHC, SC, PC, RARAwordingNear-identical: differs only in phrasing, punctuation or citation markers.
SMART GuidelinesPHC, SC, PC, RASCsubstantivePHC: “recommended digital capabilities, health and data content aligned with normative recommendations”; SC: “The WHO guidelines for developing” SMART components; PC and RA: “a comprehensive set of reusable digital health components” with a five-step pathway.
SMART GuidelinesPHC, SC, PC, RAPCsubstantivePHC: “recommended digital capabilities, health and data content aligned with normative recommendations”; SC: “The WHO guidelines for developing” SMART components; PC and RA: “a comprehensive set of reusable digital health components” with a five-step pathway.
SMART GuidelinesPHC, SC, PC, RARAsubstantivePHC: “recommended digital capabilities, health and data content aligned with normative recommendations”; SC: “The WHO guidelines for developing” SMART components; PC and RA: “a comprehensive set of reusable digital health components” with a five-step pathway.
stakeholderSC, RARAsubstantiveSC: “anyone who is affected by or interested in the consequences of the efforts”; RA glossary: “An individual, role, or organisation with an interest in the outcomes of the architecture”; RA Table 3.1: “…in the architecture and its outcomes”.
stakeholderSC, RARAsubstantiveSC: “anyone who is affected by or interested in the consequences of the efforts”; RA glossary: “An individual, role, or organisation with an interest in the outcomes of the architecture”; RA Table 3.1: “…in the architecture and its outcomes”.
Systems architecturePHC, SCPHCwordingPHC: “how the system is structured”; SC: “how the system should be structured”; PHC section 4.4 body widens it to “all the software and hardware components”.
Systems architecturePHC, SCSCwordingPHC: “how the system is structured”; SC: “how the system should be structured”; PHC section 4.4 body widens it to “all the software and hardware components”.
traceabilitySCSCinternalSC glossary: “The ability to trace something” (verify history, location or application); SC Chapter 4 body quotes GS1: the ability “to see the movement of health products across the supply chain”.
Trade itemPCPCinternalPC glossary (GS1): “Products or services that are priced, ordered or invoiced”; PC Chapter 02 body: “manufacturer-specific branded health products”.
Use casePHC, SCSCwordingWording differs (automatic comparison; not reviewed as substantive).
User acceptance testingPHC, PCPCwordingWording differs (automatic comparison; not reviewed as substantive).
User personaPHCPHCwordingGlossary: profile “of an end-user”; section 3.2.1: depiction “of a relevant stakeholder, or end-user”.
User storyPHCfolio-assistant-core/glossary/cat-harness.glossary.jsonwordingCompatible template; PHC binds the story to a user PERSONA (“As a… [user persona]”), the platform to a Role.
WorkflowPHCPHCinternalPHC glossary: “The sequence of activities from one task to another”; PHC section 3.3 body: “a visual representation of the progression of activities” within a business process.
ITUPHC, SCSCwordingPHC “Telecommunications” vs SC “Telecommunication” (the organisation’s own name is singular).
RFQSC, PCPCwordingSC “request for quotation” vs PC “Request for quote”.
SCISMMSC, PCPCwordingSC “Supply Chain Information System Maturity Model” vs PC “Supply chain information systems maturity model”.
SDGPHC, RARAwordingPHC plural “Goals” vs RA singular “Goal”.

All glossary terms (241)

termkindstatussource
Accesses (relationship)bodynewRA p.52-59
Actor (conformance model)bodyoverlaps:folio-assistant-core/glossary/cat-harness.glossary.jsonRA p.90-94
Adaptation (country-to-reference)bodynewRA p.96-97
Adoption (country-to-reference)bodynewRA p.96-97
AEFIabbreviationnewPC p.6
AIabbreviationnewRA p.1-19
AIDCabbreviationnewPC p.6
AlgorithmglossarynewPHC p.8
ANCabbreviationnewPHC p.7-8
AnnotationglossarynewPHC p.8
APIabbreviationnewPHC p.7-8
Application ComponentglossarynewRA p.1-19
Application FunctionbodynewRA p.90-94
Application InteractionbodynewRA p.90-94
Application ServiceglossarynewRA p.1-19; RA p.52-59
Artificial intelligencebodynewRA p.114-115
As-isglossarynewPHC p.8
Assignment (relationship)bodynewRA p.90-94
ATCabbreviationnewPC p.6
Benefits Package RegistrybodynewRA p.210-218
Beta versionglossarynewPHC p.8
BPMNabbreviationoverlaps:skills/process/workflow/bpmn-authoring.mdPHC p.7-8
BuildglossarynewPHC p.8
Business DomainglossarynewRA p.1-19
Business objectiveglossarynewPHC p.8
Business processglossaryoverlaps:docs/artifact/StructureDefinition-BusinessProcessWorkflow.mdPHC p.8
Business Services layerglossarynewRA p.1-19
CapabilityglossarynewRA p.1-19; RA p.52-59
Care pathwayglossarynewPHC p.8
ClientglossarynewRA p.1-19
Client RegistrybodynewRA p.125-135
Clinical protocolglossarynewPHC p.8
Community-based information systemglossarynewPHC p.8
Composes (relationship)bodynewRA p.52-59
Computable Decision Support Engine (CDSE)bodynewRA p.191-202
ConformancebodynewRA p.90-94
Coverage (adoption)bodynewRA p.96-97
CRDMabbreviationoverlaps:skills/sdlc/crdm/crdm-requirements-workflow.mdPHC p.7-8
DAKabbreviationoverlaps:docs/artifact/StructureDefinition-DAK.mdPHC p.7-8; PC p.6
Data custodian (body, ch. 02)bodynewPC p.26
Data dictionaryglossarynewPHC p.8
Data elementglossaryoverlaps:docs/artifact/StructureDefinition-CoreDataElement.mdPHC p.8; PC p.8
Data GovernanceglossarynewRA p.1-19
Data ObjectglossarynewRA p.1-19
Data owner (body, ch. 02)bodynewPC p.26
Data steward (body, ch. 02)bodynewPC p.26
DBPabbreviationnewPHC p.7-8
Decision support logicglossaryoverlaps:docs/artifact/StructureDefinition-DecisionSupportLogic.mdPHC p.8
Decision support systemglossarynewPHC p.8
Decision-support tableglossaryoverlaps:methodologies/dmn.mdPHC p.8
DeployglossarynewPHC p.8; SC p.8
DevSecOpsglossarynewPHC p.8
DH&IabbreviationnewPC p.6
DH&I WGabbreviationnewSC p.7
DHAabbreviationnewPHC p.7-8
DHSCabbreviationnewSC p.7; PC p.6
DICOMabbreviationnewPHC p.7-8
Digital adaptation kits (DAKs)glossaryoverlaps:docs/artifact/StructureDefinition-DAK.mdPHC p.9
Digital healthglossarynewPHC p.9; SC p.8
Digital health interventionglossaryoverlaps:docs/artifact/CodeSystem-CDHIv2.mdPHC p.9
digital health supply chain (DHSC) (body)bodynewSC p.12
digital health supply chain interventionglossarynewSC p.8
Digital InfrastructureglossarynewRA p.1-19
Digital Public Infrastructure (DPI)glossarynewRA p.1-19; RA p.19-21
Digital transformationglossarynewPHC p.9; SC p.8
DigitalizationglossarynewPHC p.9; SC p.8
DigitizationglossarynewPHC p.9; SC p.8
DIIGabbreviationoverlaps:methodologies/diig.mdPHC p.7-8; SC p.7
DPIabbreviationnewRA p.1-19
DPI-FabbreviationnewRA p.1-19
DPI-HabbreviationnewRA p.1-19
EAabbreviationnewPHC p.7-8
Electronic health record systemglossarynewPHC p.9
eLMISabbreviationnewPC p.6
End-userglossarynewPHC p.9; SC p.8
Enterprise architectureglossarynewPHC p.9; SC p.8
eRISabbreviationnewSC p.7
ERPabbreviationnewSC p.7
Fast Healthcare Interoperability Resources (FHIR)glossarynewRA p.1-19
FDAabbreviationnewPC p.6
FeaturesglossarynewPHC p.9; SC p.8
FHIRabbreviationnewPHC p.7-8; PC p.6
FlagglossarynewPHC p.9
foundational components (body, DHSC architecture)bodynewSC p.35
FTEabbreviationnewSC p.7
Functional applicationglossarynewRA p.1-19
Functional requirementsglossaryoverlaps:docs/artifact/StructureDefinition-FunctionalRequirement.mdPHC p.9; SC p.8
FunctionsglossarynewPHC p.9; SC p.8
GDSNabbreviationnewPC p.6
Generic product or product informationglossarynewPC p.8; PC p.28
GFPVANabbreviationnewSC p.7
GHSC-PSMabbreviationnewSC p.7
GoalglossarynewRA p.1-19
governance (body, health supply chain)bodynewSC p.45; RA p.64-65
GTINabbreviationnewPC p.6
Health Digital Public Infrastructure (DPI-H)glossarynewRA p.1-19; RA p.19-21
Health Facility RegistrybodynewRA p.135-146
Health Information ExchangeglossarynewRA p.1-19
Health Management Information System (HMIS)bodynewRA p.221-229
Health ProgrammeglossarynewRA p.1-19
Health service usersglossarynewPHC p.9
Health service user’s health recordsglossarynewPHC p.9
health supply chain information systemglossarynewSC p.8
Health Workforce RegistrybodynewRA p.146-156
HL7abbreviationnewPHC p.7-8; PC p.6
HL7 FHIR®abbreviationnewRA p.1-19
HRPabbreviationnewPHC p.7-8
HSCISabbreviationnewSC p.7
HTSSabbreviationnewSC p.7
ICD-11abbreviationnewPHC p.7-8; PC p.6
ICFabbreviationnewPHC p.7-8
ICHIabbreviationnewPHC p.7-8; PC p.6
ICTabbreviationnewSC p.7
ICVPabbreviationnewRA p.1-19
IDabbreviationnewPHC p.7-8; PC p.6
IDMPabbreviationnewPC p.6
IHEabbreviationnewPHC p.7-8
INNabbreviationnewPC p.6
InputglossarynewPHC p.9
IntegrationglossarynewRA p.1-19
InteroperabilityglossarynewPHC p.9; PHC p.56-60
interoperability layer (body, DHSC architecture)bodynewSC p.35
IPSabbreviationnewRA p.1-19
ITabbreviationnewPHC p.7-8; SC p.7
ITUabbreviationnewPHC p.7-8; SC p.7
JSONabbreviationnewPHC p.7-8
KPIabbreviationnewSC p.7
Legacy systemglossarynewPHC p.10
Lifelong Health Record (LHR)bodynewRA p.166-175
LMICabbreviationnewRA p.1-19
Logical Information Model Repository (LIMR)bodynewRA p.183-191
Logical Observation Identifiers Names and Codes (LOINC)glossarynewRA p.1-19
LOINCabbreviationnewPHC p.7-8; RA p.1-19
Longitudinal tracking [of a health service user]glossarynewPHC p.10
Mapping (country-to-reference)bodynewRA p.96-97
MAPSabbreviationnewPHC p.7-8
Minimum viable product (MVP)glossarynewPHC p.10
Mock-upglossarynewPHC p.10
MOHabbreviationnewSC p.7
MVPabbreviationnewPHC p.7-8
NAFDACabbreviationnewPC p.6
National digital architectbodynewRA p.104-105
National digital health architecture roadmapbodynewRA p.99-100
NGOabbreviationnewPC p.6
Non-functional requirementsglossaryoverlaps:docs/artifact/StructureDefinition-NonFunctionalRequirement.mdPHC p.10; SC p.8
NPCabbreviationnewSC p.7; PC p.6
NPC (national product catalogue tool) (body, ch. 03)bodynewPC p.35
NRAabbreviationnewPC p.6
NSCAabbreviationnewSC p.7
Open sourceglossarynewPHC p.10; SC p.8
Open standardsglossarynewPHC p.10; SC p.9
OpenHIEabbreviationnewPHC p.7-8; SC p.7
Operational governancebodynewRA p.67-68
order managementglossarynewSC p.9
order management systemglossarynewSC p.9
organogramglossarynewSC p.9; PC p.8
OutcomeglossarynewRA p.1-19; RA p.52-59
OutputglossarynewPHC p.10
Pain pointglossarynewPHC p.10
PCMTabbreviationnewPC p.7
PCPOSSabbreviationnewPHC p.7-8
Person-centredglossarynewPHC p.10
Person-centred point of service system (PCPOSS)glossarynewPHC p.10
PHCabbreviationnewPHC p.7-8
Point-of-service applicationsglossarynewRA p.1-19
Pop-up messageglossarynewPHC p.10
POSabbreviationnewPHC p.7-8
ProductglossarynewRA p.1-19; RA p.52-59
Product master data (body)bodynewPC p.10
Product RegistrybodynewRA p.156-166
PrototypeglossarynewPHC p.10
Public Health Surveillance Platform (PHSP)bodynewRA p.229-240
QAabbreviationnewSC p.7
Realises (relationship)bodynewRA p.52-59
REDDHIabbreviationnewRA p.1-19
Reference ArchitectureglossarynewRA p.1-19; RA p.19
Reference softwareglossarynewPHC p.10
RegisterglossarynewPHC p.11
RegistryglossarynewPHC p.11; SC p.9
Regulated Trade Item (body, ch. 02)bodynewPC p.28
Resilient Essential Data and Digital Health Infrastructure (REDDHI)bodynewRA p.38-39
RFPabbreviationnewSC p.7; PC p.7
RFQabbreviationnewSC p.7; PC p.7
RMSabbreviationnewPC p.7
RuleglossarynewPHC p.11
SBPabbreviationnewPHC p.7-8
SCISMMabbreviationnewSC p.7; PC p.7
SCSAabbreviationnewSC p.7
SDGabbreviationnewPHC p.7-8; RA p.1-19
Semantic Governance Infrastructure (SGI)bodynewRA p.68-73
Serves (relationship)bodynewRA p.52-59
SMARTabbreviationnewSC p.7; PC p.7
SMART GuidelinesglossarynewPHC p.11; SC p.9
SMART GuidelinesabbreviationnewRA p.1-19
SNOMED CTglossarynewRA p.1-19
SNOMED CTabbreviationnewRA p.1-19
SNOMED GPSglossarynewRA p.1-19
SNOMED-GPSabbreviationnewPHC p.7-8; RA p.1-19
Software platformglossarynewPHC p.11
Solution ArchitectureglossarynewRA p.1-19
SOPabbreviationnewPC p.7
stakeholderglossarynewSC p.9; RA p.1-19
Strategic governancebodynewRA p.65-67
Subsidiarity (governance principle)bodynewRA p.65
Supplier RegistrybodynewRA p.202-210
SWGabbreviationnewPC p.7
Systems architectureglossarynewPHC p.11; PHC p.56-60
Technical DebtglossarynewPHC p.11
Terminology ServicebodynewRA p.175-183
To-beglossarynewPHC p.11
TOGAFabbreviationnewSC p.7; RA p.1-19
TORabbreviationnewPC p.7
total cost of ownershipglossarynewSC p.9
traceabilityglossarynewSC p.9; SC p.54
traceability models (centralized, semi-centralized, distributed)bodynewSC p.54
Trade itemglossarynewPC p.9; PC p.28
TransactionbodynewRA p.90-94
Transactional data (body)bodynewPC p.10
Trigger eventglossarynewPHC p.11
Triggering (relationship)bodynewRA p.90-94
TSSabbreviationnewSC p.7; PC p.7
TWGabbreviationnewSC p.7
UATabbreviationnewPHC p.7-8; PC p.7
UIabbreviationnewPHC p.7-8
UMCabbreviationnewPC p.7
USAIDabbreviationnewSC p.7; PC p.7
USAID GHSC-PSMabbreviationnewPC p.7
Use caseglossarynewPHC p.11; SC p.9
User acceptance testingglossarynewPHC p.11; PC p.9
User personaglossaryoverlaps:docs/artifact/StructureDefinition-GenericPersona.mdPHC p.11; PHC p.33-35
User storyglossaryoverlaps:folio-assistant-core/glossary/cat-harness.glossary.jsonPHC p.11
ValueglossarynewRA p.1-19
warehouse management systemglossarynewSC p.9
WHOabbreviationnewPHC p.7-8; SC p.7
WHO-FICabbreviationnewPHC p.7-8
WHODrugabbreviationnewPC p.7
WireframesglossarynewPHC p.11
WMSabbreviationnewSC p.7; PC p.7
WorkflowglossarynewPHC p.11; PHC p.35-39
ZAMMSAabbreviationnewPC p.7
ZAMRAabbreviationnewPC p.7

folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev