Release 4B

This page is part of the FHIR Specification (v4.3.0: R4B - STU). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

2.30.3 Element Definition Mappings

FHIR Infrastructure Work GroupMaturity Level: N/AStandards Status: Informative

This page provides mappings for Element Definition (see Mappings to Other Standards for further information & status).

Many other standard frameworks define frameworks for defining "data elements". These overlap to some degree with the ElementDefinition type. This page provides general mappings between ElementDefinition and the other frameworks. One important consideration with regard to other Element definition frameworks is the scope of the definition. Many of these definition frameworks use the term "Data Element" to refer to a data item that is collected and stored with provenance, such as when it was collected, who recorded it, etc. In this specification, that's an Observation, and the definition of this kind of data element is an ObservationDefinition, or a StructureDefinition that contains several different atomic data items. An ElementDefinition in this specification is a narrower notion, solely around the characteristics of a single element, it's definition, and it's value domain . Other frameworks - especially ISO 11179 - are used in both ways, sometimes with no formal differentiation between them. For this reason, the mappings on this page are very provisional, and are provided with the intent of helping implementers understand the possible relationships.

On this page:

v2 Mappings to the V2 segment OM1 which is used to define observations (i.e. also related to ObservationDefinition)
RIM Mappings to the RIM class Observation in definition mood which is used to define observations (i.e. also related to ObservationDefinition)
IHE DEX Mappings IHE Data Element Exchange, which is closer to defining atomic data elements - still very incomplete
LOINC Mappings to the LOINC master table which defines observations (i.e. also related to ObservationDefinition)
ISO 11179 Mappings to ISO 11179 which details how the ElementDefinition class relates to the ISO 11179 framework. Note that the principle differences are that FHIR does not differentiate between a Data Element and a Data Element Value, and the FHIR specification is heavily type dependent. Also, the FHIR specification includes constraints and other concerns that are outside the scope of ISO 11179

