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

FHIR IG analytics

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

Resources that use this resource

No resources found


Resources that this resource uses

StructureDefinition
hl7.fhir.uv.xver-r3.r4b.r4#0.0.1-snapshot-2extension-CompartmentDefinition.jurisdictionCross-version Extension for R3.CompartmentDefinition.jurisdiction for use in FHIR R4B

Narrative

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

Generated Narrative: ConceptMap R3-CompartmentDefinition-element-map-to-R4

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


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/CompartmentDefinition|3.0.2 to CompartmentDefinitionversion: 4.0.1)

Source CodeRelationshipTarget CodeComment
CompartmentDefinition.meta (meta)is equivalent toCompartmentDefinition.metaElement `CompartmentDefinition.meta` is mapped to FHIR R4 element `CompartmentDefinition.meta` as `Equivalent`.
CompartmentDefinition.implicitRules (implicitRules)is equivalent toCompartmentDefinition.implicitRulesElement `CompartmentDefinition.implicitRules` is mapped to FHIR R4 element `CompartmentDefinition.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
CompartmentDefinition.language (language)is equivalent toCompartmentDefinition.languageElement `CompartmentDefinition.language` is mapped to FHIR R4 element `CompartmentDefinition.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).
CompartmentDefinition.text (text)is equivalent toCompartmentDefinition.textElement `CompartmentDefinition.text` is mapped to FHIR R4 element `CompartmentDefinition.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 in formation is added later.
CompartmentDefinition.contained (contained)is equivalent toCompartmentDefinition.containedElement `CompartmentDefinition.contained` is mapped to FHIR R4 element `CompartmentDefinition.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.
CompartmentDefinition.url (url)is equivalent toCompartmentDefinition.urlElement `CompartmentDefinition.url` is mapped to FHIR R4 element `CompartmentDefinition.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.
CompartmentDefinition.name (name)is equivalent toCompartmentDefinition.nameElement `CompartmentDefinition.name` is mapped to FHIR R4 element `CompartmentDefinition.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly. This is often the same as the code for the parameter, but does not need to be.
CompartmentDefinition.status (status)is equivalent toCompartmentDefinition.statusElement `CompartmentDefinition.status` is mapped to FHIR R4 element `CompartmentDefinition.status` as `Equivalent`. Allows filtering of compartment definitions that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use a retired compartment definition without due consideration.
CompartmentDefinition.experimental (experimental)is equivalent toCompartmentDefinition.experimentalElement `CompartmentDefinition.experimental` is mapped to FHIR R4 element `CompartmentDefinition.experimental` as `Equivalent`. Allows filtering of compartment definition that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use an experimental compartment definition in production.
CompartmentDefinition.date (date)is equivalent toCompartmentDefinition.dateElement `CompartmentDefinition.date` is mapped to FHIR R4 element `CompartmentDefinition.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 compartment definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
CompartmentDefinition.publisher (publisher)is equivalent toCompartmentDefinition.publisherElement `CompartmentDefinition.publisher` is mapped to FHIR R4 element `CompartmentDefinition.publisher` as `Equivalent`. Usually an organization, but may be an individual. The publisher (or steward) of the compartment definition is the organization or individual primarily responsible for the maintenance and upkeep of the compartment 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 compartment definition. This item SHOULD be populated unless the information is available from context.
CompartmentDefinition.contact (contact)is equivalent toCompartmentDefinition.contactElement `CompartmentDefinition.contact` is mapped to FHIR R4 element `CompartmentDefinition.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.
CompartmentDefinition.description (description)is equivalent toCompartmentDefinition.descriptionElement `CompartmentDefinition.description` is mapped to FHIR R4 element `CompartmentDefinition.description` as `Equivalent`. This description can be used to capture details such as why the compartment 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 compartment 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 profile is presumed to be the predominant language in the place the profile was created).
CompartmentDefinition.purpose (purpose)is equivalent toCompartmentDefinition.purposeElement `CompartmentDefinition.purpose` is mapped to FHIR R4 element `CompartmentDefinition.purpose` as `Equivalent`. This element does not describe the usage of the compartment 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 compartment definition.
CompartmentDefinition.useContext (useContext)is equivalent toCompartmentDefinition.useContextElement `CompartmentDefinition.useContext` is mapped to FHIR R4 element `CompartmentDefinition.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.
CompartmentDefinition.code (code)is equivalent toCompartmentDefinition.codeElement `CompartmentDefinition.code` is mapped to FHIR R4 element `CompartmentDefinition.code` as `Equivalent`. Only the specification can define the compartments that can exist. Servers can choose to support them.
CompartmentDefinition.search (search)is equivalent toCompartmentDefinition.searchElement `CompartmentDefinition.search` is mapped to FHIR R4 element `CompartmentDefinition.search` as `Equivalent`. Servers may define and use compartments to manage logical access without implementing the compartment related syntax.
CompartmentDefinition.resource (resource)maps to wider conceptCompartmentDefinition.resourceElement `CompartmentDefinition.resource` is mapped to FHIR R4 element `CompartmentDefinition.resource` as `Equivalent`.
CompartmentDefinition.resource.code (code)is equivalent toCompartmentDefinition.resource.codeElement `CompartmentDefinition.resource.code` is mapped to FHIR R4 element `CompartmentDefinition.resource.code` as `SourceIsNarrowerThanTarget`. The mappings for `CompartmentDefinition.resource.code` do not allow expression of the necessary codes, per the bindings on the source and target.
CompartmentDefinition.resource.param (param)is equivalent toCompartmentDefinition.resource.paramElement `CompartmentDefinition.resource.param` is mapped to FHIR R4 element `CompartmentDefinition.resource.param` as `Equivalent`. If no search parameters are listed, then the resource is not linked to the compartment.
CompartmentDefinition.resource.documentation (documentation)is equivalent toCompartmentDefinition.resource.documentationElement `CompartmentDefinition.resource.documentation` is mapped to FHIR R4 element `CompartmentDefinition.resource.documentation` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/CompartmentDefinition|3.0.2 to STU3: Intended jurisdiction for compartment definition (if applicable) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
CompartmentDefinition.jurisdiction (jurisdiction)is equivalent toExtension (STU3: Intended jurisdiction for compartment definition (if applicable) (new))Element `CompartmentDefinition.jurisdiction` has a context of CompartmentDefinition based on following the parent source element upwards and mapping to `CompartmentDefinition`. Element `CompartmentDefinition.jurisdiction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). It may be possible for the compartment definition to be used in jurisdictions other than those for which it was originally designed or intended.

