Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4 - Downloaded Version null See the Directory of published versions

ConceptMap: R2DataElementElementMapToR4

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R2-DataElement-element-map-to-R4 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R2DataElementElementMapToR4

This ConceptMap represents cross-version mappings for elements from a FHIR DSTU2 DataElement to FHIR R4.

Mapping from http://hl7.org/fhir/1.0 to http://hl7.org/fhir/4.0


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/DataElement|1.0.2 to StructureDefinitionversion: 4.0.1)

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from http://hl7.org/fhir/StructureDefinition/DataElement|1.0.2Codes from StructureDefinition
DataElement.metametamaps to wider conceptStructureDefinition.metaStructureDefinition.metaElement `DataElement.meta` is mapped to FHIR R4 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.implicitRulesimplicitRulesis equivalent toStructureDefinition.implicitRulesStructureDefinition.implicitRulesElement `DataElement.implicitRules` is mapped to FHIR R4 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 as much as possible.
DataElement.languagelanguageis equivalent toStructureDefinition.languageStructureDefinition.languageElement `DataElement.language` is mapped to FHIR R4 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.texttextmaps to wider conceptStructureDefinition.textStructureDefinition.textElement `DataElement.text` is mapped to FHIR R4 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.
DataElement.containedcontainedis equivalent toStructureDefinition.containedStructureDefinition.containedElement `DataElement.contained` is mapped to FHIR R4 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.urlurlis equivalent toStructureDefinition.urlStructureDefinition.urlElement `DataElement.url` is mapped to FHIR R4 element `StructureDefinition.url` as `Equivalent`.
DataElement.identifieridentifiermaps to wider conceptStructureDefinition.identifierStructureDefinition.identifierElement `DataElement.identifier` is mapped to FHIR R4 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 values that can go in a v3 II data type.
DataElement.versionversionis equivalent toStructureDefinition.versionStructureDefinition.versionElement `DataElement.version` is mapped to FHIR R4 element `StructureDefinition.version` as `Equivalent`. N/A.
DataElement.namenameis equivalent toStructureDefinition.nameStructureDefinition.nameElement `DataElement.name` is mapped to FHIR R4 element `StructureDefinition.name` as `Equivalent`. 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.statusstatusnarrowerStructureDefinition.statusStructureDefinition.statusElement `DataElement.status` is mapped to FHIR R4 element `StructureDefinition.status` as `SourceIsNarrowerThanTarget`. The mappings for `DataElement.status` do not allow expression of the necessary codes, per the bindings on the source and target.
DataElement.experimentalexperimentalis equivalent toStructureDefinition.experimentalStructureDefinition.experimentalElement `DataElement.experimental` is mapped to FHIR R4 element `StructureDefinition.experimental` as `Equivalent`. Allows filtering of search data element definitions that are appropriate for use vs. not.
DataElement.publisherpublisheris equivalent toStructureDefinition.publisherStructureDefinition.publisherElement `DataElement.publisher` is mapped to FHIR R4 element `StructureDefinition.publisher` as `Equivalent`. Usually an organization, but may be an individual. This item SHOULD be populated unless the information is available from context.
DataElement.contactcontactmaps to wider conceptStructureDefinition.contactStructureDefinition.contactElement `DataElement.contact` is mapped to FHIR R4 element `StructureDefinition.contact` as `Equivalent`. May be a web site, an email address, a telephone number (tel:), etc.
DataElement.contact.namenameis related toStructureDefinition.contactStructureDefinition.contactElement `DataElement.contact.name` is mapped to FHIR R4 element `StructureDefinition.contact` as `RelatedTo`. The mappings for `DataElement.contact.name` do not cover the following types: string. The mappings for `DataElement.contact.name` do not cover the following types based on type expansion: value. If there is no named individual, the telecom is for the organization as a whole.
DataElement.contact.telecomtelecommaps to wider conceptStructureDefinition.contactStructureDefinition.contactElement `DataElement.contact.telecom` is mapped to FHIR R4 element `StructureDefinition.contact` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.contact.telecom` do not cover the following types: ContactPoint. The mappings for `DataElement.contact.telecom` do not cover the following types based on type expansion: period, rank, system, use, value.
DataElement.datedateis equivalent toStructureDefinition.dateStructureDefinition.dateElement `DataElement.date` is mapped to FHIR R4 element `StructureDefinition.date` as `Equivalent`. This refers to the "business" version, the DataElement.version which changes based on business processes. It does not refer to the date of the RESTful version which is part of the resource metadata. Additional specific dates may be added as extensions.
DataElement.useContextuseContextis equivalent toStructureDefinition.jurisdictionStructureDefinition.jurisdictionElement `DataElement.useContext` is mapped to FHIR R4 element `StructureDefinition.useContext` as `SourceIsBroaderThanTarget`. Element `DataElement.useContext` is mapped to FHIR R4 element `StructureDefinition.jurisdiction` as `Equivalent`.
is related toStructureDefinition.useContextStructureDefinition.useContextElement `DataElement.useContext` is mapped to FHIR R4 element `StructureDefinition.useContext` as `SourceIsBroaderThanTarget`. Element `DataElement.useContext` is mapped to FHIR R4 element `StructureDefinition.jurisdiction` as `Equivalent`.
DataElement.copyrightcopyrightis equivalent toStructureDefinition.copyrightStructureDefinition.copyrightElement `DataElement.copyright` is mapped to FHIR R4 element `StructureDefinition.copyright` as `Equivalent`. The copyright statement does not apply to values for the data element, only to its definition.
DataElement.mappingmappingmaps to wider conceptStructureDefinition.mappingStructureDefinition.mappingElement `DataElement.mapping` is mapped to FHIR R4 element `StructureDefinition.mapping` as `Equivalent`.
DataElement.mapping.identityidentityis equivalent toStructureDefinition.mapping.identityStructureDefinition.mapping.identityElement `DataElement.mapping.identity` is mapped to FHIR R4 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.uriuriis equivalent toStructureDefinition.mapping.uriStructureDefinition.mapping.uriElement `DataElement.mapping.uri` is mapped to FHIR R4 element `StructureDefinition.mapping.uri` as `Equivalent`. A formal identity for the specification being mapped to helps with identifying maps consistently.
DataElement.mapping.namenameis equivalent toStructureDefinition.mapping.nameStructureDefinition.mapping.nameElement `DataElement.mapping.name` is mapped to FHIR R4 element `StructureDefinition.mapping.name` as `Equivalent`.
DataElement.mapping.commentscommentsis equivalent toStructureDefinition.mapping.commentStructureDefinition.mapping.commentElement `DataElement.mapping.comments` is mapped to FHIR R4 element `StructureDefinition.mapping.comment` as `Equivalent`.
DataElement.elementelementmaps to wider conceptStructureDefinition.differential.elementStructureDefinition.differential.elementElement `DataElement.element` is mapped to FHIR R4 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, comments, condition, constraint, defaultValue[x], definition, description, discriminator, example[x], fixed[x], human, identity, isModifier, isSummary, key, label, language, map, mapping, max, maxLength, maxValue[x], meaningWhenMissing, min, minValue[x], mustSupport, name, nameReference, ordered, path, pattern[x], profile, representation, requirements, rules, severity, short, slicing, strength, type, valueSet[x], 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|1.0.2 to DSTU2: meta additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DataElement.meta (meta)maps to wider conceptExtension (DSTU2: meta additional types)Element `DataElement.meta` is mapped to FHIR R4 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|1.0.2 to DSTU2: text additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DataElement.text (text)maps to wider conceptExtension (DSTU2: text additional types)Element `DataElement.text` is mapped to FHIR R4 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.

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/DataElement|1.0.2 to DSTU2: Logical id to reference this data element additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DataElement.identifier (identifier)maps to wider conceptExtension (DSTU2: Logical id to reference this data element additional types)Element `DataElement.identifier` is mapped to FHIR R4 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 values that can go in a v3 II data type.

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/DataElement|1.0.2 to DSTU2: Name of a individual to contact additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DataElement.contact.name (name)maps to wider conceptExtension (DSTU2: Name of a individual to contact additional types)Element `DataElement.contact.name` is mapped to FHIR R4 element `StructureDefinition.contact` as `RelatedTo`. The mappings for `DataElement.contact.name` do not cover the following types: string. The mappings for `DataElement.contact.name` do not cover the following types based on type expansion: value. If there is no named individual, the telecom is for the organization as a whole.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/DataElement|1.0.2 to DSTU2: Contact details for individual or publisher additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DataElement.contact.telecom (telecom)maps to wider conceptExtension (DSTU2: Contact details for individual or publisher additional types)Element `DataElement.contact.telecom` is mapped to FHIR R4 element `StructureDefinition.contact` as `SourceIsBroaderThanTarget`. The mappings for `DataElement.contact.telecom` do not cover the following types: ContactPoint. The mappings for `DataElement.contact.telecom` do not cover the following types based on type expansion: period, rank, system, use, value.

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/DataElement|1.0.2 to DSTU2: comparable | fully-specified | equivalent | convertable | scaleable | flexible (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DataElement.stringency (stringency)is equivalent toExtension (DSTU2: 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 R4. Typically, this is because the element has been added (is a new element).

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/DataElement|1.0.2 to DSTU2: Definition of element additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DataElement.element (element)maps to wider conceptExtension (DSTU2: Definition of element additional types)Element `DataElement.element` is mapped to FHIR R4 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, comments, condition, constraint, defaultValue[x], definition, description, discriminator, example[x], fixed[x], human, identity, isModifier, isSummary, key, label, language, map, mapping, max, maxLength, maxValue[x], meaningWhenMissing, min, minValue[x], mustSupport, name, nameReference, ordered, path, pattern[x], profile, representation, requirements, rules, severity, short, slicing, strength, type, valueSet[x], 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.