2.30.3.1 HL7 v2 Mapping (http://hl7.org/v2)

ElementDefinitionOM1
    pathN/A
    representationN/A
    sliceNameN/A
    sliceIsConstrainingN/A
    label
    codeOM1.7
    slicing
        discriminator
            type
            path
        description
        ordered
        rules
    short
    definitionOM1.6, OM1.41
    commentNTE, OM1.32, OM1.33, OM1.39
    requirements
    aliasOM1.8, OM1.52
    min
    maxOMC.10
    base
        path
        min
        max
    contentReference
    typeOM1.3, OMC.9
        codeOM1.3
        profile
        targetProfile
        aggregation
        versioning
    defaultValue[x]
    meaningWhenMissing
    orderMeaning
    fixed[x]
    pattern[x]
    example
        label
        value[x]
    minValue[x]
    maxValue[x]
    maxLengthOMC.12
    condition
    constraint
        key
        requirements
        severity
        human
        expression
        xpath
        source
    mustSupport
    isModifier
    isModifierReason
    isSummary
    bindingOM3, OMC.11
        strengthN/A
        description
        valueSet
    mapping
        identity
        language
        map
        comment

2.30.3.2 RIM Mapping (http://hl7.org/v3)

ElementDefinitionObservation[classCode=OBS, moodCode=DEFN]
    pathN/A
    representationN/A
    sliceNameN/A
    sliceIsConstrainingN/A
    label./code/display
    code./code (root or translation)
    slicingN/A
        discriminatorN/A
            typeN/A
            pathN/A
        descriptionN/A
        orderedN/A
        rulesN/A
    shortN/A
    definition./text
    comment./inboundRelationship[typeCode=SUBJ]/source[classCode=LIST, moodCode=EVN]/code
    requirements./inboundRelationship[typeCode=META]/source[classCode=ACT, moodCode=EVN, isCriterionInd=true]/reasonCode/originalText
    aliasNot currently expressible
    minN/A (MIF territory)
    maxN/A (MIF territory)
    baseN/A (MIF territory)
        pathN/A (MIF territory)
        minN/A (MIF territory)
        maxN/A (MIF territory)
    contentReferenceN/A
    typeN/A (MIF territory)
        codeN/A (MIF territory)
        profileN/A (MIF territory)
        targetProfileN/A (MIF territory)
        aggregationN/A (MIF territory)
        versioningN/A (MIF territory)
    defaultValue[x]N/A (MIF territory)
    meaningWhenMissingN/A (MIF territory)
    orderMeaningN/A (MIF territory)
    fixed[x]N/A (MIF territory)
    pattern[x]N/A (MIF territory)
    exampleN/A (MIF territory)
        labelN/A (MIF territory)
        value[x]N/A (MIF territory)
    minValue[x]N/A (MIF territory)
    maxValue[x]N/A (MIF territory)
    maxLengthN/A (MIF territory)
    conditionN/A (MIF territory)
    constraintN/A (MIF territory)
        keyN/A (MIF territory)
        requirementsN/A (MIF territory)
        severityN/A (MIF territory)
        humanN/A (MIF territory)
        expressionN/A (MIF territory)
        xpathN/A (MIF territory)
        sourceN/A (MIF territory)
    mustSupportN/A (MIF territory)
    isModifierN/A (MIF territory)
    isModifierReasonN/A (MIF territory)
    isSummaryN/A (MIF territory)
    bindingN/A (MIF territory)
        strengthN/A (MIF territory)
        descriptionN/A (MIF territory)
        valueSetN/A (MIF territory)
    mappingN/A (MIF territory)
        identityN/A (MIF territory)
        languageN/A (MIF territory)
        mapN/A (MIF territory)
        commentN/A (MIF territory)

2.30.3.3 IHE Data Element Exchange (DEX) (http://ihe.net/data-element-exchange)

ElementDefinitionRetrieveMetadata response
    path
    representation
    sliceName
    sliceIsConstraining
    label
    code
    slicing
        discriminator
            type
            path
        description
        ordered
        rules
    short
    definition
    comment
    requirements
    alias
    min
    max
    base
        path
        min
        max
    contentReference
    typevalueDomain.dataType
        code
        profile
        targetProfile
        aggregation
        versioning
    defaultValue[x]
    meaningWhenMissing
    orderMeaning
    fixed[x]
    pattern[x]
    example
        label
        value[x]
    minValue[x]
    maxValue[x]
    maxLength
    condition
    constraint
        key
        requirements
        severity
        human
        expression
        xpath
        source
    mustSupport
    isModifier
    isModifierReason
    isSummary
    binding
        strength
        description
        valueSetvalueDomain.valueSet
    mappingmappingSpecification
        identity
        language
        map
        comment

2.30.3.4 LOINC code for the element (http://loinc.org)

ElementDefinition
    path
    representation
    sliceName
    sliceIsConstraining
    label
    codeLOINC_NUM
    slicing
        discriminator
            type
            path
        description
        ordered
        rules
    short
    definitionTERM DEFINITION/DESCRIPTION(S)
    commentCOMMENTS
    requirements
    aliasRELATED NAMES (only some of these apply)
    min
    max
    base
        path
        min
        max
    contentReference
    typeHL7_V2_DATATYPE (translation required), HL7_V3_DATATYPE (translation required)
        codeHL7_V2_DATATYPE (translation required), HL7_V3_DATATYPE (translation required)
        profile
        targetProfile
        aggregation
        versioning
    defaultValue[x]
    meaningWhenMissing
    orderMeaning
    fixed[x]
    pattern[x]
    example
        label
        value[x]EXMPL_ANSWERS
    minValue[x]
    maxValue[x]
    maxLength
    condition
    constraint
        key
        requirements
        severity
        human
        expression
        xpath
        source
    mustSupport
    isModifier
    isModifierReason
    isSummary
    bindingANSWER LIST, NORMATIVE ANSWER LIST
        strengthN/A
        description
        valueSetCODE_TABLE
    mapping
        identity
        language
        map
        comment

2.30.3.5 ISO 11179 (http://metadata-standards.org/11179/)

ElementDefinitionData_Element
    pathName, Identifier & Context
    representationn/a
    sliceNamen/a
    sliceIsConstrainingn/a
    labeln/a
    code(Data_Element).data_element_concept.identifier
    slicingn/a
        discriminatorn/a
            type
            pathn/a
        description
        orderedn/a
        rulesn/a
    shortN/A
    definition(Designatable_Item).definition.text acceptability=preferred in default context
    comment(Administered_Item).explanatory_comment
    requirements(Registered_item).document_reference[document_type=requirements].notation
    alias(Designatable_Item).designation.sign acceptability!=preferred or context is other than default
    minMinimum size of data element values?
    maxMaximum size of data element values?
    basen/a
        pathn/a
        minn/a
        maxn/a
    contentReference
    type.domain.data+Q14type
        code.domain.data+Q14type
        profilen/a
        targetProfilen/a
        aggregationn/a
        versioning
    defaultValue[x]
    meaningWhenMissing
    orderMeaning
    fixed[x]N/A (only relevant when constraining, which 11179 doesn't do)
    pattern[x]
    example
        label
        value[x].example
    minValue[x]
    maxValue[x]
    maxLength.domain.maximum_character_quantity
    condition
    constraint??
        key
        requirements
        severity
        human
        expression
        xpath
        source
    mustSupport??
    isModifier??
    isModifierReason
    isSummary??
    binding.domain
        strength
        description.domain.description
        valueSetpoints to explicit list or expression that evaluates to list of (Enumerated_Value_Domain).member
    mappingRegistered_item).document_reference[document_type=mapping] Also, .meaning linkage to Data_Element_Concept is done as a mapping to a reference model. (Data_Element_Concepts are all defined in some sort of reference model, be that Object_Class and Property or some other mechanism)
        identity
        language
        mapObjectClass, Property (this is one possible data model that can be mapped to - the uri would identify the data model mappingSpecification.mappingScript
        comment