SMART Base
0.3.0 - ci-build
SMART Base, published by WHO. This guide is not an authorized publication; it is the continuous build for version 0.3.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/litlfred/smart-base/ and changes regularly. See the Directory of published versions
| Active as of 2026-10-06 |
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="KGL1Classes"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><div xml:lang="en" lang="en"><hr/><p><b>English</b></p><hr/><p class="res-header-id"><b>Generated Narrative: CodeSystem KGL1Classes</b></p><a name="KGL1Classes"> </a><a name="hcKGL1Classes"> </a><p>This case-sensitive code system <code>http://smart.who.int/base/CodeSystem/KGL1Classes</code> defines the following codes:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style="white-space:nowrap">publication<a name="KGL1Classes-publication"> </a></td><td>Publication</td><td>A WHO normative publication: a guideline, guidance, recommendation summary, or classification. Metadata follows Dublin Core, which HealthInterventions already uses.</td></tr><tr><td style="white-space:nowrap">publication-section<a name="KGL1Classes-publication-section"> </a></td><td>Publication section</td><td>A chapter, annex or numbered section. Recommendations are located by section and page, which is what makes an extraction checkable.</td></tr><tr><td style="white-space:nowrap">recommendation<a name="KGL1Classes-recommendation"> </a></td><td>Recommendation</td><td>The atomic normative statement. This is the node nothing in the WHO estate currently makes addressable.</td></tr><tr><td style="white-space:nowrap">remark<a name="KGL1Classes-remark"> </a></td><td>Remark</td><td>An implementation consideration attached to a recommendation. Grounded: the BCG table's first annotationEntry carries exactly this — "Neonates born to women of unknown HIV status should be vaccinated as the benefits…" — clinical nuance that shapes the decision logic but is not the recommendation itself.</td></tr><tr><td style="white-space:nowrap">evidence<a name="KGL1Classes-evidence"> </a></td><td>Evidence</td><td>The body of evidence behind a recommendation, with its GRADE certainty rating.</td></tr><tr><td style="white-space:nowrap">population<a name="KGL1Classes-population"> </a></td><td>Population</td><td>PICO P.</td></tr><tr><td style="white-space:nowrap">intervention<a name="KGL1Classes-intervention"> </a></td><td>Intervention</td><td>PICO I. The clinical or public-health action, distinct from health-intervention, which is the DAK-facing component.</td></tr><tr><td style="white-space:nowrap">comparator<a name="KGL1Classes-comparator"> </a></td><td>Comparator</td><td>PICO C. Frequently absent in WHO recommendations; absence is recorded rather than invented.</td></tr><tr><td style="white-space:nowrap">outcome<a name="KGL1Classes-outcome"> </a></td><td>Outcome</td><td>PICO O.</td></tr><tr><td style="white-space:nowrap">health-intervention<a name="KGL1Classes-health-intervention"> </a></td><td>Health intervention</td><td>What a recommendation is about, and the hinge to L2. Corresponds to the DAK component smart-base defines as HealthInterventions — today `id`, `description[x]` and `reference 1..* DublinCore`, i.e. a bibliographic citation with no recommendation behind it. This class is what that citation should resolve to.</td></tr><tr><td style="white-space:nowrap">schedule<a name="KGL1Classes-schedule"> </a></td><td>Schedule</td><td>A normative delivery schedule. Grounded: the BCG table cites "WHO recommendations for routine immunization – summary tables", which IS a schedule publication — the single most-cited L1 source in the immunization DAK.</td></tr><tr><td style="white-space:nowrap">schedule-entry<a name="KGL1Classes-schedule-entry"> </a></td><td>Schedule entry</td><td>One row of a schedule: which intervention, for whom, when, how many doses. This is the granularity a decision table actually consumes — the BCG rules turn on dose count, age and interval since a live vaccine.</td></tr><tr><td style="white-space:nowrap">indicator<a name="KGL1Classes-indicator"> </a></td><td>Indicator</td><td>A programme indicator defined normatively at L1. Distinct from the DAK's ProgramIndicator component, which is its L2 expression; that model already carries `references 0..* id` pointing at health intervention ids.</td></tr><tr><td style="white-space:nowrap">terminology-code<a name="KGL1Classes-terminology-code"> </a></td><td>Terminology code</td><td>A code in an external terminology — ICD-10, ICD-11, SNOMED CT, ATC, or a WHO classification such as CDHI. CROSS-REFERENCE ONLY. It records system, code and display, and asserts NOTHING about the terminology: no hierarchy, no subsumption, no synonyms, no post-coordination. The terminology has its own authority, its own release cycle and its own tooling, and a partial copy here would be wrong within one release. Resolve meaning against the terminology server, not against this graph.</td></tr><tr><td style="white-space:nowrap">citation<a name="KGL1Classes-citation"> </a></td><td>Citation</td><td>A citation string exactly as it appears in an L2 or L3 artefact, together with what it was resolved to. Grounded directly in the BCG table, where every rule's annotationEntry[1] reads "WHO recommendations for routine immunization – summary tables (March 2023) (1)" — a citation that no tool can currently follow. This class is where that string becomes a link, and where the fact that resolving it was a judgement gets recorded.</td></tr><tr><td style="white-space:nowrap">external-artifact<a name="KGL1Classes-external-artifact"> </a></td><td>External artefact</td><td>An L2 or L3 artefact addressed by canonical URL — a BPMN process, a DMN decision table, a FHIR PlanDefinition. Deliberately opaque: it carries an IRI and a free-text kind, and this graph asserts nothing about its internal structure. That opacity is the boundary. The L2 and L3 subgraphs model those artefacts properly; L1 only needs to point.</td></tr></table></div><div xml:lang="fr" lang="fr"><hr/><p><b>French</b></p><hr/><p class="res-header-id"><b>Narratif généré : CodeSystem KGL1Classes</b></p><a name="fr-KGL1Classes"> </a><a name="fr-hcKGL1Classes"> </a><p>This case-sensitive code system <code>http://smart.who.int/base/CodeSystem/KGL1Classes</code> defines the following codes:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Affichage</b></td><td><b>Définition</b></td></tr><tr><td style="white-space:nowrap">publication<a name="fr-KGL1Classes-publication"> </a></td><td>Publication</td><td>A WHO normative publication: a guideline, guidance, recommendation summary, or classification. Metadata follows Dublin Core, which HealthInterventions already uses.</td></tr><tr><td style="white-space:nowrap">publication-section<a name="fr-KGL1Classes-publication-section"> </a></td><td>Publication section</td><td>A chapter, annex or numbered section. Recommendations are located by section and page, which is what makes an extraction checkable.</td></tr><tr><td style="white-space:nowrap">recommendation<a name="fr-KGL1Classes-recommendation"> </a></td><td>Recommendation</td><td>The atomic normative statement. This is the node nothing in the WHO estate currently makes addressable.</td></tr><tr><td style="white-space:nowrap">remark<a name="fr-KGL1Classes-remark"> </a></td><td>Remark</td><td>An implementation consideration attached to a recommendation. Grounded: the BCG table's first annotationEntry carries exactly this — "Neonates born to women of unknown HIV status should be vaccinated as the benefits…" — clinical nuance that shapes the decision logic but is not the recommendation itself.</td></tr><tr><td style="white-space:nowrap">evidence<a name="fr-KGL1Classes-evidence"> </a></td><td>Evidence</td><td>The body of evidence behind a recommendation, with its GRADE certainty rating.</td></tr><tr><td style="white-space:nowrap">population<a name="fr-KGL1Classes-population"> </a></td><td>Population</td><td>PICO P.</td></tr><tr><td style="white-space:nowrap">intervention<a name="fr-KGL1Classes-intervention"> </a></td><td>Intervention</td><td>PICO I. The clinical or public-health action, distinct from health-intervention, which is the DAK-facing component.</td></tr><tr><td style="white-space:nowrap">comparator<a name="fr-KGL1Classes-comparator"> </a></td><td>Comparator</td><td>PICO C. Frequently absent in WHO recommendations; absence is recorded rather than invented.</td></tr><tr><td style="white-space:nowrap">outcome<a name="fr-KGL1Classes-outcome"> </a></td><td>Outcome</td><td>PICO O.</td></tr><tr><td style="white-space:nowrap">health-intervention<a name="fr-KGL1Classes-health-intervention"> </a></td><td>Health intervention</td><td>What a recommendation is about, and the hinge to L2. Corresponds to the DAK component smart-base defines as HealthInterventions — today `id`, `description[x]` and `reference 1..* DublinCore`, i.e. a bibliographic citation with no recommendation behind it. This class is what that citation should resolve to.</td></tr><tr><td style="white-space:nowrap">schedule<a name="fr-KGL1Classes-schedule"> </a></td><td>Schedule</td><td>A normative delivery schedule. Grounded: the BCG table cites "WHO recommendations for routine immunization – summary tables", which IS a schedule publication — the single most-cited L1 source in the immunization DAK.</td></tr><tr><td style="white-space:nowrap">schedule-entry<a name="fr-KGL1Classes-schedule-entry"> </a></td><td>Schedule entry</td><td>One row of a schedule: which intervention, for whom, when, how many doses. This is the granularity a decision table actually consumes — the BCG rules turn on dose count, age and interval since a live vaccine.</td></tr><tr><td style="white-space:nowrap">indicator<a name="fr-KGL1Classes-indicator"> </a></td><td>Indicator</td><td>A programme indicator defined normatively at L1. Distinct from the DAK's ProgramIndicator component, which is its L2 expression; that model already carries `references 0..* id` pointing at health intervention ids.</td></tr><tr><td style="white-space:nowrap">terminology-code<a name="fr-KGL1Classes-terminology-code"> </a></td><td>Terminology code</td><td>A code in an external terminology — ICD-10, ICD-11, SNOMED CT, ATC, or a WHO classification such as CDHI. CROSS-REFERENCE ONLY. It records system, code and display, and asserts NOTHING about the terminology: no hierarchy, no subsumption, no synonyms, no post-coordination. The terminology has its own authority, its own release cycle and its own tooling, and a partial copy here would be wrong within one release. Resolve meaning against the terminology server, not against this graph.</td></tr><tr><td style="white-space:nowrap">citation<a name="fr-KGL1Classes-citation"> </a></td><td>Citation</td><td>A citation string exactly as it appears in an L2 or L3 artefact, together with what it was resolved to. Grounded directly in the BCG table, where every rule's annotationEntry[1] reads "WHO recommendations for routine immunization – summary tables (March 2023) (1)" — a citation that no tool can currently follow. This class is where that string becomes a link, and where the fact that resolving it was a judgement gets recorded.</td></tr><tr><td style="white-space:nowrap">external-artifact<a name="fr-KGL1Classes-external-artifact"> </a></td><td>External artefact</td><td>An L2 or L3 artefact addressed by canonical URL — a BPMN process, a DMN decision table, a FHIR PlanDefinition. Deliberately opaque: it carries an IRI and a free-text kind, and this graph asserts nothing about its internal structure. That opacity is the boundary. The L2 and L3 subgraphs model those artefacts properly; L1 only needs to point.</td></tr></table></div><div xml:lang="ar" lang="ar"><hr/><p><b>Arabic</b></p><hr/><p class="res-header-id"><b>السرد المُنشأ: CodeSystem KGL1Classes</b></p><a name="ar-KGL1Classes"> </a><a name="ar-hcKGL1Classes"> </a><p>يُعرّف هذا case-sensitive نظام الشيفرة <code>http://smart.who.int/base/CodeSystem/KGL1Classes</code> الرمز التالي<f test="code-count != 1">s</f>:</p><table class="codes"><tr><td style="white-space:nowrap"><b>الكود</b></td><td><b>العرض</b></td><td><b>التعريف</b></td></tr><tr><td style="white-space:nowrap">publication<a name="ar-KGL1Classes-publication"> </a></td><td>Publication</td><td>A WHO normative publication: a guideline, guidance, recommendation summary, or classification. Metadata follows Dublin Core, which HealthInterventions already uses.</td></tr><tr><td style="white-space:nowrap">publication-section<a name="ar-KGL1Classes-publication-section"> </a></td><td>Publication section</td><td>A chapter, annex or numbered section. Recommendations are located by section and page, which is what makes an extraction checkable.</td></tr><tr><td style="white-space:nowrap">recommendation<a name="ar-KGL1Classes-recommendation"> </a></td><td>Recommendation</td><td>The atomic normative statement. This is the node nothing in the WHO estate currently makes addressable.</td></tr><tr><td style="white-space:nowrap">remark<a name="ar-KGL1Classes-remark"> </a></td><td>Remark</td><td>An implementation consideration attached to a recommendation. Grounded: the BCG table's first annotationEntry carries exactly this — "Neonates born to women of unknown HIV status should be vaccinated as the benefits…" — clinical nuance that shapes the decision logic but is not the recommendation itself.</td></tr><tr><td style="white-space:nowrap">evidence<a name="ar-KGL1Classes-evidence"> </a></td><td>Evidence</td><td>The body of evidence behind a recommendation, with its GRADE certainty rating.</td></tr><tr><td style="white-space:nowrap">population<a name="ar-KGL1Classes-population"> </a></td><td>Population</td><td>PICO P.</td></tr><tr><td style="white-space:nowrap">intervention<a name="ar-KGL1Classes-intervention"> </a></td><td>Intervention</td><td>PICO I. The clinical or public-health action, distinct from health-intervention, which is the DAK-facing component.</td></tr><tr><td style="white-space:nowrap">comparator<a name="ar-KGL1Classes-comparator"> </a></td><td>Comparator</td><td>PICO C. Frequently absent in WHO recommendations; absence is recorded rather than invented.</td></tr><tr><td style="white-space:nowrap">outcome<a name="ar-KGL1Classes-outcome"> </a></td><td>Outcome</td><td>PICO O.</td></tr><tr><td style="white-space:nowrap">health-intervention<a name="ar-KGL1Classes-health-intervention"> </a></td><td>Health intervention</td><td>What a recommendation is about, and the hinge to L2. Corresponds to the DAK component smart-base defines as HealthInterventions — today `id`, `description[x]` and `reference 1..* DublinCore`, i.e. a bibliographic citation with no recommendation behind it. This class is what that citation should resolve to.</td></tr><tr><td style="white-space:nowrap">schedule<a name="ar-KGL1Classes-schedule"> </a></td><td>Schedule</td><td>A normative delivery schedule. Grounded: the BCG table cites "WHO recommendations for routine immunization – summary tables", which IS a schedule publication — the single most-cited L1 source in the immunization DAK.</td></tr><tr><td style="white-space:nowrap">schedule-entry<a name="ar-KGL1Classes-schedule-entry"> </a></td><td>Schedule entry</td><td>One row of a schedule: which intervention, for whom, when, how many doses. This is the granularity a decision table actually consumes — the BCG rules turn on dose count, age and interval since a live vaccine.</td></tr><tr><td style="white-space:nowrap">indicator<a name="ar-KGL1Classes-indicator"> </a></td><td>Indicator</td><td>A programme indicator defined normatively at L1. Distinct from the DAK's ProgramIndicator component, which is its L2 expression; that model already carries `references 0..* id` pointing at health intervention ids.</td></tr><tr><td style="white-space:nowrap">terminology-code<a name="ar-KGL1Classes-terminology-code"> </a></td><td>Terminology code</td><td>A code in an external terminology — ICD-10, ICD-11, SNOMED CT, ATC, or a WHO classification such as CDHI. CROSS-REFERENCE ONLY. It records system, code and display, and asserts NOTHING about the terminology: no hierarchy, no subsumption, no synonyms, no post-coordination. The terminology has its own authority, its own release cycle and its own tooling, and a partial copy here would be wrong within one release. Resolve meaning against the terminology server, not against this graph.</td></tr><tr><td style="white-space:nowrap">citation<a name="ar-KGL1Classes-citation"> </a></td><td>Citation</td><td>A citation string exactly as it appears in an L2 or L3 artefact, together with what it was resolved to. Grounded directly in the BCG table, where every rule's annotationEntry[1] reads "WHO recommendations for routine immunization – summary tables (March 2023) (1)" — a citation that no tool can currently follow. This class is where that string becomes a link, and where the fact that resolving it was a judgement gets recorded.</td></tr><tr><td style="white-space:nowrap">external-artifact<a name="ar-KGL1Classes-external-artifact"> </a></td><td>External artefact</td><td>An L2 or L3 artefact addressed by canonical URL — a BPMN process, a DMN decision table, a FHIR PlanDefinition. Deliberately opaque: it carries an IRI and a free-text kind, and this graph asserts nothing about its internal structure. That opacity is the boundary. The L2 and L3 subgraphs model those artefacts properly; L1 only needs to point.</td></tr></table></div><div xml:lang="zh" lang="zh"><hr/><p><b>Chinese</b></p><hr/><p class="res-header-id"><b>Generated Narrative: 代码系统 KGL1Classes</b></p><a name="zh-KGL1Classes"> </a><a name="zh-hcKGL1Classes"> </a><p>This case-sensitive code system <code>http://smart.who.int/base/CodeSystem/KGL1Classes</code> defines the following codes:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style="white-space:nowrap">publication<a name="zh-KGL1Classes-publication"> </a></td><td>Publication</td><td>A WHO normative publication: a guideline, guidance, recommendation summary, or classification. Metadata follows Dublin Core, which HealthInterventions already uses.</td></tr><tr><td style="white-space:nowrap">publication-section<a name="zh-KGL1Classes-publication-section"> </a></td><td>Publication section</td><td>A chapter, annex or numbered section. Recommendations are located by section and page, which is what makes an extraction checkable.</td></tr><tr><td style="white-space:nowrap">recommendation<a name="zh-KGL1Classes-recommendation"> </a></td><td>Recommendation</td><td>The atomic normative statement. This is the node nothing in the WHO estate currently makes addressable.</td></tr><tr><td style="white-space:nowrap">remark<a name="zh-KGL1Classes-remark"> </a></td><td>Remark</td><td>An implementation consideration attached to a recommendation. Grounded: the BCG table's first annotationEntry carries exactly this — "Neonates born to women of unknown HIV status should be vaccinated as the benefits…" — clinical nuance that shapes the decision logic but is not the recommendation itself.</td></tr><tr><td style="white-space:nowrap">evidence<a name="zh-KGL1Classes-evidence"> </a></td><td>Evidence</td><td>The body of evidence behind a recommendation, with its GRADE certainty rating.</td></tr><tr><td style="white-space:nowrap">population<a name="zh-KGL1Classes-population"> </a></td><td>Population</td><td>PICO P.</td></tr><tr><td style="white-space:nowrap">intervention<a name="zh-KGL1Classes-intervention"> </a></td><td>Intervention</td><td>PICO I. The clinical or public-health action, distinct from health-intervention, which is the DAK-facing component.</td></tr><tr><td style="white-space:nowrap">comparator<a name="zh-KGL1Classes-comparator"> </a></td><td>Comparator</td><td>PICO C. Frequently absent in WHO recommendations; absence is recorded rather than invented.</td></tr><tr><td style="white-space:nowrap">outcome<a name="zh-KGL1Classes-outcome"> </a></td><td>Outcome</td><td>PICO O.</td></tr><tr><td style="white-space:nowrap">health-intervention<a name="zh-KGL1Classes-health-intervention"> </a></td><td>Health intervention</td><td>What a recommendation is about, and the hinge to L2. Corresponds to the DAK component smart-base defines as HealthInterventions — today `id`, `description[x]` and `reference 1..* DublinCore`, i.e. a bibliographic citation with no recommendation behind it. This class is what that citation should resolve to.</td></tr><tr><td style="white-space:nowrap">schedule<a name="zh-KGL1Classes-schedule"> </a></td><td>Schedule</td><td>A normative delivery schedule. Grounded: the BCG table cites "WHO recommendations for routine immunization – summary tables", which IS a schedule publication — the single most-cited L1 source in the immunization DAK.</td></tr><tr><td style="white-space:nowrap">schedule-entry<a name="zh-KGL1Classes-schedule-entry"> </a></td><td>Schedule entry</td><td>One row of a schedule: which intervention, for whom, when, how many doses. This is the granularity a decision table actually consumes — the BCG rules turn on dose count, age and interval since a live vaccine.</td></tr><tr><td style="white-space:nowrap">indicator<a name="zh-KGL1Classes-indicator"> </a></td><td>Indicator</td><td>A programme indicator defined normatively at L1. Distinct from the DAK's ProgramIndicator component, which is its L2 expression; that model already carries `references 0..* id` pointing at health intervention ids.</td></tr><tr><td style="white-space:nowrap">terminology-code<a name="zh-KGL1Classes-terminology-code"> </a></td><td>Terminology code</td><td>A code in an external terminology — ICD-10, ICD-11, SNOMED CT, ATC, or a WHO classification such as CDHI. CROSS-REFERENCE ONLY. It records system, code and display, and asserts NOTHING about the terminology: no hierarchy, no subsumption, no synonyms, no post-coordination. The terminology has its own authority, its own release cycle and its own tooling, and a partial copy here would be wrong within one release. Resolve meaning against the terminology server, not against this graph.</td></tr><tr><td style="white-space:nowrap">citation<a name="zh-KGL1Classes-citation"> </a></td><td>Citation</td><td>A citation string exactly as it appears in an L2 or L3 artefact, together with what it was resolved to. Grounded directly in the BCG table, where every rule's annotationEntry[1] reads "WHO recommendations for routine immunization – summary tables (March 2023) (1)" — a citation that no tool can currently follow. This class is where that string becomes a link, and where the fact that resolving it was a judgement gets recorded.</td></tr><tr><td style="white-space:nowrap">external-artifact<a name="zh-KGL1Classes-external-artifact"> </a></td><td>External artefact</td><td>An L2 or L3 artefact addressed by canonical URL — a BPMN process, a DMN decision table, a FHIR PlanDefinition. Deliberately opaque: it carries an IRI and a free-text kind, and this graph asserts nothing about its internal structure. That opacity is the boundary. The L2 and L3 subgraphs model those artefacts properly; L1 only needs to point.</td></tr></table></div><div xml:lang="ru" lang="ru"><hr/><p><b>Russian</b></p><hr/><p class="res-header-id"><b>Сгенерированный нарратив: CodeSystem KGL1Classes</b></p><a name="ru-KGL1Classes"> </a><a name="ru-hcKGL1Classes"> </a><p>Данная система кодов <code>http://smart.who.int/base/CodeSystem/KGL1Classes</code> case-sensitive определяет следующие коды:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Код</b></td><td><b>Отображение</b></td><td><b>Определение</b></td></tr><tr><td style="white-space:nowrap">publication<a name="ru-KGL1Classes-publication"> </a></td><td>Publication</td><td>A WHO normative publication: a guideline, guidance, recommendation summary, or classification. Metadata follows Dublin Core, which HealthInterventions already uses.</td></tr><tr><td style="white-space:nowrap">publication-section<a name="ru-KGL1Classes-publication-section"> </a></td><td>Publication section</td><td>A chapter, annex or numbered section. Recommendations are located by section and page, which is what makes an extraction checkable.</td></tr><tr><td style="white-space:nowrap">recommendation<a name="ru-KGL1Classes-recommendation"> </a></td><td>Recommendation</td><td>The atomic normative statement. This is the node nothing in the WHO estate currently makes addressable.</td></tr><tr><td style="white-space:nowrap">remark<a name="ru-KGL1Classes-remark"> </a></td><td>Remark</td><td>An implementation consideration attached to a recommendation. Grounded: the BCG table's first annotationEntry carries exactly this — "Neonates born to women of unknown HIV status should be vaccinated as the benefits…" — clinical nuance that shapes the decision logic but is not the recommendation itself.</td></tr><tr><td style="white-space:nowrap">evidence<a name="ru-KGL1Classes-evidence"> </a></td><td>Evidence</td><td>The body of evidence behind a recommendation, with its GRADE certainty rating.</td></tr><tr><td style="white-space:nowrap">population<a name="ru-KGL1Classes-population"> </a></td><td>Population</td><td>PICO P.</td></tr><tr><td style="white-space:nowrap">intervention<a name="ru-KGL1Classes-intervention"> </a></td><td>Intervention</td><td>PICO I. The clinical or public-health action, distinct from health-intervention, which is the DAK-facing component.</td></tr><tr><td style="white-space:nowrap">comparator<a name="ru-KGL1Classes-comparator"> </a></td><td>Comparator</td><td>PICO C. Frequently absent in WHO recommendations; absence is recorded rather than invented.</td></tr><tr><td style="white-space:nowrap">outcome<a name="ru-KGL1Classes-outcome"> </a></td><td>Outcome</td><td>PICO O.</td></tr><tr><td style="white-space:nowrap">health-intervention<a name="ru-KGL1Classes-health-intervention"> </a></td><td>Health intervention</td><td>What a recommendation is about, and the hinge to L2. Corresponds to the DAK component smart-base defines as HealthInterventions — today `id`, `description[x]` and `reference 1..* DublinCore`, i.e. a bibliographic citation with no recommendation behind it. This class is what that citation should resolve to.</td></tr><tr><td style="white-space:nowrap">schedule<a name="ru-KGL1Classes-schedule"> </a></td><td>Schedule</td><td>A normative delivery schedule. Grounded: the BCG table cites "WHO recommendations for routine immunization – summary tables", which IS a schedule publication — the single most-cited L1 source in the immunization DAK.</td></tr><tr><td style="white-space:nowrap">schedule-entry<a name="ru-KGL1Classes-schedule-entry"> </a></td><td>Schedule entry</td><td>One row of a schedule: which intervention, for whom, when, how many doses. This is the granularity a decision table actually consumes — the BCG rules turn on dose count, age and interval since a live vaccine.</td></tr><tr><td style="white-space:nowrap">indicator<a name="ru-KGL1Classes-indicator"> </a></td><td>Indicator</td><td>A programme indicator defined normatively at L1. Distinct from the DAK's ProgramIndicator component, which is its L2 expression; that model already carries `references 0..* id` pointing at health intervention ids.</td></tr><tr><td style="white-space:nowrap">terminology-code<a name="ru-KGL1Classes-terminology-code"> </a></td><td>Terminology code</td><td>A code in an external terminology — ICD-10, ICD-11, SNOMED CT, ATC, or a WHO classification such as CDHI. CROSS-REFERENCE ONLY. It records system, code and display, and asserts NOTHING about the terminology: no hierarchy, no subsumption, no synonyms, no post-coordination. The terminology has its own authority, its own release cycle and its own tooling, and a partial copy here would be wrong within one release. Resolve meaning against the terminology server, not against this graph.</td></tr><tr><td style="white-space:nowrap">citation<a name="ru-KGL1Classes-citation"> </a></td><td>Citation</td><td>A citation string exactly as it appears in an L2 or L3 artefact, together with what it was resolved to. Grounded directly in the BCG table, where every rule's annotationEntry[1] reads "WHO recommendations for routine immunization – summary tables (March 2023) (1)" — a citation that no tool can currently follow. This class is where that string becomes a link, and where the fact that resolving it was a judgement gets recorded.</td></tr><tr><td style="white-space:nowrap">external-artifact<a name="ru-KGL1Classes-external-artifact"> </a></td><td>External artefact</td><td>An L2 or L3 artefact addressed by canonical URL — a BPMN process, a DMN decision table, a FHIR PlanDefinition. Deliberately opaque: it carries an IRI and a free-text kind, and this graph asserts nothing about its internal structure. That opacity is the boundary. The L2 and L3 subgraphs model those artefacts properly; L1 only needs to point.</td></tr></table></div><div xml:lang="es" lang="es"><hr/><p><b>Spanish</b></p><hr/><p class="res-header-id"><b>Generated Narrative: SistemaDeCodigos KGL1Classes</b></p><a name="es-KGL1Classes"> </a><a name="es-hcKGL1Classes"> </a><p>This case-sensitive code system <code>http://smart.who.int/base/CodeSystem/KGL1Classes</code> defines the following codes:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style="white-space:nowrap">publication<a name="es-KGL1Classes-publication"> </a></td><td>Publication</td><td>A WHO normative publication: a guideline, guidance, recommendation summary, or classification. Metadata follows Dublin Core, which HealthInterventions already uses.</td></tr><tr><td style="white-space:nowrap">publication-section<a name="es-KGL1Classes-publication-section"> </a></td><td>Publication section</td><td>A chapter, annex or numbered section. Recommendations are located by section and page, which is what makes an extraction checkable.</td></tr><tr><td style="white-space:nowrap">recommendation<a name="es-KGL1Classes-recommendation"> </a></td><td>Recommendation</td><td>The atomic normative statement. This is the node nothing in the WHO estate currently makes addressable.</td></tr><tr><td style="white-space:nowrap">remark<a name="es-KGL1Classes-remark"> </a></td><td>Remark</td><td>An implementation consideration attached to a recommendation. Grounded: the BCG table's first annotationEntry carries exactly this — "Neonates born to women of unknown HIV status should be vaccinated as the benefits…" — clinical nuance that shapes the decision logic but is not the recommendation itself.</td></tr><tr><td style="white-space:nowrap">evidence<a name="es-KGL1Classes-evidence"> </a></td><td>Evidence</td><td>The body of evidence behind a recommendation, with its GRADE certainty rating.</td></tr><tr><td style="white-space:nowrap">population<a name="es-KGL1Classes-population"> </a></td><td>Population</td><td>PICO P.</td></tr><tr><td style="white-space:nowrap">intervention<a name="es-KGL1Classes-intervention"> </a></td><td>Intervention</td><td>PICO I. The clinical or public-health action, distinct from health-intervention, which is the DAK-facing component.</td></tr><tr><td style="white-space:nowrap">comparator<a name="es-KGL1Classes-comparator"> </a></td><td>Comparator</td><td>PICO C. Frequently absent in WHO recommendations; absence is recorded rather than invented.</td></tr><tr><td style="white-space:nowrap">outcome<a name="es-KGL1Classes-outcome"> </a></td><td>Outcome</td><td>PICO O.</td></tr><tr><td style="white-space:nowrap">health-intervention<a name="es-KGL1Classes-health-intervention"> </a></td><td>Health intervention</td><td>What a recommendation is about, and the hinge to L2. Corresponds to the DAK component smart-base defines as HealthInterventions — today `id`, `description[x]` and `reference 1..* DublinCore`, i.e. a bibliographic citation with no recommendation behind it. This class is what that citation should resolve to.</td></tr><tr><td style="white-space:nowrap">schedule<a name="es-KGL1Classes-schedule"> </a></td><td>Schedule</td><td>A normative delivery schedule. Grounded: the BCG table cites "WHO recommendations for routine immunization – summary tables", which IS a schedule publication — the single most-cited L1 source in the immunization DAK.</td></tr><tr><td style="white-space:nowrap">schedule-entry<a name="es-KGL1Classes-schedule-entry"> </a></td><td>Schedule entry</td><td>One row of a schedule: which intervention, for whom, when, how many doses. This is the granularity a decision table actually consumes — the BCG rules turn on dose count, age and interval since a live vaccine.</td></tr><tr><td style="white-space:nowrap">indicator<a name="es-KGL1Classes-indicator"> </a></td><td>Indicator</td><td>A programme indicator defined normatively at L1. Distinct from the DAK's ProgramIndicator component, which is its L2 expression; that model already carries `references 0..* id` pointing at health intervention ids.</td></tr><tr><td style="white-space:nowrap">terminology-code<a name="es-KGL1Classes-terminology-code"> </a></td><td>Terminology code</td><td>A code in an external terminology — ICD-10, ICD-11, SNOMED CT, ATC, or a WHO classification such as CDHI. CROSS-REFERENCE ONLY. It records system, code and display, and asserts NOTHING about the terminology: no hierarchy, no subsumption, no synonyms, no post-coordination. The terminology has its own authority, its own release cycle and its own tooling, and a partial copy here would be wrong within one release. Resolve meaning against the terminology server, not against this graph.</td></tr><tr><td style="white-space:nowrap">citation<a name="es-KGL1Classes-citation"> </a></td><td>Citation</td><td>A citation string exactly as it appears in an L2 or L3 artefact, together with what it was resolved to. Grounded directly in the BCG table, where every rule's annotationEntry[1] reads "WHO recommendations for routine immunization – summary tables (March 2023) (1)" — a citation that no tool can currently follow. This class is where that string becomes a link, and where the fact that resolving it was a judgement gets recorded.</td></tr><tr><td style="white-space:nowrap">external-artifact<a name="es-KGL1Classes-external-artifact"> </a></td><td>External artefact</td><td>An L2 or L3 artefact addressed by canonical URL — a BPMN process, a DMN decision table, a FHIR PlanDefinition. Deliberately opaque: it carries an IRI and a free-text kind, and this graph asserts nothing about its internal structure. That opacity is the boundary. The L2 and L3 subgraphs model those artefacts properly; L1 only needs to point.</td></tr></table></div></div>
</text>
<url value="http://smart.who.int/base/CodeSystem/KGL1Classes"/>
<version value="0.3.0"/>
<name value="KGL1Classes"/>
<title value="Knowledge graph L1: classes"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-10-06T14:15:03+00:00"/>
<publisher value="WHO"/>
<contact>
<name value="WHO"/>
<telecom>
<system value="url"/>
<value value="http://who.int"/>
</telecom>
</contact>
<description
value="The classes of the L1 layer of the SMART Guidelines knowledge graph. A node's `type` is one of these. Source: kg/src/L1.ts (migrated from smart-kg ontology/L1/L1.json)."/>
<caseSensitive value="true"/>
<content value="complete"/>
<count value="16"/>
<concept>
<code value="publication"/>
<display value="Publication"/>
<definition
value="A WHO normative publication: a guideline, guidance, recommendation summary, or classification. Metadata follows Dublin Core, which HealthInterventions already uses."/>
</concept>
<concept>
<code value="publication-section"/>
<display value="Publication section"/>
<definition
value="A chapter, annex or numbered section. Recommendations are located by section and page, which is what makes an extraction checkable."/>
</concept>
<concept>
<code value="recommendation"/>
<display value="Recommendation"/>
<definition
value="The atomic normative statement. This is the node nothing in the WHO estate currently makes addressable."/>
</concept>
<concept>
<code value="remark"/>
<display value="Remark"/>
<definition
value="An implementation consideration attached to a recommendation. Grounded: the BCG table's first annotationEntry carries exactly this — "Neonates born to women of unknown HIV status should be vaccinated as the benefits…" — clinical nuance that shapes the decision logic but is not the recommendation itself."/>
</concept>
<concept>
<code value="evidence"/>
<display value="Evidence"/>
<definition
value="The body of evidence behind a recommendation, with its GRADE certainty rating."/>
</concept>
<concept>
<code value="population"/>
<display value="Population"/>
<definition value="PICO P."/>
</concept>
<concept>
<code value="intervention"/>
<display value="Intervention"/>
<definition
value="PICO I. The clinical or public-health action, distinct from health-intervention, which is the DAK-facing component."/>
</concept>
<concept>
<code value="comparator"/>
<display value="Comparator"/>
<definition
value="PICO C. Frequently absent in WHO recommendations; absence is recorded rather than invented."/>
</concept>
<concept>
<code value="outcome"/>
<display value="Outcome"/>
<definition value="PICO O."/>
</concept>
<concept>
<code value="health-intervention"/>
<display value="Health intervention"/>
<definition
value="What a recommendation is about, and the hinge to L2. Corresponds to the DAK component smart-base defines as HealthInterventions — today `id`, `description[x]` and `reference 1..* DublinCore`, i.e. a bibliographic citation with no recommendation behind it. This class is what that citation should resolve to."/>
</concept>
<concept>
<code value="schedule"/>
<display value="Schedule"/>
<definition
value="A normative delivery schedule. Grounded: the BCG table cites "WHO recommendations for routine immunization – summary tables", which IS a schedule publication — the single most-cited L1 source in the immunization DAK."/>
</concept>
<concept>
<code value="schedule-entry"/>
<display value="Schedule entry"/>
<definition
value="One row of a schedule: which intervention, for whom, when, how many doses. This is the granularity a decision table actually consumes — the BCG rules turn on dose count, age and interval since a live vaccine."/>
</concept>
<concept>
<code value="indicator"/>
<display value="Indicator"/>
<definition
value="A programme indicator defined normatively at L1. Distinct from the DAK's ProgramIndicator component, which is its L2 expression; that model already carries `references 0..* id` pointing at health intervention ids."/>
</concept>
<concept>
<code value="terminology-code"/>
<display value="Terminology code"/>
<definition
value="A code in an external terminology — ICD-10, ICD-11, SNOMED CT, ATC, or a WHO classification such as CDHI. CROSS-REFERENCE ONLY. It records system, code and display, and asserts NOTHING about the terminology: no hierarchy, no subsumption, no synonyms, no post-coordination. The terminology has its own authority, its own release cycle and its own tooling, and a partial copy here would be wrong within one release. Resolve meaning against the terminology server, not against this graph."/>
</concept>
<concept>
<code value="citation"/>
<display value="Citation"/>
<definition
value="A citation string exactly as it appears in an L2 or L3 artefact, together with what it was resolved to. Grounded directly in the BCG table, where every rule's annotationEntry[1] reads "WHO recommendations for routine immunization – summary tables (March 2023) (1)" — a citation that no tool can currently follow. This class is where that string becomes a link, and where the fact that resolving it was a judgement gets recorded."/>
</concept>
<concept>
<code value="external-artifact"/>
<display value="External artefact"/>
<definition
value="An L2 or L3 artefact addressed by canonical URL — a BPMN process, a DMN decision table, a FHIR PlanDefinition. Deliberately opaque: it carries an IRI and a free-text kind, and this graph asserts nothing about its internal structure. That opacity is the boundary. The L2 and L3 subgraphs model those artefacts properly; L1 only needs to point."/>
</concept>
</CodeSystem>