FHIR © HL7.org  |  FHIRsmith 4.0.1  |  Server Home  |  XIG Home  |  XIG Stats  | 

FHIR IG analytics

Packagehl7.fhir.uv.xver-r4b.r4
Resource TypeConceptMap
IdConceptMap-R4B-StructureDefinition-element-map-to-R4.json
FHIR VersionR4
Sourcehttp://hl7.org/fhir/uv/xver-r4b.r4/0.1.0/ConceptMap-R4B-StructureDefinition-element-map-to-R4.html
URLhttp://hl7.org/fhir/uv/xver/ConceptMap/R4B-StructureDefinition-element-map-to-R4
Version0.1.0
Statusactive
Date2026-03-17T16:03:46.2113684-05:00
NameR4BStructureDefinitionElementMapToR4
TitleCross-version mapping for FHIR R4B StructureDefinition to FHIR R4 StructureDefinition
Realmuv
Authorityhl7
DescriptionThis ConceptMap represents cross-version mappings for elements from a FHIR R4B StructureDefinition to FHIR R4.

Resources that use this resource

No resources found


Resources that this resource uses

StructureDefinition
hl7.fhir.uv.xver-r4b.r4.r4b#0.0.1-snapshot-2extension-StructureDefinition.fhirVersionCross-version Extension for R4B.StructureDefinition.fhirVersion for use in FHIR R4

Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ConceptMap R4B-StructureDefinition-element-map-to-R4

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


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

