Generated Narrative: ConceptMap R5-ConceptMap-element-map-to-R4 Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ConceptMap|5.0.0 to ConceptMapversion: 4.0.1) Source Code Relationship Target Code Comment ConceptMap.meta (meta) is equivalent to ConceptMap.meta Element `ConceptMap.meta` is mapped to FHIR R4 element `ConceptMap.meta` as `Equivalent`. ConceptMap.implicitRules (implicitRules) is equivalent to ConceptMap.implicitRules Element `ConceptMap.implicitRules` is mapped to FHIR R4 element `ConceptMap.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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc. ConceptMap.language (language) is equivalent to ConceptMap.language Element `ConceptMap.language` is mapped to FHIR R4 element `ConceptMap.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). ConceptMap.text (text) is equivalent to ConceptMap.text Element `ConceptMap.text` is mapped to FHIR R4 element `ConceptMap.text` as `Equivalent`. Contained resources do not have a 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 information is added later. ConceptMap.contained (contained) is equivalent to ConceptMap.contained Element `ConceptMap.contained` is mapped to FHIR R4 element `ConceptMap.contained` as `Equivalent`. 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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. ConceptMap.url (url) is equivalent to ConceptMap.url Element `ConceptMap.url` is mapped to FHIR R4 element `ConceptMap.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. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions). In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found. ConceptMap.identifier (identifier) is equivalent to ConceptMap.identifier Element `ConceptMap.identifier` is mapped to FHIR R4 element `ConceptMap.identifier` as `SourceIsBroaderThanTarget`. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this concept map outside of FHIR, where it is not possible to use the logical URI. ConceptMap.version (version) is equivalent to ConceptMap.version Element `ConceptMap.version` is mapped to FHIR R4 element `ConceptMap.version` as `Equivalent`. There may be different concept map instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the concept map with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format). ConceptMap.name (name) is equivalent to ConceptMap.name Element `ConceptMap.name` is mapped to FHIR R4 element `ConceptMap.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly. ConceptMap.title (title) is equivalent to ConceptMap.title Element `ConceptMap.title` is mapped to FHIR R4 element `ConceptMap.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc. ConceptMap.status (status) is equivalent to ConceptMap.status Element `ConceptMap.status` is mapped to FHIR R4 element `ConceptMap.status` as `Equivalent`. Allows filtering of concept maps that are appropriate for use versus not. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). ConceptMap.experimental (experimental) is equivalent to ConceptMap.experimental Element `ConceptMap.experimental` is mapped to FHIR R4 element `ConceptMap.experimental` as `Equivalent`. Allows filtering of concept maps that are appropriate for use versus not. ConceptMap.date (date) is equivalent to ConceptMap.date Element `ConceptMap.date` is mapped to FHIR R4 element `ConceptMap.date` as `Equivalent`. The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the concept map. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). ConceptMap.publisher (publisher) is equivalent to ConceptMap.publisher Element `ConceptMap.publisher` is mapped to FHIR R4 element `ConceptMap.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the concept map is the organization or individual primarily responsible for the maintenance and upkeep of the concept map. 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 concept map. This item SHOULD be populated unless the information is available from context. ConceptMap.contact (contact) is equivalent to ConceptMap.contact Element `ConceptMap.contact` is mapped to FHIR R4 element `ConceptMap.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). ConceptMap.description (description) is equivalent to ConceptMap.description Element `ConceptMap.description` is mapped to FHIR R4 element `ConceptMap.description` as `Equivalent`. The description is not intended to describe the semantics of the concept map. The description should capture its intended use, which is needed for ensuring integrity for its use in models across future changes. ConceptMap.useContext (useContext) is equivalent to ConceptMap.useContext Element `ConceptMap.useContext` is mapped to FHIR R4 element `ConceptMap.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply. ConceptMap.jurisdiction (jurisdiction) is equivalent to ConceptMap.jurisdiction Element `ConceptMap.jurisdiction` is mapped to FHIR R4 element `ConceptMap.jurisdiction` as `Equivalent`. Element `ConceptMap.jurisdiction` has been flagged as deprecated. It may be possible for the concept map to be used in jurisdictions other than those for which it was originally designed or intended. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.) ConceptMap.purpose (purpose) is equivalent to ConceptMap.purpose Element `ConceptMap.purpose` is mapped to FHIR R4 element `ConceptMap.purpose` as `Equivalent`. This element does not describe the usage of the concept map. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this concept map. ConceptMap.copyright (copyright) is equivalent to ConceptMap.copyright Element `ConceptMap.copyright` is mapped to FHIR R4 element `ConceptMap.copyright` as `Equivalent`. Frequently the copyright differs between the concept map and codes that are included. The copyright statement should clearly differentiate between these when required. ConceptMap.sourceScope[x] (sourceScope[x]) is equivalent to ConceptMap.source[x] Element `ConceptMap.sourceScope[x]` is mapped to FHIR R4 element `ConceptMap.source[x]` as `Equivalent`. The target context `ConceptMap.source[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ConceptMap`. Should be a version specific reference. URIs SHOULD be absolute. If there is no sourceScope or targetScope value set, there is no specified context for the map (not recommended). The sourceScope value set may select codes from either an explicit (standard or local) or implicit code system. ConceptMap.targetScope[x] (targetScope[x]) is equivalent to ConceptMap.target[x] Element `ConceptMap.targetScope[x]` is mapped to FHIR R4 element `ConceptMap.target[x]` as `Equivalent`. The target context `ConceptMap.target[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ConceptMap`. Should be a version specific reference. URIs SHOULD be absolute. If there is no sourceScope or targetScope value set, there is no specified context for the map (not recommended). The targetScope value set may select codes from either an explicit (standard or local) or implicit code system. ConceptMap.group (group) maps to wider concept ConceptMap.group Element `ConceptMap.group` is mapped to FHIR R4 element `ConceptMap.group` as `Equivalent`. ConceptMap.group.source (source) is equivalent to ConceptMap.group.source Element `ConceptMap.group.source` is mapped to FHIR R4 element `ConceptMap.group.source` as `Equivalent`. This is not needed if the source value set is specified and it contains concepts from only a single system. ConceptMap.group.target (target) is equivalent to ConceptMap.group.target Element `ConceptMap.group.target` is mapped to FHIR R4 element `ConceptMap.group.target` as `Equivalent`. This is not needed if the target value set is specified and it contains concepts from only a single system. The group target may also be omitted if all of the target element relationship values are 'not-related-to'. ConceptMap.group.element (element) maps to wider concept ConceptMap.group.element Element `ConceptMap.group.element` is mapped to FHIR R4 element `ConceptMap.group.element` as `Equivalent`. Generally, the ideal is that there would only be one mapping for each concept in the source value set, but a given concept may be mapped multiple times with different comments or dependencies. ConceptMap.group.element.code (code) is equivalent to ConceptMap.group.element.code Element `ConceptMap.group.element.code` is mapped to FHIR R4 element `ConceptMap.group.element.code` as `Equivalent`. ConceptMap.group.element.display (display) is equivalent to ConceptMap.group.element.display Element `ConceptMap.group.element.display` is mapped to FHIR R4 element `ConceptMap.group.element.display` as `Equivalent`. The display is ignored when processing the map. ConceptMap.group.element.noMap (noMap) maps to wider concept ConceptMap.group.element.target.equivalence Element `ConceptMap.group.element.noMap` is mapped to FHIR R4 element `ConceptMap.group.element.target.equivalence` as `SourceIsBroaderThanTarget`. The mappings for `ConceptMap.group.element.noMap` do not cover the following types: boolean. The mappings for `ConceptMap.group.element.noMap` do not cover the following types based on type expansion: value. If noMap = true, then the behavior of ConceptMap.group.unmapped (if present) does not apply. ConceptMap.group.element.target (target) maps to wider concept ConceptMap.group.element.target Element `ConceptMap.group.element.target` is mapped to FHIR R4 element `ConceptMap.group.element.target` as `Equivalent`. Ideally there would only be one map, with an 'equivalent' mapping. But multiple maps are allowed for several narrower (i.e. source-is-broader-than-target) options, or to assert that other concepts are not related. ConceptMap.group.element.target.code (code) is equivalent to ConceptMap.group.element.target.code Element `ConceptMap.group.element.target.code` is mapped to FHIR R4 element `ConceptMap.group.element.target.code` as `Equivalent`. ConceptMap.group.element.target.display (display) is equivalent to ConceptMap.group.element.target.display Element `ConceptMap.group.element.target.display` is mapped to FHIR R4 element `ConceptMap.group.element.target.display` as `Equivalent`. The display is ignored when processing the map. ConceptMap.group.element.target.relationship (relationship) narrower ConceptMap.group.element.target.equivalence Element `ConceptMap.group.element.target.relationship` is mapped to FHIR R4 element `ConceptMap.group.element.target.equivalence` as `SourceIsNarrowerThanTarget`. The mappings for `ConceptMap.group.element.target.relationship` do not allow expression of the necessary codes, per the bindings on the source and target. This element is labeled as a modifier because it may indicate that there is no mapping. ConceptMap.group.element.target.comment (comment) is equivalent to ConceptMap.group.element.target.comment Element `ConceptMap.group.element.target.comment` is mapped to FHIR R4 element `ConceptMap.group.element.target.comment` as `Equivalent`. ConceptMap.group.element.target.dependsOn (dependsOn) maps to wider concept ConceptMap.group.element.target.dependsOn Element `ConceptMap.group.element.target.dependsOn` is mapped to FHIR R4 element `ConceptMap.group.element.target.dependsOn` as `Equivalent`. ConceptMap.group.element.target.dependsOn.attribute (attribute) maps to wider concept ConceptMap.group.element.target.dependsOn.property Element `ConceptMap.group.element.target.dependsOn.attribute` is mapped to FHIR R4 element `ConceptMap.group.element.target.dependsOn.property` as `SourceIsBroaderThanTarget`. The mappings for `ConceptMap.group.element.target.dependsOn.attribute` do not cover the following types: code. The mappings for `ConceptMap.group.element.target.dependsOn.attribute` do not cover the following types based on type expansion: value. ConceptMap.group.element.target.dependsOn.value[x] (value[x]) maps to wider concept ConceptMap.group.element.target.dependsOn.value Element `ConceptMap.group.element.target.dependsOn.value[x]` is mapped to FHIR R4 element `ConceptMap.group.element.target.dependsOn.value` as `SourceIsBroaderThanTarget`. The mappings for `ConceptMap.group.element.target.dependsOn.value[x]` do not cover the following types: boolean, Coding, Quantity. If the data type is a code, then the code system is .group.source for .dependsOn.valueCode and .group.target for .product.valueCode. ConceptMap.group.element.target.product (product) is equivalent to ConceptMap.group.element.target.product Element `ConceptMap.group.element.target.product` is mapped to FHIR R4 element `ConceptMap.group.element.target.product` as `Equivalent`. ConceptMap.group.unmapped (unmapped) maps to wider concept ConceptMap.group.unmapped Element `ConceptMap.group.unmapped` is mapped to FHIR R4 element `ConceptMap.group.unmapped` as `Equivalent`. The 'unmapped' element is ignored if a code is specified to have relationship = not-related-to or if ConceptMap.group.element.noMap = true. ConceptMap.group.unmapped.mode (mode) is equivalent to ConceptMap.group.unmapped.mode Element `ConceptMap.group.unmapped.mode` is mapped to FHIR R4 element `ConceptMap.group.unmapped.mode` as `Equivalent`. ConceptMap.group.unmapped.code (code) is equivalent to ConceptMap.group.unmapped.code Element `ConceptMap.group.unmapped.code` is mapped to FHIR R4 element `ConceptMap.group.unmapped.code` as `Equivalent`. ConceptMap.group.unmapped.display (display) is equivalent to ConceptMap.group.unmapped.display Element `ConceptMap.group.unmapped.display` is mapped to FHIR R4 element `ConceptMap.group.unmapped.display` as `Equivalent`. The display is ignored when processing the map. ConceptMap.group.unmapped.otherMap (otherMap) is equivalent to ConceptMap.group.unmapped.url Element `ConceptMap.group.unmapped.otherMap` is mapped to FHIR R4 element `ConceptMap.group.unmapped.url` as `Equivalent`. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/ConceptMap|5.0.0 to R5: Additional properties of the mapping (new)version: 0.1.0) Source Code Relationship Target Code Comment ConceptMap.property (property) maps to wider concept Extension (R5: Additional properties of the mapping (new)) Element `ConceptMap.property` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.property` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Properties may be used to supply for example, mapping priority, provenance, presentation hints, flag as experimental, and additional documentation. Multiple occurrences of ConceptMap.group.element.target.property may occur for a ConceptMap.property where ConceptMap.group.element.target.property.code is the same and the values in ConceptMap.group.element.target.property.value differ. ConceptMap.property.code (code) maps to wider concept Extension.extension:code (R5: Identifies the property on the mappings, and when referred to in the $translate operation (new)) Element `ConceptMap.property.code` is part of an existing definition because parent element `ConceptMap.property` requires a cross-version extension. Element `ConceptMap.property.code` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.property.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). ConceptMap.property.uri (uri) maps to wider concept Extension.extension:uri (R5: Formal identifier for the property (new)) Element `ConceptMap.property.uri` is part of an existing definition because parent element `ConceptMap.property` requires a cross-version extension. Element `ConceptMap.property.uri` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.property.uri` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). ConceptMap.property.description (description) maps to wider concept Extension.extension:description (R5: Why the property is defined, and/or what it conveys (new)) Element `ConceptMap.property.description` is part of an existing definition because parent element `ConceptMap.property` requires a cross-version extension. Element `ConceptMap.property.description` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.property.description` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). ConceptMap.property.type (type) maps to wider concept Extension.extension:type (R5: Coding | string | integer | boolean | dateTime | decimal | code (new)) Element `ConceptMap.property.type` is part of an existing definition because parent element `ConceptMap.property` requires a cross-version extension. Element `ConceptMap.property.type` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.property.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). ConceptMap.property.system (system) maps to wider concept Extension.extension:system (R5: The CodeSystem from which code values come (new)) Element `ConceptMap.property.system` is part of an existing definition because parent element `ConceptMap.property` requires a cross-version extension. Element `ConceptMap.property.system` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.property.system` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/ConceptMap|5.0.0 to R5: Definition of an additional attribute to act as a data source or target (new)version: 0.1.0) Source Code Relationship Target Code Comment ConceptMap.additionalAttribute (additionalAttribute) maps to wider concept Extension (R5: Definition of an additional attribute to act as a data source or target (new)) Element `ConceptMap.additionalAttribute` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.additionalAttribute` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Additional attributes are used to define additional data elements where mapping data can be found. For an example, see [Specimen Type v2 -> SNOMED CT Mapping(conceptmap-example-specimen-type.html) ConceptMap.additionalAttribute.code (code) maps to wider concept Extension.extension:code (R5: Identifies this additional attribute through this resource (new)) Element `ConceptMap.additionalAttribute.code` is part of an existing definition because parent element `ConceptMap.additionalAttribute` requires a cross-version extension. Element `ConceptMap.additionalAttribute.code` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.additionalAttribute.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). ConceptMap.additionalAttribute.uri (uri) maps to wider concept Extension.extension:uri (R5: Formal identifier for the data element referred to in this attribte (new)) Element `ConceptMap.additionalAttribute.uri` is part of an existing definition because parent element `ConceptMap.additionalAttribute` requires a cross-version extension. Element `ConceptMap.additionalAttribute.uri` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.additionalAttribute.uri` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). ConceptMap.additionalAttribute.description (description) maps to wider concept Extension.extension:description (R5: Why the additional attribute is defined, and/or what the data element it refers to is (new)) Element `ConceptMap.additionalAttribute.description` is part of an existing definition because parent element `ConceptMap.additionalAttribute` requires a cross-version extension. Element `ConceptMap.additionalAttribute.description` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.additionalAttribute.description` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). ConceptMap.additionalAttribute.type (type) maps to wider concept Extension.extension:type (R5: code | Coding | string | boolean | Quantity (new)) Element `ConceptMap.additionalAttribute.type` is part of an existing definition because parent element `ConceptMap.additionalAttribute` requires a cross-version extension. Element `ConceptMap.additionalAttribute.type` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.additionalAttribute.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). When the source or target is not content defined by FHIR, some additional application logic might be required to map from the FHIR Datatype to the externally defined content Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/ConceptMap|5.0.0 to R5: Identifies the set of concepts being mapped (new)version: 0.1.0) Source Code Relationship Target Code Comment ConceptMap.group.element.valueSet (valueSet) maps to wider concept Extension (R5: Identifies the set of concepts being mapped (new)) Element `ConceptMap.group.element.valueSet` has a context of ConceptMap.group.element based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.group.element.valueSet` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If the value set expansion is empty then there are no source concepts to map in this rule. Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/ConceptMap|5.0.0 to R5: No mapping to a target concept for this source concept additional typesversion: 0.1.0) Source Code Relationship Target Code Comment ConceptMap.group.element.noMap (noMap) maps to wider concept Extension (R5: No mapping to a target concept for this source concept additional types) Element `ConceptMap.group.element.noMap` is mapped to FHIR R4 element `ConceptMap.group.element.target.equivalence` as `SourceIsBroaderThanTarget`. The mappings for `ConceptMap.group.element.noMap` do not cover the following types: boolean. The mappings for `ConceptMap.group.element.noMap` do not cover the following types based on type expansion: value. If noMap = true, then the behavior of ConceptMap.group.unmapped (if present) does not apply. Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/ConceptMap|5.0.0 to R5: Identifies the set of target concepts (new)version: 0.1.0) Source Code Relationship Target Code Comment ConceptMap.group.element.target.valueSet (valueSet) maps to wider concept Extension (R5: Identifies the set of target concepts (new)) Element `ConceptMap.group.element.target.valueSet` has a context of ConceptMap.group.element.target based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.group.element.target.valueSet` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If the the value set expansion is empty then the source concept(s) are unmapped and the behavior of ConceptMap.group.unmapped (if present) applies. Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/ConceptMap|5.0.0 to R5: Property value for the source -> target mapping (new)version: 0.1.0) Source Code Relationship Target Code Comment ConceptMap.group.element.target.property (property) maps to wider concept Extension (R5: Property value for the source -> target mapping (new)) Element `ConceptMap.group.element.target.property` has a context of ConceptMap.group.element.target based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.group.element.target.property` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). ConceptMap.group.element.target.property.code (code) maps to wider concept Extension.extension:code (R5: Reference to ConceptMap.property.code (new)) Element `ConceptMap.group.element.target.property.code` is part of an existing definition because parent element `ConceptMap.group.element.target.property` requires a cross-version extension. Element `ConceptMap.group.element.target.property.code` has a context of ConceptMap.group.element.target based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.group.element.target.property.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). ConceptMap.group.element.target.property.value[x] (value[x]) maps to wider concept Extension.extension:value (R5: Value of the property for this concept (new)) Element `ConceptMap.group.element.target.property.value[x]` is part of an existing definition because parent element `ConceptMap.group.element.target.property` requires a cross-version extension. Element `ConceptMap.group.element.target.property.value[x]` has a context of ConceptMap.group.element.target based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.group.element.target.property.value[x]` 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/ConceptMap|5.0.0 to R5: A reference to a mapping attribute defined in ConceptMap.additionalAttribute additional typesversion: 0.1.0) Source Code Relationship Target Code Comment ConceptMap.group.element.target.dependsOn.attribute (attribute) maps to wider concept Extension (R5: A reference to a mapping attribute defined in ConceptMap.additionalAttribute additional types) Element `ConceptMap.group.element.target.dependsOn.attribute` is mapped to FHIR R4 element `ConceptMap.group.element.target.dependsOn.property` as `SourceIsBroaderThanTarget`. The mappings for `ConceptMap.group.element.target.dependsOn.attribute` do not cover the following types: code. The mappings for `ConceptMap.group.element.target.dependsOn.attribute` do not cover the following types based on type expansion: value. Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/ConceptMap|5.0.0 to R5: Value of the referenced data element additional typesversion: 0.1.0) Source Code Relationship Target Code Comment ConceptMap.group.element.target.dependsOn.value[x] (value[x]) maps to wider concept Extension (R5: Value of the referenced data element additional types) Element `ConceptMap.group.element.target.dependsOn.value[x]` is mapped to FHIR R4 element `ConceptMap.group.element.target.dependsOn.value` as `SourceIsBroaderThanTarget`. The mappings for `ConceptMap.group.element.target.dependsOn.value[x]` do not cover the following types: boolean, Coding, Quantity. If the data type is a code, then the code system is .group.source for .dependsOn.valueCode and .group.target for .product.valueCode. Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/ConceptMap|5.0.0 to R5: The mapping depends on a data element with a value from this value set (new)version: 0.1.0) Source Code Relationship Target Code Comment ConceptMap.group.element.target.dependsOn.valueSet (valueSet) maps to wider concept Extension (R5: The mapping depends on a data element with a value from this value set (new)) Element `ConceptMap.group.element.target.dependsOn.valueSet` has a context of ConceptMap.group.element.target.dependsOn based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.group.element.target.dependsOn.valueSet` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/ConceptMap|5.0.0 to R5: Fixed code set when mode = fixed (new)version: 0.1.0) Source Code Relationship Target Code Comment ConceptMap.group.unmapped.valueSet (valueSet) maps to wider concept Extension (R5: Fixed code set when mode = fixed (new)) Element `ConceptMap.group.unmapped.valueSet` has a context of ConceptMap.group.unmapped based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.group.unmapped.valueSet` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/ConceptMap|5.0.0 to R5: related-to | equivalent | source-is-narrower-than-target | source-is-broader-than-target | not-related-to (new)version: 0.1.0) Source Code Relationship Target Code Comment ConceptMap.group.unmapped.relationship (relationship) maps to wider concept Extension (R5: related-to | equivalent | source-is-narrower-than-target | source-is-broader-than-target | not-related-to (new)) Element `ConceptMap.group.unmapped.relationship` has a context of ConceptMap.group.unmapped based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.group.unmapped.relationship` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This element is labeled as a modifier because it may indicate that there is no mapping.
Cross-version mapping for FHIR R5 ConceptMap to FHIR R4 ConceptMap
This ConceptMap represents cross-version mappings for elements from a FHIR R5 ConceptMap to FHIR R4.
Element `ConceptMap.meta` is mapped to FHIR R4 element `ConceptMap.meta` as `Equivalent`.
Element `ConceptMap.implicitRules` is mapped to FHIR R4 element `ConceptMap.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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
Element `ConceptMap.language` is mapped to FHIR R4 element `ConceptMap.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 `ConceptMap.text` is mapped to FHIR R4 element `ConceptMap.text` as `Equivalent`. Contained resources do not have a 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 information is added later.
Element `ConceptMap.contained` is mapped to FHIR R4 element `ConceptMap.contained` as `Equivalent`. 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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
Element `ConceptMap.url` is mapped to FHIR R4 element `ConceptMap.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. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions). In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found.
Element `ConceptMap.identifier` is mapped to FHIR R4 element `ConceptMap.identifier` as `SourceIsBroaderThanTarget`. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this concept map outside of FHIR, where it is not possible to use the logical URI.
Element `ConceptMap.version` is mapped to FHIR R4 element `ConceptMap.version` as `Equivalent`. There may be different concept map instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the concept map with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format).
Element `ConceptMap.name` is mapped to FHIR R4 element `ConceptMap.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.
Element `ConceptMap.title` is mapped to FHIR R4 element `ConceptMap.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
Element `ConceptMap.status` is mapped to FHIR R4 element `ConceptMap.status` as `Equivalent`. Allows filtering of concept maps that are appropriate for use versus not. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
Element `ConceptMap.experimental` is mapped to FHIR R4 element `ConceptMap.experimental` as `Equivalent`. Allows filtering of concept maps that are appropriate for use versus not.
Element `ConceptMap.date` is mapped to FHIR R4 element `ConceptMap.date` as `Equivalent`. The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the concept map. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
Element `ConceptMap.publisher` is mapped to FHIR R4 element `ConceptMap.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the concept map is the organization or individual primarily responsible for the maintenance and upkeep of the concept map. 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 concept map. This item SHOULD be populated unless the information is available from context.
Element `ConceptMap.contact` is mapped to FHIR R4 element `ConceptMap.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
Element `ConceptMap.description` is mapped to FHIR R4 element `ConceptMap.description` as `Equivalent`. The description is not intended to describe the semantics of the concept map. The description should capture its intended use, which is needed for ensuring integrity for its use in models across future changes.
Element `ConceptMap.useContext` is mapped to FHIR R4 element `ConceptMap.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
Element `ConceptMap.jurisdiction` is mapped to FHIR R4 element `ConceptMap.jurisdiction` as `Equivalent`. Element `ConceptMap.jurisdiction` has been flagged as deprecated. It may be possible for the concept map to be used in jurisdictions other than those for which it was originally designed or intended. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)
Element `ConceptMap.purpose` is mapped to FHIR R4 element `ConceptMap.purpose` as `Equivalent`. This element does not describe the usage of the concept map. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this concept map.
Element `ConceptMap.copyright` is mapped to FHIR R4 element `ConceptMap.copyright` as `Equivalent`. Frequently the copyright differs between the concept map and codes that are included. The copyright statement should clearly differentiate between these when required.
Element `ConceptMap.sourceScope[x]` is mapped to FHIR R4 element `ConceptMap.source[x]` as `Equivalent`. The target context `ConceptMap.source[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ConceptMap`. Should be a version specific reference. URIs SHOULD be absolute. If there is no sourceScope or targetScope value set, there is no specified context for the map (not recommended). The sourceScope value set may select codes from either an explicit (standard or local) or implicit code system.
Element `ConceptMap.targetScope[x]` is mapped to FHIR R4 element `ConceptMap.target[x]` as `Equivalent`. The target context `ConceptMap.target[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ConceptMap`. Should be a version specific reference. URIs SHOULD be absolute. If there is no sourceScope or targetScope value set, there is no specified context for the map (not recommended). The targetScope value set may select codes from either an explicit (standard or local) or implicit code system.
Element `ConceptMap.group` is mapped to FHIR R4 element `ConceptMap.group` as `Equivalent`.
Element `ConceptMap.group.source` is mapped to FHIR R4 element `ConceptMap.group.source` as `Equivalent`. This is not needed if the source value set is specified and it contains concepts from only a single system.
Element `ConceptMap.group.target` is mapped to FHIR R4 element `ConceptMap.group.target` as `Equivalent`. This is not needed if the target value set is specified and it contains concepts from only a single system. The group target may also be omitted if all of the target element relationship values are 'not-related-to'.
Element `ConceptMap.group.element` is mapped to FHIR R4 element `ConceptMap.group.element` as `Equivalent`. Generally, the ideal is that there would only be one mapping for each concept in the source value set, but a given concept may be mapped multiple times with different comments or dependencies.
Element `ConceptMap.group.element.code` is mapped to FHIR R4 element `ConceptMap.group.element.code` as `Equivalent`.
Element `ConceptMap.group.element.display` is mapped to FHIR R4 element `ConceptMap.group.element.display` as `Equivalent`. The display is ignored when processing the map.
Element `ConceptMap.group.element.noMap` is mapped to FHIR R4 element `ConceptMap.group.element.target.equivalence` as `SourceIsBroaderThanTarget`. The mappings for `ConceptMap.group.element.noMap` do not cover the following types: boolean. The mappings for `ConceptMap.group.element.noMap` do not cover the following types based on type expansion: value. If noMap = true, then the behavior of ConceptMap.group.unmapped (if present) does not apply.
Element `ConceptMap.group.element.target` is mapped to FHIR R4 element `ConceptMap.group.element.target` as `Equivalent`. Ideally there would only be one map, with an 'equivalent' mapping. But multiple maps are allowed for several narrower (i.e. source-is-broader-than-target) options, or to assert that other concepts are not related.
Element `ConceptMap.group.element.target.code` is mapped to FHIR R4 element `ConceptMap.group.element.target.code` as `Equivalent`.
Element `ConceptMap.group.element.target.display` is mapped to FHIR R4 element `ConceptMap.group.element.target.display` as `Equivalent`. The display is ignored when processing the map.
Element `ConceptMap.group.element.target.relationship` is mapped to FHIR R4 element `ConceptMap.group.element.target.equivalence` as `SourceIsNarrowerThanTarget`. The mappings for `ConceptMap.group.element.target.relationship` do not allow expression of the necessary codes, per the bindings on the source and target. This element is labeled as a modifier because it may indicate that there is no mapping.
Element `ConceptMap.group.element.target.comment` is mapped to FHIR R4 element `ConceptMap.group.element.target.comment` as `Equivalent`.
Element `ConceptMap.group.element.target.dependsOn` is mapped to FHIR R4 element `ConceptMap.group.element.target.dependsOn` as `Equivalent`.
Element `ConceptMap.group.element.target.dependsOn.attribute` is mapped to FHIR R4 element `ConceptMap.group.element.target.dependsOn.property` as `SourceIsBroaderThanTarget`. The mappings for `ConceptMap.group.element.target.dependsOn.attribute` do not cover the following types: code. The mappings for `ConceptMap.group.element.target.dependsOn.attribute` do not cover the following types based on type expansion: value.
Element `ConceptMap.group.element.target.dependsOn.value[x]` is mapped to FHIR R4 element `ConceptMap.group.element.target.dependsOn.value` as `SourceIsBroaderThanTarget`. The mappings for `ConceptMap.group.element.target.dependsOn.value[x]` do not cover the following types: boolean, Coding, Quantity. If the data type is a code, then the code system is .group.source for .dependsOn.valueCode and .group.target for .product.valueCode.
Element `ConceptMap.group.element.target.product` is mapped to FHIR R4 element `ConceptMap.group.element.target.product` as `Equivalent`.
Element `ConceptMap.group.unmapped` is mapped to FHIR R4 element `ConceptMap.group.unmapped` as `Equivalent`. The 'unmapped' element is ignored if a code is specified to have relationship = not-related-to or if ConceptMap.group.element.noMap = true.
Element `ConceptMap.group.unmapped.mode` is mapped to FHIR R4 element `ConceptMap.group.unmapped.mode` as `Equivalent`.
Element `ConceptMap.group.unmapped.code` is mapped to FHIR R4 element `ConceptMap.group.unmapped.code` as `Equivalent`.
Element `ConceptMap.group.unmapped.display` is mapped to FHIR R4 element `ConceptMap.group.unmapped.display` as `Equivalent`. The display is ignored when processing the map.
Element `ConceptMap.group.unmapped.otherMap` is mapped to FHIR R4 element `ConceptMap.group.unmapped.url` as `Equivalent`.
Element `ConceptMap.property` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.property` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Properties may be used to supply for example, mapping priority, provenance, presentation hints, flag as experimental, and additional documentation. Multiple occurrences of ConceptMap.group.element.target.property may occur for a ConceptMap.property where ConceptMap.group.element.target.property.code is the same and the values in ConceptMap.group.element.target.property.value differ.
Element `ConceptMap.property.code` is part of an existing definition because parent element `ConceptMap.property` requires a cross-version extension. Element `ConceptMap.property.code` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.property.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ConceptMap.property.uri` is part of an existing definition because parent element `ConceptMap.property` requires a cross-version extension. Element `ConceptMap.property.uri` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.property.uri` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ConceptMap.property.description` is part of an existing definition because parent element `ConceptMap.property` requires a cross-version extension. Element `ConceptMap.property.description` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.property.description` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ConceptMap.property.type` is part of an existing definition because parent element `ConceptMap.property` requires a cross-version extension. Element `ConceptMap.property.type` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.property.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ConceptMap.property.system` is part of an existing definition because parent element `ConceptMap.property` requires a cross-version extension. Element `ConceptMap.property.system` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.property.system` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ConceptMap.additionalAttribute` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.additionalAttribute` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Additional attributes are used to define additional data elements where mapping data can be found. For an example, see [Specimen Type v2 -> SNOMED CT Mapping(conceptmap-example-specimen-type.html)
Element `ConceptMap.additionalAttribute.code` is part of an existing definition because parent element `ConceptMap.additionalAttribute` requires a cross-version extension. Element `ConceptMap.additionalAttribute.code` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.additionalAttribute.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ConceptMap.additionalAttribute.uri` is part of an existing definition because parent element `ConceptMap.additionalAttribute` requires a cross-version extension. Element `ConceptMap.additionalAttribute.uri` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.additionalAttribute.uri` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ConceptMap.additionalAttribute.description` is part of an existing definition because parent element `ConceptMap.additionalAttribute` requires a cross-version extension. Element `ConceptMap.additionalAttribute.description` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.additionalAttribute.description` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ConceptMap.additionalAttribute.type` is part of an existing definition because parent element `ConceptMap.additionalAttribute` requires a cross-version extension. Element `ConceptMap.additionalAttribute.type` has a context of ConceptMap based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.additionalAttribute.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). When the source or target is not content defined by FHIR, some additional application logic might be required to map from the FHIR Datatype to the externally defined content
Element `ConceptMap.group.element.valueSet` has a context of ConceptMap.group.element based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.group.element.valueSet` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If the value set expansion is empty then there are no source concepts to map in this rule.
Element `ConceptMap.group.element.target.valueSet` has a context of ConceptMap.group.element.target based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.group.element.target.valueSet` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If the the value set expansion is empty then the source concept(s) are unmapped and the behavior of ConceptMap.group.unmapped (if present) applies.
Element `ConceptMap.group.element.target.property` has a context of ConceptMap.group.element.target based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.group.element.target.property` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ConceptMap.group.element.target.property.code` is part of an existing definition because parent element `ConceptMap.group.element.target.property` requires a cross-version extension. Element `ConceptMap.group.element.target.property.code` has a context of ConceptMap.group.element.target based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.group.element.target.property.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ConceptMap.group.element.target.property.value[x]` is part of an existing definition because parent element `ConceptMap.group.element.target.property` requires a cross-version extension. Element `ConceptMap.group.element.target.property.value[x]` has a context of ConceptMap.group.element.target based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.group.element.target.property.value[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ConceptMap.group.element.target.dependsOn.valueSet` has a context of ConceptMap.group.element.target.dependsOn based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.group.element.target.dependsOn.valueSet` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ConceptMap.group.unmapped.valueSet` has a context of ConceptMap.group.unmapped based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.group.unmapped.valueSet` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ConceptMap.group.unmapped.relationship` has a context of ConceptMap.group.unmapped based on following the parent source element upwards and mapping to `ConceptMap`. Element `ConceptMap.group.unmapped.relationship` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This element is labeled as a modifier because it may indicate that there is no mapping.