Generated Narrative: ConceptMap R5-StructureDefinition-element-map-to-R3 Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/3.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/StructureDefinition|5.0.0 to http://hl7.org/fhir/StructureDefinition/DataElement|3.0.2 Source Code Relationship Target Code Comment StructureDefinition.meta (meta) is equivalent to DataElement.meta Element `StructureDefinition.meta` is mapped to FHIR STU3 element `DataElement.meta` as `Equivalent`. Element `StructureDefinition.meta` is mapped to FHIR STU3 element `StructureDefinition.meta` as `Equivalent`. StructureDefinition.implicitRules (implicitRules) is equivalent to DataElement.implicitRules Element `StructureDefinition.implicitRules` is mapped to FHIR STU3 element `DataElement.implicitRules` as `Equivalent`. Element `StructureDefinition.implicitRules` is mapped to FHIR STU3 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. 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. StructureDefinition.language (language) is equivalent to DataElement.language Element `StructureDefinition.language` is mapped to FHIR STU3 element `DataElement.language` as `Equivalent`. Element `StructureDefinition.language` is mapped to FHIR STU3 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). StructureDefinition.text (text) is equivalent to DataElement.text Element `StructureDefinition.text` is mapped to FHIR STU3 element `DataElement.text` as `Equivalent`. Element `StructureDefinition.text` is mapped to FHIR STU3 element `StructureDefinition.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. StructureDefinition.contained (contained) is related to DataElement.contained Element `StructureDefinition.contained` is mapped to FHIR STU3 element `DataElement.contained` as `SourceIsBroaderThanTarget`. Element `StructureDefinition.contained` is mapped to FHIR STU3 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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. StructureDefinition.url (url) is equivalent to DataElement.url Element `StructureDefinition.url` is mapped to FHIR STU3 element `DataElement.url` as `Equivalent`. Element `StructureDefinition.url` is mapped to FHIR STU3 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. 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. StructureDefinition.identifier (identifier) is equivalent to DataElement.identifier Element `StructureDefinition.identifier` is mapped to FHIR STU3 element `DataElement.identifier` as `Equivalent`. Element `StructureDefinition.identifier` is mapped to FHIR STU3 element `StructureDefinition.identifier` as `Equivalent`. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this structure definition outside of FHIR, where it is not possible to use the logical URI. StructureDefinition.version (version) is equivalent to DataElement.version Element `StructureDefinition.version` is mapped to FHIR STU3 element `DataElement.version` as `Equivalent`. Element `StructureDefinition.version` is mapped to FHIR STU3 element `StructureDefinition.version` as `Equivalent`. There may be different structure definition 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 structure definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format). StructureDefinition.name (name) is equivalent to DataElement.name Element `StructureDefinition.name` is mapped to FHIR STU3 element `DataElement.name` as `Equivalent`. Element `StructureDefinition.name` is mapped to FHIR STU3 element `StructureDefinition.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.Some Examples: * O2SatObservation * PresentationReport * Immunization2 * AcmeAdmissionRecordOld. StructureDefinition.title (title) is equivalent to DataElement.title Element `StructureDefinition.title` is mapped to FHIR STU3 element `DataElement.title` as `Equivalent`. Element `StructureDefinition.title` is mapped to FHIR STU3 element `StructureDefinition.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.Applications don't have to use this name but can always fall back to it. The title also corresponds to the label for the root element. StructureDefinition.status (status) is equivalent to DataElement.status Element `StructureDefinition.status` is mapped to FHIR STU3 element `DataElement.status` as `Equivalent`. Element `StructureDefinition.status` is mapped to FHIR STU3 element `StructureDefinition.status` as `Equivalent`. Allows filtering of structure definitions that are appropriate for use versus not. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). StructureDefinition.experimental (experimental) is equivalent to DataElement.experimental Element `StructureDefinition.experimental` is mapped to FHIR STU3 element `DataElement.experimental` as `Equivalent`. Element `StructureDefinition.experimental` is mapped to FHIR STU3 element `StructureDefinition.experimental` as `Equivalent`. Allows filtering of structure definitions that are appropriate for use versus not. StructureDefinition.date (date) is equivalent to DataElement.date Element `StructureDefinition.date` is mapped to FHIR STU3 element `DataElement.date` as `Equivalent`. Element `StructureDefinition.date` is mapped to FHIR STU3 element `StructureDefinition.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 structure definition. 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). StructureDefinition.publisher (publisher) is equivalent to DataElement.publisher Element `StructureDefinition.publisher` is mapped to FHIR STU3 element `DataElement.publisher` as `Equivalent`. Element `StructureDefinition.publisher` is mapped to FHIR STU3 element `StructureDefinition.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the structure definition is the organization or individual primarily responsible for the maintenance and upkeep of the structure definition. 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 structure definition. This item SHOULD be populated unless the information is available from context. StructureDefinition.contact (contact) is related to DataElement.contact Element `StructureDefinition.contact` is mapped to FHIR STU3 element `DataElement.contact` as `SourceIsBroaderThanTarget`. Element `StructureDefinition.contact` is mapped to FHIR STU3 element `StructureDefinition.contact` as `SourceIsBroaderThanTarget`. The mappings for `StructureDefinition.contact` do not cover the following types: ContactDetail. The mappings for `StructureDefinition.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. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). StructureDefinition.useContext (useContext) is equivalent to DataElement.useContext Element `StructureDefinition.useContext` is mapped to FHIR STU3 element `DataElement.useContext` as `Equivalent`. Element `StructureDefinition.useContext` is mapped to FHIR STU3 element `StructureDefinition.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply. StructureDefinition.jurisdiction (jurisdiction) is equivalent to DataElement.jurisdiction Element `StructureDefinition.jurisdiction` is mapped to FHIR STU3 element `DataElement.jurisdiction` as `Equivalent`. Element `StructureDefinition.jurisdiction` is mapped to FHIR STU3 element `StructureDefinition.jurisdiction` as `Equivalent`. Element `StructureDefinition.jurisdiction` has been flagged as deprecated. It may be possible for the structure definition 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.) StructureDefinition.copyright (copyright) is equivalent to DataElement.copyright Element `StructureDefinition.copyright` is mapped to FHIR STU3 element `DataElement.copyright` as `Equivalent`. Element `StructureDefinition.copyright` is mapped to FHIR STU3 element `StructureDefinition.copyright` as `Equivalent`. ... StructureDefinition.mapping (mapping) is related to DataElement.mapping Element `StructureDefinition.mapping` is mapped to FHIR STU3 element `DataElement.mapping` as `Equivalent`. Element `StructureDefinition.mapping` is mapped to FHIR STU3 element `StructureDefinition.mapping` as `Equivalent`. StructureDefinition.mapping.identity (identity) is equivalent to DataElement.mapping.identity Element `StructureDefinition.mapping.identity` is mapped to FHIR STU3 element `DataElement.mapping.identity` as `Equivalent`. Element `StructureDefinition.mapping.identity` is mapped to FHIR STU3 element `StructureDefinition.mapping.identity` as `Equivalent`. The specification is described once, with general comments, and then specific mappings are made that reference this declaration. StructureDefinition.mapping.uri (uri) is equivalent to DataElement.mapping.uri Element `StructureDefinition.mapping.uri` is mapped to FHIR STU3 element `DataElement.mapping.uri` as `Equivalent`. Element `StructureDefinition.mapping.uri` is mapped to FHIR STU3 element `StructureDefinition.mapping.uri` as `Equivalent`. A formal identity for the specification being mapped to helps with identifying maps consistently. StructureDefinition.mapping.name (name) is equivalent to DataElement.mapping.name Element `StructureDefinition.mapping.name` is mapped to FHIR STU3 element `DataElement.mapping.name` as `Equivalent`. Element `StructureDefinition.mapping.name` is mapped to FHIR STU3 element `StructureDefinition.mapping.name` as `Equivalent`. StructureDefinition.mapping.comment (comment) is equivalent to DataElement.mapping.comment Element `StructureDefinition.mapping.comment` is mapped to FHIR STU3 element `DataElement.mapping.comment` as `Equivalent`. Element `StructureDefinition.mapping.comment` is mapped to FHIR STU3 element `StructureDefinition.mapping.comment` as `Equivalent`. StructureDefinition.differential.element (element) is equivalent to DataElement.element Element `StructureDefinition.differential.element` is mapped to FHIR STU3 element `DataElement.element` as `Equivalent`. Element `StructureDefinition.differential.element` is mapped to FHIR STU3 element `StructureDefinition.differential.element` as `Equivalent`. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/StructureDefinition|5.0.0 to http://hl7.org/fhir/StructureDefinition/StructureDefinition|3.0.2 Source Code Relationship Target Code Comment StructureDefinition.meta (meta) is equivalent to StructureDefinition.meta Element `StructureDefinition.meta` is mapped to FHIR STU3 element `DataElement.meta` as `Equivalent`. Element `StructureDefinition.meta` is mapped to FHIR STU3 element `StructureDefinition.meta` as `Equivalent`. StructureDefinition.implicitRules (implicitRules) is equivalent to StructureDefinition.implicitRules Element `StructureDefinition.implicitRules` is mapped to FHIR STU3 element `DataElement.implicitRules` as `Equivalent`. Element `StructureDefinition.implicitRules` is mapped to FHIR STU3 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. 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. StructureDefinition.language (language) is equivalent to StructureDefinition.language Element `StructureDefinition.language` is mapped to FHIR STU3 element `DataElement.language` as `Equivalent`. Element `StructureDefinition.language` is mapped to FHIR STU3 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). StructureDefinition.text (text) is equivalent to StructureDefinition.text Element `StructureDefinition.text` is mapped to FHIR STU3 element `DataElement.text` as `Equivalent`. Element `StructureDefinition.text` is mapped to FHIR STU3 element `StructureDefinition.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. StructureDefinition.contained (contained) is related to StructureDefinition.contained Element `StructureDefinition.contained` is mapped to FHIR STU3 element `DataElement.contained` as `SourceIsBroaderThanTarget`. Element `StructureDefinition.contained` is mapped to FHIR STU3 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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. StructureDefinition.url (url) is equivalent to StructureDefinition.url Element `StructureDefinition.url` is mapped to FHIR STU3 element `DataElement.url` as `Equivalent`. Element `StructureDefinition.url` is mapped to FHIR STU3 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. 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. StructureDefinition.identifier (identifier) is equivalent to StructureDefinition.identifier Element `StructureDefinition.identifier` is mapped to FHIR STU3 element `DataElement.identifier` as `Equivalent`. Element `StructureDefinition.identifier` is mapped to FHIR STU3 element `StructureDefinition.identifier` as `Equivalent`. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this structure definition outside of FHIR, where it is not possible to use the logical URI. StructureDefinition.version (version) is equivalent to StructureDefinition.version Element `StructureDefinition.version` is mapped to FHIR STU3 element `DataElement.version` as `Equivalent`. Element `StructureDefinition.version` is mapped to FHIR STU3 element `StructureDefinition.version` as `Equivalent`. There may be different structure definition 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 structure definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format). StructureDefinition.name (name) is equivalent to StructureDefinition.name Element `StructureDefinition.name` is mapped to FHIR STU3 element `DataElement.name` as `Equivalent`. Element `StructureDefinition.name` is mapped to FHIR STU3 element `StructureDefinition.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.Some Examples: * O2SatObservation * PresentationReport * Immunization2 * AcmeAdmissionRecordOld. StructureDefinition.title (title) is equivalent to StructureDefinition.title Element `StructureDefinition.title` is mapped to FHIR STU3 element `DataElement.title` as `Equivalent`. Element `StructureDefinition.title` is mapped to FHIR STU3 element `StructureDefinition.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.Applications don't have to use this name but can always fall back to it. The title also corresponds to the label for the root element. StructureDefinition.status (status) is equivalent to StructureDefinition.status Element `StructureDefinition.status` is mapped to FHIR STU3 element `DataElement.status` as `Equivalent`. Element `StructureDefinition.status` is mapped to FHIR STU3 element `StructureDefinition.status` as `Equivalent`. Allows filtering of structure definitions that are appropriate for use versus not. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). StructureDefinition.experimental (experimental) is equivalent to StructureDefinition.experimental Element `StructureDefinition.experimental` is mapped to FHIR STU3 element `DataElement.experimental` as `Equivalent`. Element `StructureDefinition.experimental` is mapped to FHIR STU3 element `StructureDefinition.experimental` as `Equivalent`. Allows filtering of structure definitions that are appropriate for use versus not. StructureDefinition.date (date) is equivalent to StructureDefinition.date Element `StructureDefinition.date` is mapped to FHIR STU3 element `DataElement.date` as `Equivalent`. Element `StructureDefinition.date` is mapped to FHIR STU3 element `StructureDefinition.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 structure definition. 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). StructureDefinition.publisher (publisher) is equivalent to StructureDefinition.publisher Element `StructureDefinition.publisher` is mapped to FHIR STU3 element `DataElement.publisher` as `Equivalent`. Element `StructureDefinition.publisher` is mapped to FHIR STU3 element `StructureDefinition.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the structure definition is the organization or individual primarily responsible for the maintenance and upkeep of the structure definition. 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 structure definition. This item SHOULD be populated unless the information is available from context. StructureDefinition.contact (contact) is related to StructureDefinition.contact Element `StructureDefinition.contact` is mapped to FHIR STU3 element `DataElement.contact` as `SourceIsBroaderThanTarget`. Element `StructureDefinition.contact` is mapped to FHIR STU3 element `StructureDefinition.contact` as `SourceIsBroaderThanTarget`. The mappings for `StructureDefinition.contact` do not cover the following types: ContactDetail. The mappings for `StructureDefinition.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. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). StructureDefinition.description (description) is equivalent to StructureDefinition.description Element `StructureDefinition.description` is mapped to FHIR STU3 element `StructureDefinition.description` as `Equivalent`. This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the structure definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the structure definition is presumed to be the predominant language in the place the structure definition was created). StructureDefinition.useContext (useContext) is equivalent to StructureDefinition.useContext Element `StructureDefinition.useContext` is mapped to FHIR STU3 element `DataElement.useContext` as `Equivalent`. Element `StructureDefinition.useContext` is mapped to FHIR STU3 element `StructureDefinition.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply. StructureDefinition.jurisdiction (jurisdiction) is equivalent to StructureDefinition.jurisdiction Element `StructureDefinition.jurisdiction` is mapped to FHIR STU3 element `DataElement.jurisdiction` as `Equivalent`. Element `StructureDefinition.jurisdiction` is mapped to FHIR STU3 element `StructureDefinition.jurisdiction` as `Equivalent`. Element `StructureDefinition.jurisdiction` has been flagged as deprecated. It may be possible for the structure definition 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.) StructureDefinition.purpose (purpose) is equivalent to StructureDefinition.purpose Element `StructureDefinition.purpose` is mapped to FHIR STU3 element `StructureDefinition.purpose` as `Equivalent`. This element does not describe the usage of the structure definition. 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 structure definition. StructureDefinition.copyright (copyright) is equivalent to StructureDefinition.copyright Element `StructureDefinition.copyright` is mapped to FHIR STU3 element `DataElement.copyright` as `Equivalent`. Element `StructureDefinition.copyright` is mapped to FHIR STU3 element `StructureDefinition.copyright` as `Equivalent`. ... StructureDefinition.keyword (keyword) is equivalent to StructureDefinition.keyword Element `StructureDefinition.keyword` is mapped to FHIR STU3 element `StructureDefinition.keyword` as `Equivalent`. Element `StructureDefinition.keyword` has been flagged as deprecated. Note that this element is deprecated. Use the [http://hl7.org/fhir/StructureDefinition/artifact-topic](http://hl7.org/fhir/extensions/StructureDefinition-artifact-topic.html) extension instead. StructureDefinition.fhirVersion (fhirVersion) is related to StructureDefinition.fhirVersion Element `StructureDefinition.fhirVersion` is mapped to FHIR STU3 element `StructureDefinition.fhirVersion` as `SourceIsBroaderThanTarget`. The mappings for `StructureDefinition.fhirVersion` do not cover the following types: code. The mappings for `StructureDefinition.fhirVersion` do not cover the following types based on type expansion: value. A StructureDefinition does not need to specify the target it applies to as StructureDefinitions will often be valid across multiple versions of FHIR. FHIR tooling can determine whether a StructureDefinition is consistent with a particular StructureDefinition if desired. StructureDefinition.mapping (mapping) is related to StructureDefinition.mapping Element `StructureDefinition.mapping` is mapped to FHIR STU3 element `DataElement.mapping` as `Equivalent`. Element `StructureDefinition.mapping` is mapped to FHIR STU3 element `StructureDefinition.mapping` as `Equivalent`. StructureDefinition.mapping.identity (identity) is equivalent to StructureDefinition.mapping.identity Element `StructureDefinition.mapping.identity` is mapped to FHIR STU3 element `DataElement.mapping.identity` as `Equivalent`. Element `StructureDefinition.mapping.identity` is mapped to FHIR STU3 element `StructureDefinition.mapping.identity` as `Equivalent`. The specification is described once, with general comments, and then specific mappings are made that reference this declaration. StructureDefinition.mapping.uri (uri) is equivalent to StructureDefinition.mapping.uri Element `StructureDefinition.mapping.uri` is mapped to FHIR STU3 element `DataElement.mapping.uri` as `Equivalent`. Element `StructureDefinition.mapping.uri` is mapped to FHIR STU3 element `StructureDefinition.mapping.uri` as `Equivalent`. A formal identity for the specification being mapped to helps with identifying maps consistently. StructureDefinition.mapping.name (name) is equivalent to StructureDefinition.mapping.name Element `StructureDefinition.mapping.name` is mapped to FHIR STU3 element `DataElement.mapping.name` as `Equivalent`. Element `StructureDefinition.mapping.name` is mapped to FHIR STU3 element `StructureDefinition.mapping.name` as `Equivalent`. StructureDefinition.mapping.comment (comment) is equivalent to StructureDefinition.mapping.comment Element `StructureDefinition.mapping.comment` is mapped to FHIR STU3 element `DataElement.mapping.comment` as `Equivalent`. Element `StructureDefinition.mapping.comment` is mapped to FHIR STU3 element `StructureDefinition.mapping.comment` as `Equivalent`. StructureDefinition.kind (kind) is equivalent to StructureDefinition.kind Element `StructureDefinition.kind` is mapped to FHIR STU3 element `StructureDefinition.kind` as `Equivalent`. StructureDefinition.abstract (abstract) is equivalent to StructureDefinition.abstract Element `StructureDefinition.abstract` is mapped to FHIR STU3 element `StructureDefinition.abstract` as `Equivalent`. Abstract Resources cannot be instantiated - a concrete sub-type must be used. Abstract datatypes and extensions cannot be used in an instance. For logical models, the exact implication of "abstract" will rest with the author, depending how the logical model is used. Flagging a constraint structure as abstract conveys design intent but makes no difference to how the structure definition is handled. Note that inline declared elements that are given the type "Element" in the StructureDefinition, but have children described, are anonymous concrete types that specialize Element. StructureDefinition.context (context) is related to StructureDefinition.context Element `StructureDefinition.context` is mapped to FHIR STU3 element `StructureDefinition.context` as `Equivalent`. StructureDefinition.context.expression (expression) is equivalent to StructureDefinition.contextType Element `StructureDefinition.context.expression` is mapped to FHIR STU3 element `StructureDefinition.contextType` as `Equivalent`. StructureDefinition.contextInvariant (contextInvariant) is equivalent to StructureDefinition.contextInvariant Element `StructureDefinition.contextInvariant` is mapped to FHIR STU3 element `StructureDefinition.contextInvariant` as `Equivalent`. The rules are only evaluated when the extension is present. When evaluating the invariant, the FHIRPath focus is the element that holds the extension, and %extension refers to the extension itself. StructureDefinition.type (type) is equivalent to StructureDefinition.type Element `StructureDefinition.type` is mapped to FHIR STU3 element `StructureDefinition.type` as `SourceIsNarrowerThanTarget`. Note that in the case of constraints, the type could be determined by chasing through the baseDefinition references until a type defining structure (derivation = specialization) is reached, or by looking at the path of the first element in the snapshot - if present - but providing the type directly makes for simpler tooling and indexing. The type must match the elements defined in the differential and the snapshot. For all FHIR defined types, the path name of the element will start with the type name. For logical models, where the type SHALL be a fully specified URL, the type name SHOULD start with the final path segment of the type URL where required. E.g. If the type was "http://example.org/fhir/MyLogicalModelType", the type name should start with 'MyLogicalModelType'. StructureDefinition.baseDefinition (baseDefinition) is equivalent to StructureDefinition.baseDefinition Element `StructureDefinition.baseDefinition` is mapped to FHIR STU3 element `StructureDefinition.baseDefinition` as `Equivalent`. If differential constraints are specified in this structure, they are applied to the base in a "differential" fashion. If there is no base, then the differential constraints cannot be provided (snapshot only). Differential structures are useful for the editing perspective, and snapshot structures are suitable for operational use. The FHIR Project provides a number of tools/services to populate snapshots from differential constraints. Logical Models have a base of "Base", "Element" or another logical model. StructureDefinition.derivation (derivation) is equivalent to StructureDefinition.derivation Element `StructureDefinition.derivation` is mapped to FHIR STU3 element `StructureDefinition.derivation` as `Equivalent`. If the definition is a specialization, then it adds to the differential new elements and optionally additional rules to an existing concrete type, and the snapshot includes the inherited elements and rules. If the definition is a constraint, then it cannot define new elements, it can only make new rules about existing content (see [Profiling Resources](https://hl7.org/fhir/profiling..html#resources)). StructureDefinition.snapshot (snapshot) is related to StructureDefinition.snapshot Element `StructureDefinition.snapshot` is mapped to FHIR STU3 element `StructureDefinition.snapshot` as `Equivalent`. StructureDefinition.snapshot.element (element) is equivalent to StructureDefinition.snapshot.element Element `StructureDefinition.snapshot.element` is mapped to FHIR STU3 element `StructureDefinition.snapshot.element` as `Equivalent`. StructureDefinition.differential (differential) is related to StructureDefinition.differential Element `StructureDefinition.differential` is mapped to FHIR STU3 element `StructureDefinition.differential` as `Equivalent`. StructureDefinition.differential.element (element) is equivalent to StructureDefinition.differential.element Element `StructureDefinition.differential.element` is mapped to FHIR STU3 element `DataElement.element` as `Equivalent`. Element `StructureDefinition.differential.element` is mapped to FHIR STU3 element `StructureDefinition.differential.element` as `Equivalent`. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/StructureDefinition|5.0.0 to R5: Contact details for the publisher additional typesversion: 0.1.0) Source Code Relationship Target Code Comment StructureDefinition.contact (contact) maps to wider concept Extension (R5: Contact details for the publisher additional types) Element `StructureDefinition.contact` is mapped to FHIR STU3 element `DataElement.contact` as `SourceIsBroaderThanTarget`. Element `StructureDefinition.contact` is mapped to FHIR STU3 element `StructureDefinition.contact` as `SourceIsBroaderThanTarget`. The mappings for `StructureDefinition.contact` do not cover the following types: ContactDetail. The mappings for `StructureDefinition.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. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/StructureDefinition|5.0.0 to R5: fhirVersion additional typesversion: 0.1.0) Source Code Relationship Target Code Comment StructureDefinition.fhirVersion (fhirVersion) maps to wider concept Extension (R5: fhirVersion additional types) Element `StructureDefinition.fhirVersion` is mapped to FHIR STU3 element `StructureDefinition.fhirVersion` as `SourceIsBroaderThanTarget`. The mappings for `StructureDefinition.fhirVersion` do not cover the following types: code. The mappings for `StructureDefinition.fhirVersion` do not cover the following types based on type expansion: value. A StructureDefinition does not need to specify the target it applies to as StructureDefinitions will often be valid across multiple versions of FHIR. FHIR tooling can determine whether a StructureDefinition is consistent with a particular StructureDefinition if desired. Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/StructureDefinition|5.0.0 to R5: fhirpath | element | extension (new)version: 0.1.0) Source Code Relationship Target Code Comment StructureDefinition.context.type (type) maps to wider concept Extension (R5: fhirpath | element | extension (new)) Element `StructureDefinition.context.type` has a context of DataElement based on following the parent source element upwards and mapping to `DataElement`. Element `StructureDefinition.context.type` has a context of StructureDefinition.context based on following the parent source element upwards and mapping to `StructureDefinition`. Element `StructureDefinition.context.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Cross-version mapping for FHIR R5 StructureDefinition to FHIR STU3 DataElement
This ConceptMap represents cross-version mappings for elements from a FHIR R5 StructureDefinition to FHIR STU3.
Element `StructureDefinition.meta` is mapped to FHIR STU3 element `DataElement.meta` as `Equivalent`. Element `StructureDefinition.meta` is mapped to FHIR STU3 element `StructureDefinition.meta` as `Equivalent`.
Element `StructureDefinition.implicitRules` is mapped to FHIR STU3 element `DataElement.implicitRules` as `Equivalent`. Element `StructureDefinition.implicitRules` is mapped to FHIR STU3 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. 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 `StructureDefinition.language` is mapped to FHIR STU3 element `DataElement.language` as `Equivalent`. Element `StructureDefinition.language` is mapped to FHIR STU3 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 `StructureDefinition.text` is mapped to FHIR STU3 element `DataElement.text` as `Equivalent`. Element `StructureDefinition.text` is mapped to FHIR STU3 element `StructureDefinition.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 `StructureDefinition.contained` is mapped to FHIR STU3 element `DataElement.contained` as `SourceIsBroaderThanTarget`. Element `StructureDefinition.contained` is mapped to FHIR STU3 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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
Element `StructureDefinition.url` is mapped to FHIR STU3 element `DataElement.url` as `Equivalent`. Element `StructureDefinition.url` is mapped to FHIR STU3 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. 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 `StructureDefinition.identifier` is mapped to FHIR STU3 element `DataElement.identifier` as `Equivalent`. Element `StructureDefinition.identifier` is mapped to FHIR STU3 element `StructureDefinition.identifier` as `Equivalent`. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this structure definition outside of FHIR, where it is not possible to use the logical URI.
Element `StructureDefinition.version` is mapped to FHIR STU3 element `DataElement.version` as `Equivalent`. Element `StructureDefinition.version` is mapped to FHIR STU3 element `StructureDefinition.version` as `Equivalent`. There may be different structure definition 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 structure definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format).
Element `StructureDefinition.name` is mapped to FHIR STU3 element `DataElement.name` as `Equivalent`. Element `StructureDefinition.name` is mapped to FHIR STU3 element `StructureDefinition.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.Some Examples: * O2SatObservation * PresentationReport * Immunization2 * AcmeAdmissionRecordOld.
Element `StructureDefinition.title` is mapped to FHIR STU3 element `DataElement.title` as `Equivalent`. Element `StructureDefinition.title` is mapped to FHIR STU3 element `StructureDefinition.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.Applications don't have to use this name but can always fall back to it. The title also corresponds to the label for the root element.
Element `StructureDefinition.status` is mapped to FHIR STU3 element `DataElement.status` as `Equivalent`. Element `StructureDefinition.status` is mapped to FHIR STU3 element `StructureDefinition.status` as `Equivalent`. Allows filtering of structure definitions 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 `StructureDefinition.experimental` is mapped to FHIR STU3 element `DataElement.experimental` as `Equivalent`. Element `StructureDefinition.experimental` is mapped to FHIR STU3 element `StructureDefinition.experimental` as `Equivalent`. Allows filtering of structure definitions that are appropriate for use versus not.
Element `StructureDefinition.date` is mapped to FHIR STU3 element `DataElement.date` as `Equivalent`. Element `StructureDefinition.date` is mapped to FHIR STU3 element `StructureDefinition.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 structure definition. 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 `StructureDefinition.publisher` is mapped to FHIR STU3 element `DataElement.publisher` as `Equivalent`. Element `StructureDefinition.publisher` is mapped to FHIR STU3 element `StructureDefinition.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the structure definition is the organization or individual primarily responsible for the maintenance and upkeep of the structure definition. 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 structure definition. This item SHOULD be populated unless the information is available from context.
Element `StructureDefinition.contact` is mapped to FHIR STU3 element `DataElement.contact` as `SourceIsBroaderThanTarget`. Element `StructureDefinition.contact` is mapped to FHIR STU3 element `StructureDefinition.contact` as `SourceIsBroaderThanTarget`. The mappings for `StructureDefinition.contact` do not cover the following types: ContactDetail. The mappings for `StructureDefinition.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. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
Element `StructureDefinition.useContext` is mapped to FHIR STU3 element `DataElement.useContext` as `Equivalent`. Element `StructureDefinition.useContext` is mapped to FHIR STU3 element `StructureDefinition.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
Element `StructureDefinition.jurisdiction` is mapped to FHIR STU3 element `DataElement.jurisdiction` as `Equivalent`. Element `StructureDefinition.jurisdiction` is mapped to FHIR STU3 element `StructureDefinition.jurisdiction` as `Equivalent`. Element `StructureDefinition.jurisdiction` has been flagged as deprecated. It may be possible for the structure definition 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 `StructureDefinition.copyright` is mapped to FHIR STU3 element `DataElement.copyright` as `Equivalent`. Element `StructureDefinition.copyright` is mapped to FHIR STU3 element `StructureDefinition.copyright` as `Equivalent`. ...
Element `StructureDefinition.mapping` is mapped to FHIR STU3 element `DataElement.mapping` as `Equivalent`. Element `StructureDefinition.mapping` is mapped to FHIR STU3 element `StructureDefinition.mapping` as `Equivalent`.
Element `StructureDefinition.mapping.identity` is mapped to FHIR STU3 element `DataElement.mapping.identity` as `Equivalent`. Element `StructureDefinition.mapping.identity` is mapped to FHIR STU3 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 `StructureDefinition.mapping.uri` is mapped to FHIR STU3 element `DataElement.mapping.uri` as `Equivalent`. Element `StructureDefinition.mapping.uri` is mapped to FHIR STU3 element `StructureDefinition.mapping.uri` as `Equivalent`. A formal identity for the specification being mapped to helps with identifying maps consistently.
Element `StructureDefinition.mapping.name` is mapped to FHIR STU3 element `DataElement.mapping.name` as `Equivalent`. Element `StructureDefinition.mapping.name` is mapped to FHIR STU3 element `StructureDefinition.mapping.name` as `Equivalent`.
Element `StructureDefinition.mapping.comment` is mapped to FHIR STU3 element `DataElement.mapping.comment` as `Equivalent`. Element `StructureDefinition.mapping.comment` is mapped to FHIR STU3 element `StructureDefinition.mapping.comment` as `Equivalent`.
Element `StructureDefinition.differential.element` is mapped to FHIR STU3 element `DataElement.element` as `Equivalent`. Element `StructureDefinition.differential.element` is mapped to FHIR STU3 element `StructureDefinition.differential.element` as `Equivalent`.
Element `StructureDefinition.description` is mapped to FHIR STU3 element `StructureDefinition.description` as `Equivalent`. This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the structure definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the structure definition is presumed to be the predominant language in the place the structure definition was created).
Element `StructureDefinition.purpose` is mapped to FHIR STU3 element `StructureDefinition.purpose` as `Equivalent`. This element does not describe the usage of the structure definition. 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 structure definition.
Element `StructureDefinition.keyword` is mapped to FHIR STU3 element `StructureDefinition.keyword` as `Equivalent`. Element `StructureDefinition.keyword` has been flagged as deprecated. Note that this element is deprecated. Use the [http://hl7.org/fhir/StructureDefinition/artifact-topic](http://hl7.org/fhir/extensions/StructureDefinition-artifact-topic.html) extension instead.
Element `StructureDefinition.fhirVersion` is mapped to FHIR STU3 element `StructureDefinition.fhirVersion` as `SourceIsBroaderThanTarget`. The mappings for `StructureDefinition.fhirVersion` do not cover the following types: code. The mappings for `StructureDefinition.fhirVersion` do not cover the following types based on type expansion: value. A StructureDefinition does not need to specify the target it applies to as StructureDefinitions will often be valid across multiple versions of FHIR. FHIR tooling can determine whether a StructureDefinition is consistent with a particular StructureDefinition if desired.
Element `StructureDefinition.kind` is mapped to FHIR STU3 element `StructureDefinition.kind` as `Equivalent`.
Element `StructureDefinition.abstract` is mapped to FHIR STU3 element `StructureDefinition.abstract` as `Equivalent`. Abstract Resources cannot be instantiated - a concrete sub-type must be used. Abstract datatypes and extensions cannot be used in an instance. For logical models, the exact implication of "abstract" will rest with the author, depending how the logical model is used. Flagging a constraint structure as abstract conveys design intent but makes no difference to how the structure definition is handled. Note that inline declared elements that are given the type "Element" in the StructureDefinition, but have children described, are anonymous concrete types that specialize Element.
Element `StructureDefinition.context` is mapped to FHIR STU3 element `StructureDefinition.context` as `Equivalent`.
Element `StructureDefinition.context.expression` is mapped to FHIR STU3 element `StructureDefinition.contextType` as `Equivalent`.
Element `StructureDefinition.contextInvariant` is mapped to FHIR STU3 element `StructureDefinition.contextInvariant` as `Equivalent`. The rules are only evaluated when the extension is present. When evaluating the invariant, the FHIRPath focus is the element that holds the extension, and %extension refers to the extension itself.
Element `StructureDefinition.type` is mapped to FHIR STU3 element `StructureDefinition.type` as `SourceIsNarrowerThanTarget`. Note that in the case of constraints, the type could be determined by chasing through the baseDefinition references until a type defining structure (derivation = specialization) is reached, or by looking at the path of the first element in the snapshot - if present - but providing the type directly makes for simpler tooling and indexing. The type must match the elements defined in the differential and the snapshot. For all FHIR defined types, the path name of the element will start with the type name. For logical models, where the type SHALL be a fully specified URL, the type name SHOULD start with the final path segment of the type URL where required. E.g. If the type was "http://example.org/fhir/MyLogicalModelType", the type name should start with 'MyLogicalModelType'.
Element `StructureDefinition.baseDefinition` is mapped to FHIR STU3 element `StructureDefinition.baseDefinition` as `Equivalent`. If differential constraints are specified in this structure, they are applied to the base in a "differential" fashion. If there is no base, then the differential constraints cannot be provided (snapshot only). Differential structures are useful for the editing perspective, and snapshot structures are suitable for operational use. The FHIR Project provides a number of tools/services to populate snapshots from differential constraints. Logical Models have a base of "Base", "Element" or another logical model.
Element `StructureDefinition.derivation` is mapped to FHIR STU3 element `StructureDefinition.derivation` as `Equivalent`. If the definition is a specialization, then it adds to the differential new elements and optionally additional rules to an existing concrete type, and the snapshot includes the inherited elements and rules. If the definition is a constraint, then it cannot define new elements, it can only make new rules about existing content (see [Profiling Resources](https://hl7.org/fhir/profiling..html#resources)).
Element `StructureDefinition.snapshot` is mapped to FHIR STU3 element `StructureDefinition.snapshot` as `Equivalent`.
Element `StructureDefinition.snapshot.element` is mapped to FHIR STU3 element `StructureDefinition.snapshot.element` as `Equivalent`.
Element `StructureDefinition.differential` is mapped to FHIR STU3 element `StructureDefinition.differential` as `Equivalent`.
Element `StructureDefinition.context.type` has a context of DataElement based on following the parent source element upwards and mapping to `DataElement`. Element `StructureDefinition.context.type` has a context of StructureDefinition.context based on following the parent source element upwards and mapping to `StructureDefinition`. Element `StructureDefinition.context.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).