Source1

{
  "resourceType": "ConceptMap",
  "id": "R3-CompartmentDefinition-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-r3.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-r3.r4"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R3-CompartmentDefinition-element-map-to-R4",
  "version": "0.1.0",
  "name": "R3CompartmentDefinitionElementMapToR4",
  "title": "Cross-version mapping for FHIR STU3 CompartmentDefinition to FHIR R4 CompartmentDefinition",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:03:23.3052643-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 STU3 CompartmentDefinition to FHIR R4.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceCanonical": "http://hl7.org/fhir/3.0",
  "targetUri": "http://hl7.org/fhir/4.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/CompartmentDefinition",
      "sourceVersion": "3.0.2",
      "target": "http://hl7.org/fhir/StructureDefinition/CompartmentDefinition",
      "targetVersion": "4.0.1",
      "element": [
        {
          "code": "CompartmentDefinition.meta",
          "display": "meta",
          "target": [
            {
              "code": "CompartmentDefinition.meta",
              "display": "CompartmentDefinition.meta",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.meta` is mapped to FHIR R4 element `CompartmentDefinition.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "CompartmentDefinition.implicitRules",
              "display": "CompartmentDefinition.implicitRules",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.implicitRules` is mapped to FHIR R4 element `CompartmentDefinition.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. \n\nThis element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.language",
          "display": "language",
          "target": [
            {
              "code": "CompartmentDefinition.language",
              "display": "CompartmentDefinition.language",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.language` is mapped to FHIR R4 element `CompartmentDefinition.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": "CompartmentDefinition.text",
          "display": "text",
          "target": [
            {
              "code": "CompartmentDefinition.text",
              "display": "CompartmentDefinition.text",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.text` is mapped to FHIR R4 element `CompartmentDefinition.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 in formation is added later."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.contained",
          "display": "contained",
          "target": [
            {
              "code": "CompartmentDefinition.contained",
              "display": "CompartmentDefinition.contained",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.contained` is mapped to FHIR R4 element `CompartmentDefinition.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."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.url",
          "display": "url",
          "target": [
            {
              "code": "CompartmentDefinition.url",
              "display": "CompartmentDefinition.url",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.url` is mapped to FHIR R4 element `CompartmentDefinition.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."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.name",
          "display": "name",
          "target": [
            {
              "code": "CompartmentDefinition.name",
              "display": "CompartmentDefinition.name",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.name` is mapped to FHIR R4 element `CompartmentDefinition.name` as `Equivalent`.\nThe name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly. This is often the same as the code for the parameter, but does not need to be."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.status",
          "display": "status",
          "target": [
            {
              "code": "CompartmentDefinition.status",
              "display": "CompartmentDefinition.status",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.status` is mapped to FHIR R4 element `CompartmentDefinition.status` as `Equivalent`.\nAllows filtering of compartment definitions that are appropriate for use vs. not.  \nThis is labeled as \"Is Modifier\" because applications should not use a retired compartment definition without due consideration."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.experimental",
          "display": "experimental",
          "target": [
            {
              "code": "CompartmentDefinition.experimental",
              "display": "CompartmentDefinition.experimental",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.experimental` is mapped to FHIR R4 element `CompartmentDefinition.experimental` as `Equivalent`.\nAllows filtering of compartment definition that are appropriate for use vs. not. This is labeled as \"Is Modifier\" because applications should not use an experimental compartment definition in production."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.date",
          "display": "date",
          "target": [
            {
              "code": "CompartmentDefinition.date",
              "display": "CompartmentDefinition.date",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.date` is mapped to FHIR R4 element `CompartmentDefinition.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 compartment definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.publisher",
          "display": "publisher",
          "target": [
            {
              "code": "CompartmentDefinition.publisher",
              "display": "CompartmentDefinition.publisher",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.publisher` is mapped to FHIR R4 element `CompartmentDefinition.publisher` as `Equivalent`.\nUsually an organization, but may be an individual. The publisher (or steward) of the compartment definition is the organization or individual primarily responsible for the maintenance and upkeep of the compartment 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 compartment definition. This item SHOULD be populated unless the information is available from context."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.contact",
          "display": "contact",
          "target": [
            {
              "code": "CompartmentDefinition.contact",
              "display": "CompartmentDefinition.contact",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.contact` is mapped to FHIR R4 element `CompartmentDefinition.contact` as `Equivalent`.\nMay be a web site, an email address, a telephone number, etc."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.description",
          "display": "description",
          "target": [
            {
              "code": "CompartmentDefinition.description",
              "display": "CompartmentDefinition.description",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.description` is mapped to FHIR R4 element `CompartmentDefinition.description` as `Equivalent`.\nThis description can be used to capture details such as why the compartment 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 compartment 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 profile is presumed to be the predominant language in the place the profile was created)."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.purpose",
          "display": "purpose",
          "target": [
            {
              "code": "CompartmentDefinition.purpose",
              "display": "CompartmentDefinition.purpose",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.purpose` is mapped to FHIR R4 element `CompartmentDefinition.purpose` as `Equivalent`.\nThis element does not describe the usage of the compartment 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 compartment definition."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.useContext",
          "display": "useContext",
          "target": [
            {
              "code": "CompartmentDefinition.useContext",
              "display": "CompartmentDefinition.useContext",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.useContext` is mapped to FHIR R4 element `CompartmentDefinition.useContext` as `Equivalent`.\nWhen multiple useContexts are specified, there is no expectation whether all or any of the contexts apply."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.code",
          "display": "code",
          "target": [
            {
              "code": "CompartmentDefinition.code",
              "display": "CompartmentDefinition.code",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.code` is mapped to FHIR R4 element `CompartmentDefinition.code` as `Equivalent`.\nOnly the specification can define the compartments that can exist. Servers can choose to support them."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.search",
          "display": "search",
          "target": [
            {
              "code": "CompartmentDefinition.search",
              "display": "CompartmentDefinition.search",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.search` is mapped to FHIR R4 element `CompartmentDefinition.search` as `Equivalent`.\nServers may define and use compartments to manage logical access without implementing the compartment related syntax."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.resource",
          "display": "resource",
          "target": [
            {
              "code": "CompartmentDefinition.resource",
              "display": "CompartmentDefinition.resource",
              "equivalence": "wider",
              "comment": "Element `CompartmentDefinition.resource` is mapped to FHIR R4 element `CompartmentDefinition.resource` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.resource.code",
          "display": "code",
          "target": [
            {
              "code": "CompartmentDefinition.resource.code",
              "display": "CompartmentDefinition.resource.code",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.resource.code` is mapped to FHIR R4 element `CompartmentDefinition.resource.code` as `SourceIsNarrowerThanTarget`.\nThe mappings for `CompartmentDefinition.resource.code` do not allow expression of the necessary codes, per the bindings on the source and target."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.resource.param",
          "display": "param",
          "target": [
            {
              "code": "CompartmentDefinition.resource.param",
              "display": "CompartmentDefinition.resource.param",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.resource.param` is mapped to FHIR R4 element `CompartmentDefinition.resource.param` as `Equivalent`.\nIf no search parameters are listed, then the resource is not linked to the compartment."
            }
          ]
        },
        {
          "code": "CompartmentDefinition.resource.documentation",
          "display": "documentation",
          "target": [
            {
              "code": "CompartmentDefinition.resource.documentation",
              "display": "CompartmentDefinition.resource.documentation",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.resource.documentation` is mapped to FHIR R4 element `CompartmentDefinition.resource.documentation` as `Equivalent`."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/CompartmentDefinition",
      "sourceVersion": "3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-CompartmentDefinition.jurisdiction",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "CompartmentDefinition.jurisdiction",
          "display": "jurisdiction",
          "target": [
            {
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `CompartmentDefinition.jurisdiction` has a context of CompartmentDefinition based on following the parent source element upwards and mapping to `CompartmentDefinition`.\nElement `CompartmentDefinition.jurisdiction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nIt may be possible for the compartment definition to be used in jurisdictions other than those for which it was originally designed or intended."
            }
          ]
        }
      ]
    }
  ]
}