SMART Base
0.2.0 - ci-build

SMART Base, published by WHO. This guide is not an authorized publication; it is the continuous build for version 0.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/WorldHealthOrganization/smart-base/ and changes regularly. See the Directory of published versions

Logical Model: CoreDataElement - Detailed Descriptions

Active as of 2025-10-14

Definitions for the CoreDataElement logical model.

Guidance on how to interpret the contents of this table can be foundhere

0. CoreDataElement
Definition

Logical Model for representing Core Data Elements from a DAK. A core data element can be one of: a ValueSet, a CodeSystem, a ConceptMap, or a Logical Model adherent to SGLogicalModel. This is the ONE EXCEPTION to allowing FHIR R4 models into the DAK LMs.

ShortCore Data Element (DAK)
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. CoreDataElement.type
Definition

Type of core data element: valueset, codesystem, conceptmap, or logicalmodel

ShortType
Control1..1
BindingThe codes SHALL be taken from Core Data Element Type Value Set
(required to http://smart.who.int/base/ValueSet/CoreDataElementTypeVS)
Typecode
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
4. CoreDataElement.canonical
Definition

Canonical URI/IRI pointing to the ValueSet, CodeSystem, ConceptMap, or Logical Model definition

ShortCanonical
Control1..1
Typeuri
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. CoreDataElement.id
Definition

Identifier for the core data element

ShortElement ID
Control0..1
Typeid
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. CoreDataElement.description[x]
Definition

Description of the core data element - either Markdown content or a URI to a Markdown file (absolute or relative to repository root)

ShortDescription
Control0..1
TypeChoice of: string, uri
[x] NoteSeeChoice of Data Typesfor further information about how to use [x]
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension

Guidance on how to interpret the contents of this table can be foundhere

0. CoreDataElement
Definition

Logical Model for representing Core Data Elements from a DAK. A core data element can be one of: a ValueSet, a CodeSystem, a ConceptMap, or a Logical Model adherent to SGLogicalModel. This is the ONE EXCEPTION to allowing FHIR R4 models into the DAK LMs.

ShortCore Data Element (DAK)
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. CoreDataElement.type
Definition

Type of core data element: valueset, codesystem, conceptmap, or logicalmodel

ShortType
Control1..1
BindingThe codes SHALL be taken from Core Data Element Type Value Set
(required to http://smart.who.int/base/ValueSet/CoreDataElementTypeVS)
Typecode
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
4. CoreDataElement.canonical
Definition

Canonical URI/IRI pointing to the ValueSet, CodeSystem, ConceptMap, or Logical Model definition

ShortCanonical
Control1..1
Typeuri
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. CoreDataElement.id
Definition

Identifier for the core data element

ShortElement ID
Control0..1
Typeid
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. CoreDataElement.description[x]
Definition

Description of the core data element - either Markdown content or a URI to a Markdown file (absolute or relative to repository root)

ShortDescription
Control0..1
TypeChoice of: string, uri
[x] NoteSeeChoice of Data Typesfor further information about how to use [x]
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension

Guidance on how to interpret the contents of this table can be foundhere

0. CoreDataElement
Definition

Logical Model for representing Core Data Elements from a DAK. A core data element can be one of: a ValueSet, a CodeSystem, a ConceptMap, or a Logical Model adherent to SGLogicalModel. This is the ONE EXCEPTION to allowing FHIR R4 models into the DAK LMs.

ShortCore Data Element (DAK)
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. CoreDataElement.type
Definition

Type of core data element: valueset, codesystem, conceptmap, or logicalmodel

ShortType
Control1..1
BindingThe codes SHALL be taken from Core Data Element Type Value Set
(required to http://smart.who.int/base/ValueSet/CoreDataElementTypeVS)
Typecode
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
4. CoreDataElement.canonical
Definition

Canonical URI/IRI pointing to the ValueSet, CodeSystem, ConceptMap, or Logical Model definition

ShortCanonical
Control1..1
Typeuri
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. CoreDataElement.id
Definition

Identifier for the core data element

ShortElement ID
Control0..1
Typeid
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. CoreDataElement.description[x]
Definition

Description of the core data element - either Markdown content or a URI to a Markdown file (absolute or relative to repository root)

ShortDescription
Control0..1
TypeChoice of: string, uri
[x] NoteSeeChoice of Data Typesfor further information about how to use [x]
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension