Generated Narrative: ConceptMap R3-DataElement-element-map-to-R4B Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.3 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/DataElement|3.0.2 to StructureDefinitionversion: 4.3.0) Source Code Relationship Target Code Comment DataElement.meta (meta) maps to wider concept StructureDefinition.meta Element `DataElement.meta` is mapped to FHIR R4B element `StructureDefinition.meta` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.meta` do not cover the following types: Meta. The mappings for `DataElement.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. DataElement.implicitRules (implicitRules) is equivalent to StructureDefinition.implicitRules Element `DataElement.implicitRules` is mapped to FHIR R4B element `StructureDefinition.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. DataElement.language (language) is equivalent to StructureDefinition.language Element `DataElement.language` is mapped to FHIR R4B element `StructureDefinition.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). DataElement.text (text) maps to wider concept StructureDefinition.text Element `DataElement.text` is mapped to FHIR R4B element `StructureDefinition.text` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.text` do not cover the following types: Narrative. The mappings for `DataElement.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later. DataElement.contained (contained) is equivalent to StructureDefinition.contained Element `DataElement.contained` is mapped to FHIR R4B element `StructureDefinition.contained` as `SourceIsBroaderThanTarget`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. DataElement.url (url) is equivalent to StructureDefinition.url Element `DataElement.url` is mapped to FHIR R4B element `StructureDefinition.url` as `Equivalent`. Can be a urn:uuid: or a urn:oid:, but real http: addresses are preferred. Multiple instances may share the same url if they have a distinct version. DataElement.identifier (identifier) maps to wider concept StructureDefinition.identifier Element `DataElement.identifier` is mapped to FHIR R4B element `StructureDefinition.identifier` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.identifier` do not cover the following types: Identifier. The mappings for `DataElement.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, e.g., to identify this data element outside of FHIR, where it is not possible to use the logical URI. DataElement.version (version) is equivalent to StructureDefinition.version Element `DataElement.version` is mapped to FHIR R4B element `StructureDefinition.version` as `Equivalent`. There may be different data element instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a refrence to a particular business version of the data element with the format [url]|[version]. DataElement.status (status) is equivalent to StructureDefinition.status Element `DataElement.status` is mapped to FHIR R4B element `StructureDefinition.status` as `Equivalent`. Allows filtering of data elements that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use a retired data element without due consideration. DataElement.experimental (experimental) is equivalent to StructureDefinition.experimental Element `DataElement.experimental` is mapped to FHIR R4B element `StructureDefinition.experimental` as `Equivalent`. Allows filtering of data element that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use an experimental data element in production. DataElement.date (date) is equivalent to StructureDefinition.date Element `DataElement.date` is mapped to FHIR R4B element `StructureDefinition.date` as `Equivalent`. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the data element. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. DataElement.publisher (publisher) is equivalent to StructureDefinition.publisher Element `DataElement.publisher` is mapped to FHIR R4B element `StructureDefinition.publisher` as `Equivalent`. Usually an organization, but may be an individual. The publisher (or steward) of the data element is the organization or individual primarily responsible for the maintenance and upkeep of the data element. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the data element. This item SHOULD be populated unless the information is available from context. DataElement.name (name) is equivalent to StructureDefinition.name Element `DataElement.name` is mapped to FHIR R4B element `StructureDefinition.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly. DataElement.title (title) is equivalent to StructureDefinition.title Element `DataElement.title` is mapped to FHIR R4B element `StructureDefinition.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc. This may be similar to the question used to prompt someone for a data element value, but the purpose is communicating about the data element, not asking the question. (Refer to the 'question' element for the latter.). DataElement.contact (contact) maps to wider concept StructureDefinition.contact Element `DataElement.contact` is mapped to FHIR R4B element `StructureDefinition.contact` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.contact` do not cover the following types: ContactDetail. The mappings for `DataElement.contact` do not cover the following types based on type expansion: name, telecom. May be a web site, an email address, a telephone number, etc. DataElement.useContext (useContext) maps to wider concept StructureDefinition.useContext Element `DataElement.useContext` is mapped to FHIR R4B element `StructureDefinition.useContext` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.useContext` do not cover the following types: UsageContext. The mappings for `DataElement.useContext` do not cover the following types based on type expansion: code, value[x]. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply. DataElement.jurisdiction (jurisdiction) is equivalent to StructureDefinition.jurisdiction Element `DataElement.jurisdiction` is mapped to FHIR R4B element `StructureDefinition.jurisdiction` as `Equivalent`. It may be possible for the data element to be used in jurisdictions other than those for which it was originally designed or intended. DataElement.copyright (copyright) is equivalent to StructureDefinition.copyright Element `DataElement.copyright` is mapped to FHIR R4B element `StructureDefinition.copyright` as `Equivalent`. null The copyright statement does not apply to values for the data element, only to its definition. DataElement.mapping (mapping) maps to wider concept StructureDefinition.mapping Element `DataElement.mapping` is mapped to FHIR R4B element `StructureDefinition.mapping` as `Equivalent`. DataElement.mapping.identity (identity) is equivalent to StructureDefinition.mapping.identity Element `DataElement.mapping.identity` is mapped to FHIR R4B element `StructureDefinition.mapping.identity` as `Equivalent`. The specification is described once, with general comments, and then specific mappings are made that reference this declaration. DataElement.mapping.uri (uri) is equivalent to StructureDefinition.mapping.uri Element `DataElement.mapping.uri` is mapped to FHIR R4B element `StructureDefinition.mapping.uri` as `Equivalent`. A formal identity for the specification being mapped to helps with identifying maps consistently. DataElement.mapping.name (name) is equivalent to StructureDefinition.mapping.name Element `DataElement.mapping.name` is mapped to FHIR R4B element `StructureDefinition.mapping.name` as `Equivalent`. DataElement.mapping.comment (comment) is equivalent to StructureDefinition.mapping.comment Element `DataElement.mapping.comment` is mapped to FHIR R4B element `StructureDefinition.mapping.comment` as `Equivalent`. DataElement.element (element) maps to wider concept StructureDefinition.differential.element Element `DataElement.element` is mapped to FHIR R4B element `StructureDefinition.differential.element` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.element` do not cover the following types: ElementDefinition. The mappings for `DataElement.element` do not cover the following types based on type expansion: aggregation, alias, base, binding, code, comment, condition, constraint, contentReference, defaultValue[x], definition, description, discriminator, example, expression, fixed[x], human, identity, isModifier, isSummary, key, label, language, map, mapping, max, maxLength, maxValue[x], meaningWhenMissing, min, minValue[x], mustSupport, ordered, orderMeaning, path, pattern[x], profile, representation, requirements, rules, severity, short, sliceName, slicing, source, strength, targetProfile, type, value[x], valueSet[x], versioning, xpath. For simple data types there will only be one repetition. For complex data types, multiple repetitions will be present defining a nested structure using the "path" element. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/DataElement|3.0.2 to STU3: meta additional typesversion: 0.1.0) Source Code Relationship Target Code Comment DataElement.meta (meta) maps to wider concept Extension (STU3: meta additional types) Element `DataElement.meta` is mapped to FHIR R4B element `StructureDefinition.meta` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.meta` do not cover the following types: Meta. The mappings for `DataElement.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/DataElement|3.0.2 to STU3: text additional typesversion: 0.1.0) Source Code Relationship Target Code Comment DataElement.text (text) maps to wider concept Extension (STU3: text additional types) Element `DataElement.text` is mapped to FHIR R4B element `StructureDefinition.text` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.text` do not cover the following types: Narrative. The mappings for `DataElement.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/DataElement|3.0.2 to STU3: Additional identifier for the data element additional typesversion: 0.1.0) Source Code Relationship Target Code Comment DataElement.identifier (identifier) maps to wider concept Extension (STU3: Additional identifier for the data element additional types) Element `DataElement.identifier` is mapped to FHIR R4B element `StructureDefinition.identifier` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.identifier` do not cover the following types: Identifier. The mappings for `DataElement.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, e.g., to identify this data element outside of FHIR, where it is not possible to use the logical URI. Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/DataElement|3.0.2 to STU3: contact additional typesversion: 0.1.0) Source Code Relationship Target Code Comment DataElement.contact (contact) maps to wider concept Extension (STU3: contact additional types) Element `DataElement.contact` is mapped to FHIR R4B element `StructureDefinition.contact` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.contact` do not cover the following types: ContactDetail. The mappings for `DataElement.contact` do not cover the following types based on type expansion: name, telecom. May be a web site, an email address, a telephone number, etc. Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/DataElement|3.0.2 to STU3: Context the content is intended to support additional typesversion: 0.1.0) Source Code Relationship Target Code Comment DataElement.useContext (useContext) maps to wider concept Extension (STU3: Context the content is intended to support additional types) Element `DataElement.useContext` is mapped to FHIR R4B element `StructureDefinition.useContext` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.useContext` do not cover the following types: UsageContext. The mappings for `DataElement.useContext` do not cover the following types based on type expansion: code, value[x]. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply. Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/DataElement|3.0.2 to STU3: comparable | fully-specified | equivalent | convertable | scaleable | flexible (new)version: 0.1.0) Source Code Relationship Target Code Comment DataElement.stringency (stringency) is equivalent to Extension (STU3: comparable | fully-specified | equivalent | convertable | scaleable | flexible (new)) Element `DataElement.stringency` has a context of StructureDefinition based on following the parent source element upwards and mapping to `StructureDefinition`. Element `DataElement.stringency` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/DataElement|3.0.2 to STU3: Definition of element additional typesversion: 0.1.0) Source Code Relationship Target Code Comment DataElement.element (element) maps to wider concept Extension (STU3: Definition of element additional types) Element `DataElement.element` is mapped to FHIR R4B element `StructureDefinition.differential.element` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.element` do not cover the following types: ElementDefinition. The mappings for `DataElement.element` do not cover the following types based on type expansion: aggregation, alias, base, binding, code, comment, condition, constraint, contentReference, defaultValue[x], definition, description, discriminator, example, expression, fixed[x], human, identity, isModifier, isSummary, key, label, language, map, mapping, max, maxLength, maxValue[x], meaningWhenMissing, min, minValue[x], mustSupport, ordered, orderMeaning, path, pattern[x], profile, representation, requirements, rules, severity, short, sliceName, slicing, source, strength, targetProfile, type, value[x], valueSet[x], versioning, xpath. For simple data types there will only be one repetition. For complex data types, multiple repetitions will be present defining a nested structure using the "path" element.
Cross-version mapping for FHIR STU3 DataElement to FHIR R4B StructureDefinition
This ConceptMap represents cross-version mappings for elements from a FHIR STU3 DataElement to FHIR R4B.
Element `DataElement.meta` is mapped to FHIR R4B element `StructureDefinition.meta` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.meta` do not cover the following types: Meta. The mappings for `DataElement.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
Element `DataElement.implicitRules` is mapped to FHIR R4B element `StructureDefinition.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
Element `DataElement.language` is mapped to FHIR R4B element `StructureDefinition.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Element `DataElement.text` is mapped to FHIR R4B element `StructureDefinition.text` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.text` do not cover the following types: Narrative. The mappings for `DataElement.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.
Element `DataElement.contained` is mapped to FHIR R4B element `StructureDefinition.contained` as `SourceIsBroaderThanTarget`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.
Element `DataElement.url` is mapped to FHIR R4B element `StructureDefinition.url` as `Equivalent`. Can be a urn:uuid: or a urn:oid:, but real http: addresses are preferred. Multiple instances may share the same url if they have a distinct version.
Element `DataElement.identifier` is mapped to FHIR R4B element `StructureDefinition.identifier` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.identifier` do not cover the following types: Identifier. The mappings for `DataElement.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, e.g., to identify this data element outside of FHIR, where it is not possible to use the logical URI.
Element `DataElement.version` is mapped to FHIR R4B element `StructureDefinition.version` as `Equivalent`. There may be different data element instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a refrence to a particular business version of the data element with the format [url]|[version].
Element `DataElement.status` is mapped to FHIR R4B element `StructureDefinition.status` as `Equivalent`. Allows filtering of data elements that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use a retired data element without due consideration.
Element `DataElement.experimental` is mapped to FHIR R4B element `StructureDefinition.experimental` as `Equivalent`. Allows filtering of data element that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use an experimental data element in production.
Element `DataElement.date` is mapped to FHIR R4B element `StructureDefinition.date` as `Equivalent`. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the data element. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
Element `DataElement.publisher` is mapped to FHIR R4B element `StructureDefinition.publisher` as `Equivalent`. Usually an organization, but may be an individual. The publisher (or steward) of the data element is the organization or individual primarily responsible for the maintenance and upkeep of the data element. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the data element. This item SHOULD be populated unless the information is available from context.
Element `DataElement.name` is mapped to FHIR R4B element `StructureDefinition.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly.
Element `DataElement.title` is mapped to FHIR R4B element `StructureDefinition.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc. This may be similar to the question used to prompt someone for a data element value, but the purpose is communicating about the data element, not asking the question. (Refer to the 'question' element for the latter.).
Element `DataElement.contact` is mapped to FHIR R4B element `StructureDefinition.contact` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.contact` do not cover the following types: ContactDetail. The mappings for `DataElement.contact` do not cover the following types based on type expansion: name, telecom. May be a web site, an email address, a telephone number, etc.
Element `DataElement.useContext` is mapped to FHIR R4B element `StructureDefinition.useContext` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.useContext` do not cover the following types: UsageContext. The mappings for `DataElement.useContext` do not cover the following types based on type expansion: code, value[x]. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.
Element `DataElement.jurisdiction` is mapped to FHIR R4B element `StructureDefinition.jurisdiction` as `Equivalent`. It may be possible for the data element to be used in jurisdictions other than those for which it was originally designed or intended.
Element `DataElement.copyright` is mapped to FHIR R4B element `StructureDefinition.copyright` as `Equivalent`. null The copyright statement does not apply to values for the data element, only to its definition.
Element `DataElement.mapping` is mapped to FHIR R4B element `StructureDefinition.mapping` as `Equivalent`.
Element `DataElement.mapping.identity` is mapped to FHIR R4B element `StructureDefinition.mapping.identity` as `Equivalent`. The specification is described once, with general comments, and then specific mappings are made that reference this declaration.
Element `DataElement.mapping.uri` is mapped to FHIR R4B element `StructureDefinition.mapping.uri` as `Equivalent`. A formal identity for the specification being mapped to helps with identifying maps consistently.
Element `DataElement.mapping.name` is mapped to FHIR R4B element `StructureDefinition.mapping.name` as `Equivalent`.
Element `DataElement.mapping.comment` is mapped to FHIR R4B element `StructureDefinition.mapping.comment` as `Equivalent`.
Element `DataElement.element` is mapped to FHIR R4B element `StructureDefinition.differential.element` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.element` do not cover the following types: ElementDefinition. The mappings for `DataElement.element` do not cover the following types based on type expansion: aggregation, alias, base, binding, code, comment, condition, constraint, contentReference, defaultValue[x], definition, description, discriminator, example, expression, fixed[x], human, identity, isModifier, isSummary, key, label, language, map, mapping, max, maxLength, maxValue[x], meaningWhenMissing, min, minValue[x], mustSupport, ordered, orderMeaning, path, pattern[x], profile, representation, requirements, rules, severity, short, sliceName, slicing, source, strength, targetProfile, type, value[x], valueSet[x], versioning, xpath. For simple data types there will only be one repetition. For complex data types, multiple repetitions will be present defining a nested structure using the "path" element.
Element `DataElement.stringency` has a context of StructureDefinition based on following the parent source element upwards and mapping to `StructureDefinition`. Element `DataElement.stringency` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).