Source CodeRelationshipTarget CodeComment
StructureDefinition.meta (meta)is equivalent toStructureDefinition.metaElement `StructureDefinition.meta` is mapped to FHIR R4 element `StructureDefinition.meta` as `Equivalent`.
StructureDefinition.implicitRules (implicitRules)is equivalent toStructureDefinition.implicitRulesElement `StructureDefinition.implicitRules` is mapped to FHIR R4 element `StructureDefinition.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
StructureDefinition.language (language)is equivalent toStructureDefinition.languageElement `StructureDefinition.language` is mapped to FHIR R4 element `StructureDefinition.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
StructureDefinition.text (text)is equivalent toStructureDefinition.textElement `StructureDefinition.text` is mapped to FHIR R4 element `StructureDefinition.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
StructureDefinition.contained (contained)is equivalent toStructureDefinition.containedElement `StructureDefinition.contained` is mapped to FHIR R4 element `StructureDefinition.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.
StructureDefinition.url (url)is equivalent toStructureDefinition.urlElement `StructureDefinition.url` is mapped to FHIR R4 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 toStructureDefinition.identifierElement `StructureDefinition.identifier` is mapped to FHIR R4 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 toStructureDefinition.versionElement `StructureDefinition.version` is mapped to FHIR R4 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].
StructureDefinition.name (name)is equivalent toStructureDefinition.nameElement `StructureDefinition.name` is mapped to FHIR R4 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 toStructureDefinition.titleElement `StructureDefinition.title` is mapped to FHIR R4 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 toStructureDefinition.statusElement `StructureDefinition.status` is mapped to FHIR R4 element `StructureDefinition.status` as `Equivalent`. Allows filtering of structure definitions that are appropriate for use versus not.
StructureDefinition.experimental (experimental)is equivalent toStructureDefinition.experimentalElement `StructureDefinition.experimental` is mapped to FHIR R4 element `StructureDefinition.experimental` as `Equivalent`. Allows filtering of structure definitions that are appropriate for use versus not.
StructureDefinition.date (date)is equivalent toStructureDefinition.dateElement `StructureDefinition.date` is mapped to FHIR R4 element `StructureDefinition.date` as `Equivalent`. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the structure definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
StructureDefinition.publisher (publisher)is equivalent toStructureDefinition.publisherElement `StructureDefinition.publisher` is mapped to FHIR R4 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 equivalent toStructureDefinition.contactElement `StructureDefinition.contact` is mapped to FHIR R4 element `StructureDefinition.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.
StructureDefinition.description (description)is equivalent toStructureDefinition.descriptionElement `StructureDefinition.description` is mapped to FHIR R4 element `StructureDefinition.description` as `Equivalent`. This description can be used to capture details such as why the structure definition was built, 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 toStructureDefinition.useContextElement `StructureDefinition.useContext` is mapped to FHIR R4 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 toStructureDefinition.jurisdictionElement `StructureDefinition.jurisdiction` is mapped to FHIR R4 element `StructureDefinition.jurisdiction` as `Equivalent`. It may be possible for the structure definition to be used in jurisdictions other than those for which it was originally designed or intended.
StructureDefinition.purpose (purpose)is equivalent toStructureDefinition.purposeElement `StructureDefinition.purpose` is mapped to FHIR R4 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 toStructureDefinition.copyrightElement `StructureDefinition.copyright` is mapped to FHIR R4 element `StructureDefinition.copyright` as `Equivalent`.
StructureDefinition.keyword (keyword)is equivalent toStructureDefinition.keywordElement `StructureDefinition.keyword` is mapped to FHIR R4 element `StructureDefinition.keyword` as `Equivalent`.
StructureDefinition.fhirVersion (fhirVersion)maps to wider conceptStructureDefinition.fhirVersionElement `StructureDefinition.fhirVersion` is mapped to FHIR R4 element `StructureDefinition.fhirVersion` as `SourceIsBroaderThanTarget`. 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)maps to wider conceptStructureDefinition.mappingElement `StructureDefinition.mapping` is mapped to FHIR R4 element `StructureDefinition.mapping` as `Equivalent`.
StructureDefinition.mapping.identity (identity)is equivalent toStructureDefinition.mapping.identityElement `StructureDefinition.mapping.identity` is mapped to FHIR R4 element `StructureDefinition.mapping.identity` as `Equivalent`. The specification is described once, with general comments, and then specific mappings are made that reference this declaration.
StructureDefinition.mapping.uri (uri)is equivalent toStructureDefinition.mapping.uriElement `StructureDefinition.mapping.uri` is mapped to FHIR R4 element `StructureDefinition.mapping.uri` as `Equivalent`. A formal identity for the specification being mapped to helps with identifying maps consistently.
StructureDefinition.mapping.name (name)is equivalent toStructureDefinition.mapping.nameElement `StructureDefinition.mapping.name` is mapped to FHIR R4 element `StructureDefinition.mapping.name` as `Equivalent`.
StructureDefinition.mapping.comment (comment)is equivalent toStructureDefinition.mapping.commentElement `StructureDefinition.mapping.comment` is mapped to FHIR R4 element `StructureDefinition.mapping.comment` as `Equivalent`.
StructureDefinition.kind (kind)is equivalent toStructureDefinition.kindElement `StructureDefinition.kind` is mapped to FHIR R4 element `StructureDefinition.kind` as `Equivalent`.
StructureDefinition.abstract (abstract)is equivalent toStructureDefinition.abstractElement `StructureDefinition.abstract` is mapped to FHIR R4 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)maps to wider conceptStructureDefinition.contextElement `StructureDefinition.context` is mapped to FHIR R4 element `StructureDefinition.context` as `Equivalent`.
StructureDefinition.context.type (type)is equivalent toStructureDefinition.context.typeElement `StructureDefinition.context.type` is mapped to FHIR R4 element `StructureDefinition.context.type` as `Equivalent`.
StructureDefinition.context.expression (expression)is equivalent toStructureDefinition.context.expressionElement `StructureDefinition.context.expression` is mapped to FHIR R4 element `StructureDefinition.context.expression` as `Equivalent`.
StructureDefinition.contextInvariant (contextInvariant)is equivalent toStructureDefinition.contextInvariantElement `StructureDefinition.contextInvariant` is mapped to FHIR R4 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 toStructureDefinition.typeElement `StructureDefinition.type` is mapped to FHIR R4 element `StructureDefinition.type` as `Equivalent`. Note that in the case of constraints, the type could be determined by chasing through the baseDefinition references until a concrete 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 is a URL, the type name SHOULD start with the tail of the type URL where required.
StructureDefinition.baseDefinition (baseDefinition)is equivalent toStructureDefinition.baseDefinitionElement `StructureDefinition.baseDefinition` is mapped to FHIR R4 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 "Element" or another logical model.
StructureDefinition.derivation (derivation)is equivalent toStructureDefinition.derivationElement `StructureDefinition.derivation` is mapped to FHIR R4 element `StructureDefinition.derivation` as `Equivalent`. If the definition is a specialization, then it adds new elements in the differential, and the snapshot includes the inherited elements. 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)maps to wider conceptStructureDefinition.snapshotElement `StructureDefinition.snapshot` is mapped to FHIR R4 element `StructureDefinition.snapshot` as `Equivalent`.
StructureDefinition.snapshot.element (element)is equivalent toStructureDefinition.snapshot.elementElement `StructureDefinition.snapshot.element` is mapped to FHIR R4 element `StructureDefinition.snapshot.element` as `Equivalent`.
StructureDefinition.differential (differential)maps to wider conceptStructureDefinition.differentialElement `StructureDefinition.differential` is mapped to FHIR R4 element `StructureDefinition.differential` as `Equivalent`.
StructureDefinition.differential.element (element)is equivalent toStructureDefinition.differential.elementElement `StructureDefinition.differential.element` is mapped to FHIR R4 element `StructureDefinition.differential.element` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/StructureDefinition|4.3.0 to R4B: fhirVersionversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
StructureDefinition.fhirVersion (fhirVersion)is equivalent toExtension (R4B: fhirVersion)Element `StructureDefinition.fhirVersion` is mapped to FHIR R4 element `StructureDefinition.fhirVersion` as `SourceIsBroaderThanTarget`. 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.

Source1

{
  "resourceType": "ConceptMap",
  "id": "R4B-StructureDefinition-element-map-to-R4",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "fhir"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 0,
      "_valueInteger": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r4"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r4"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R4B-StructureDefinition-element-map-to-R4",
  "version": "0.1.0",
  "name": "R4BStructureDefinitionElementMapToR4",
  "title": "Cross-version mapping for FHIR R4B StructureDefinition to FHIR R4 StructureDefinition",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:03:46.2113684-05:00",
  "contact": [
    {
      "name": "FHIR Infrastructure",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/fiwg"
        }
      ]
    }
  ],
  "description": "This ConceptMap represents cross-version mappings for elements from a FHIR R4B StructureDefinition to FHIR R4.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceCanonical": "http://hl7.org/fhir/4.3",
  "targetUri": "http://hl7.org/fhir/4.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/StructureDefinition",
      "sourceVersion": "4.3.0",
      "target": "http://hl7.org/fhir/StructureDefinition/StructureDefinition",
      "targetVersion": "4.0.1",
      "element": [
        {
          "code": "StructureDefinition.meta",
          "display": "meta",
          "target": [
            {
              "code": "StructureDefinition.meta",
              "display": "StructureDefinition.meta",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.meta` is mapped to FHIR R4 element `StructureDefinition.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "StructureDefinition.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "StructureDefinition.implicitRules",
              "display": "StructureDefinition.implicitRules",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.implicitRules` is mapped to FHIR R4 element `StructureDefinition.implicitRules` as `Equivalent`.\nAsserting 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 it's narrative along with other profiles, value sets, etc."
            }
          ]
        },
        {
          "code": "StructureDefinition.language",
          "display": "language",
          "target": [
            {
              "code": "StructureDefinition.language",
              "display": "StructureDefinition.language",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.language` is mapped to FHIR R4 element `StructureDefinition.language` as `Equivalent`.\nLanguage 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)."
            }
          ]
        },
        {
          "code": "StructureDefinition.text",
          "display": "text",
          "target": [
            {
              "code": "StructureDefinition.text",
              "display": "StructureDefinition.text",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.text` is mapped to FHIR R4 element `StructureDefinition.text` as `Equivalent`.\nContained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a \"text blob\" or where text is additionally entered raw or narrated and encoded information is added later."
            }
          ]
        },
        {
          "code": "StructureDefinition.contained",
          "display": "contained",
          "target": [
            {
              "code": "StructureDefinition.contained",
              "display": "StructureDefinition.contained",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.contained` is mapped to FHIR R4 element `StructureDefinition.contained` as `Equivalent`.\nThis 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."
            }
          ]
        },
        {
          "code": "StructureDefinition.url",
          "display": "url",
          "target": [
            {
              "code": "StructureDefinition.url",
              "display": "StructureDefinition.url",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.url` is mapped to FHIR R4 element `StructureDefinition.url` as `Equivalent`.\nCan 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.\n\nThe 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). \n\nIn 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."
            }
          ]
        },
        {
          "code": "StructureDefinition.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "StructureDefinition.identifier",
              "display": "StructureDefinition.identifier",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.identifier` is mapped to FHIR R4 element `StructureDefinition.identifier` as `Equivalent`.\nTypically, 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."
            }
          ]
        },
        {
          "code": "StructureDefinition.version",
          "display": "version",
          "target": [
            {
              "code": "StructureDefinition.version",
              "display": "StructureDefinition.version",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.version` is mapped to FHIR R4 element `StructureDefinition.version` as `Equivalent`.\nThere 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]."
            }
          ]
        },
        {
          "code": "StructureDefinition.name",
          "display": "name",
          "target": [
            {
              "code": "StructureDefinition.name",
              "display": "StructureDefinition.name",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.name` is mapped to FHIR R4 element `StructureDefinition.name` as `Equivalent`.\nThe 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: \n\n* O2SatObservation\n* PresentationReport\n* Immunization2\n* AcmeAdmissionRecordOld."
            }
          ]
        },
        {
          "code": "StructureDefinition.title",
          "display": "title",
          "target": [
            {
              "code": "StructureDefinition.title",
              "display": "StructureDefinition.title",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.title` is mapped to FHIR R4 element `StructureDefinition.title` as `Equivalent`.\nThis 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."
            }
          ]
        },
        {
          "code": "StructureDefinition.status",
          "display": "status",
          "target": [
            {
              "code": "StructureDefinition.status",
              "display": "StructureDefinition.status",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.status` is mapped to FHIR R4 element `StructureDefinition.status` as `Equivalent`.\nAllows filtering of structure definitions that are appropriate for use versus not."
            }
          ]
        },
        {
          "code": "StructureDefinition.experimental",
          "display": "experimental",
          "target": [
            {
              "code": "StructureDefinition.experimental",
              "display": "StructureDefinition.experimental",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.experimental` is mapped to FHIR R4 element `StructureDefinition.experimental` as `Equivalent`.\nAllows filtering of structure definitions that are appropriate for use versus not."
            }
          ]
        },
        {
          "code": "StructureDefinition.date",
          "display": "date",
          "target": [
            {
              "code": "StructureDefinition.date",
              "display": "StructureDefinition.date",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.date` is mapped to FHIR R4 element `StructureDefinition.date` as `Equivalent`.\nNote 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."
            }
          ]
        },
        {
          "code": "StructureDefinition.publisher",
          "display": "publisher",
          "target": [
            {
              "code": "StructureDefinition.publisher",
              "display": "StructureDefinition.publisher",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.publisher` is mapped to FHIR R4 element `StructureDefinition.publisher` as `Equivalent`.\nUsually 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."
            }
          ]
        },
        {
          "code": "StructureDefinition.contact",
          "display": "contact",
          "target": [
            {
              "code": "StructureDefinition.contact",
              "display": "StructureDefinition.contact",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.contact` is mapped to FHIR R4 element `StructureDefinition.contact` as `Equivalent`.\nMay be a web site, an email address, a telephone number, etc."
            }
          ]
        },
        {
          "code": "StructureDefinition.description",
          "display": "description",
          "target": [
            {
              "code": "StructureDefinition.description",
              "display": "StructureDefinition.description",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.description` is mapped to FHIR R4 element `StructureDefinition.description` as `Equivalent`.\nThis description can be used to capture details such as why the structure definition was built, 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)."
            }
          ]
        },
        {
          "code": "StructureDefinition.useContext",
          "display": "useContext",
          "target": [
            {
              "code": "StructureDefinition.useContext",
              "display": "StructureDefinition.useContext",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.useContext` is mapped to FHIR R4 element `StructureDefinition.useContext` as `Equivalent`.\nWhen multiple useContexts are specified, there is no expectation that all or any of the contexts apply."
            }
          ]
        },
        {
          "code": "StructureDefinition.jurisdiction",
          "display": "jurisdiction",
          "target": [
            {
              "code": "StructureDefinition.jurisdiction",
              "display": "StructureDefinition.jurisdiction",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.jurisdiction` is mapped to FHIR R4 element `StructureDefinition.jurisdiction` as `Equivalent`.\nIt may be possible for the structure definition to be used in jurisdictions other than those for which it was originally designed or intended."
            }
          ]
        },
        {
          "code": "StructureDefinition.purpose",
          "display": "purpose",
          "target": [
            {
              "code": "StructureDefinition.purpose",
              "display": "StructureDefinition.purpose",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.purpose` is mapped to FHIR R4 element `StructureDefinition.purpose` as `Equivalent`.\nThis 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."
            }
          ]
        },
        {
          "code": "StructureDefinition.copyright",
          "display": "copyright",
          "target": [
            {
              "code": "StructureDefinition.copyright",
              "display": "StructureDefinition.copyright",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.copyright` is mapped to FHIR R4 element `StructureDefinition.copyright` as `Equivalent`."
            }
          ]
        },
        {
          "code": "StructureDefinition.keyword",
          "display": "keyword",
          "target": [
            {
              "code": "StructureDefinition.keyword",
              "display": "StructureDefinition.keyword",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.keyword` is mapped to FHIR R4 element `StructureDefinition.keyword` as `Equivalent`."
            }
          ]
        },
        {
          "code": "StructureDefinition.fhirVersion",
          "display": "fhirVersion",
          "target": [
            {
              "code": "StructureDefinition.fhirVersion",
              "display": "StructureDefinition.fhirVersion",
              "equivalence": "wider",
              "comment": "Element `StructureDefinition.fhirVersion` is mapped to FHIR R4 element `StructureDefinition.fhirVersion` as `SourceIsBroaderThanTarget`.\nA 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."
            }
          ]
        },
        {
          "code": "StructureDefinition.mapping",
          "display": "mapping",
          "target": [
            {
              "code": "StructureDefinition.mapping",
              "display": "StructureDefinition.mapping",
              "equivalence": "wider",
              "comment": "Element `StructureDefinition.mapping` is mapped to FHIR R4 element `StructureDefinition.mapping` as `Equivalent`."
            }
          ]
        },
        {
          "code": "StructureDefinition.mapping.identity",
          "display": "identity",
          "target": [
            {
              "code": "StructureDefinition.mapping.identity",
              "display": "StructureDefinition.mapping.identity",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.mapping.identity` is mapped to FHIR R4 element `StructureDefinition.mapping.identity` as `Equivalent`.\nThe specification is described once, with general comments, and then specific mappings are made that reference this declaration."
            }
          ]
        },
        {
          "code": "StructureDefinition.mapping.uri",
          "display": "uri",
          "target": [
            {
              "code": "StructureDefinition.mapping.uri",
              "display": "StructureDefinition.mapping.uri",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.mapping.uri` is mapped to FHIR R4 element `StructureDefinition.mapping.uri` as `Equivalent`.\nA formal identity for the specification being mapped to helps with identifying maps consistently."
            }
          ]
        },
        {
          "code": "StructureDefinition.mapping.name",
          "display": "name",
          "target": [
            {
              "code": "StructureDefinition.mapping.name",
              "display": "StructureDefinition.mapping.name",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.mapping.name` is mapped to FHIR R4 element `StructureDefinition.mapping.name` as `Equivalent`."
            }
          ]
        },
        {
          "code": "StructureDefinition.mapping.comment",
          "display": "comment",
          "target": [
            {
              "code": "StructureDefinition.mapping.comment",
              "display": "StructureDefinition.mapping.comment",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.mapping.comment` is mapped to FHIR R4 element `StructureDefinition.mapping.comment` as `Equivalent`."
            }
          ]
        },
        {
          "code": "StructureDefinition.kind",
          "display": "kind",
          "target": [
            {
              "code": "StructureDefinition.kind",
              "display": "StructureDefinition.kind",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.kind` is mapped to FHIR R4 element `StructureDefinition.kind` as `Equivalent`."
            }
          ]
        },
        {
          "code": "StructureDefinition.abstract",
          "display": "abstract",
          "target": [
            {
              "code": "StructureDefinition.abstract",
              "display": "StructureDefinition.abstract",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.abstract` is mapped to FHIR R4 element `StructureDefinition.abstract` as `Equivalent`.\nAbstract 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."
            }
          ]
        },
        {
          "code": "StructureDefinition.context",
          "display": "context",
          "target": [
            {
              "code": "StructureDefinition.context",
              "display": "StructureDefinition.context",
              "equivalence": "wider",
              "comment": "Element `StructureDefinition.context` is mapped to FHIR R4 element `StructureDefinition.context` as `Equivalent`."
            }
          ]
        },
        {
          "code": "StructureDefinition.context.type",
          "display": "type",
          "target": [
            {
              "code": "StructureDefinition.context.type",
              "display": "StructureDefinition.context.type",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.context.type` is mapped to FHIR R4 element `StructureDefinition.context.type` as `Equivalent`."
            }
          ]
        },
        {
          "code": "StructureDefinition.context.expression",
          "display": "expression",
          "target": [
            {
              "code": "StructureDefinition.context.expression",
              "display": "StructureDefinition.context.expression",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.context.expression` is mapped to FHIR R4 element `StructureDefinition.context.expression` as `Equivalent`."
            }
          ]
        },
        {
          "code": "StructureDefinition.contextInvariant",
          "display": "contextInvariant",
          "target": [
            {
              "code": "StructureDefinition.contextInvariant",
              "display": "StructureDefinition.contextInvariant",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.contextInvariant` is mapped to FHIR R4 element `StructureDefinition.contextInvariant` as `Equivalent`.\nThe 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."
            }
          ]
        },
        {
          "code": "StructureDefinition.type",
          "display": "type",
          "target": [
            {
              "code": "StructureDefinition.type",
              "display": "StructureDefinition.type",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.type` is mapped to FHIR R4 element `StructureDefinition.type` as `Equivalent`.\nNote that in the case of constraints, the type could be determined by chasing through the baseDefinition references until a concrete 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. \n\nThe 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 is a URL, the type name SHOULD start with the tail of the type URL where required."
            }
          ]
        },
        {
          "code": "StructureDefinition.baseDefinition",
          "display": "baseDefinition",
          "target": [
            {
              "code": "StructureDefinition.baseDefinition",
              "display": "StructureDefinition.baseDefinition",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.baseDefinition` is mapped to FHIR R4 element `StructureDefinition.baseDefinition` as `Equivalent`.\nIf 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 \"Element\" or another logical model."
            }
          ]
        },
        {
          "code": "StructureDefinition.derivation",
          "display": "derivation",
          "target": [
            {
              "code": "StructureDefinition.derivation",
              "display": "StructureDefinition.derivation",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.derivation` is mapped to FHIR R4 element `StructureDefinition.derivation` as `Equivalent`.\nIf the definition is a specialization, then it adds new elements in the differential, and the snapshot includes the inherited elements.  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))."
            }
          ]
        },
        {
          "code": "StructureDefinition.snapshot",
          "display": "snapshot",
          "target": [
            {
              "code": "StructureDefinition.snapshot",
              "display": "StructureDefinition.snapshot",
              "equivalence": "wider",
              "comment": "Element `StructureDefinition.snapshot` is mapped to FHIR R4 element `StructureDefinition.snapshot` as `Equivalent`."
            }
          ]
        },
        {
          "code": "StructureDefinition.snapshot.element",
          "display": "element",
          "target": [
            {
              "code": "StructureDefinition.snapshot.element",
              "display": "StructureDefinition.snapshot.element",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.snapshot.element` is mapped to FHIR R4 element `StructureDefinition.snapshot.element` as `Equivalent`."
            }
          ]
        },
        {
          "code": "StructureDefinition.differential",
          "display": "differential",
          "target": [
            {
              "code": "StructureDefinition.differential",
              "display": "StructureDefinition.differential",
              "equivalence": "wider",
              "comment": "Element `StructureDefinition.differential` is mapped to FHIR R4 element `StructureDefinition.differential` as `Equivalent`."
            }
          ]
        },
        {
          "code": "StructureDefinition.differential.element",
          "display": "element",
          "target": [
            {
              "code": "StructureDefinition.differential.element",
              "display": "StructureDefinition.differential.element",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.differential.element` is mapped to FHIR R4 element `StructureDefinition.differential.element` as `Equivalent`."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/StructureDefinition",
      "sourceVersion": "4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-StructureDefinition.fhirVersion",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "StructureDefinition.fhirVersion",
          "display": "fhirVersion",
          "target": [
            {
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `StructureDefinition.fhirVersion` is mapped to FHIR R4 element `StructureDefinition.fhirVersion` as `SourceIsBroaderThanTarget`.\nA 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."
            }
          ]
        }
      ]
    }
  ]
}