R5-ValueSet-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R5-ValueSet-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R5-ValueSet-element-map-to-R4 Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ValueSet|5.0.0 to ValueSetversion: 4.0.1) Source Code Relationship Target Code Comment ValueSet.meta (meta) is equivalent to ValueSet.meta Element `ValueSet.meta` is mapped to FHIR R4 element `ValueSet.meta` as `Equivalent`. ValueSet.implicitRules (implicitRules) is equivalent to ValueSet.implicitRules Element `ValueSet.implicitRules` is mapped to FHIR R4 element `ValueSet.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. ValueSet.language (language) is equivalent to ValueSet.language Element `ValueSet.language` is mapped to FHIR R4 element `ValueSet.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). Va…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fhir
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 0
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R5-ValueSet-element-map-to-R4
  l: R5-ValueSet-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R5ValueSetElementMapToR4
title:
  v: Cross-version mapping for FHIR R5 ValueSet to FHIR R4 ValueSet
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:49.9890483-05:00
contact:
  name:
    v: FHIR Infrastructure
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/fiwg
description:
  v: This ConceptMap represents cross-version mappings for elements from a FHIR R5 ValueSet to FHIR R4.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source: Canonical
  v: http://hl7.org/fhir/5.0
  l: http://hl7.org/fhir/5.0
target: Uri
  v: http://hl7.org/fhir/4.0
  l: http://hl7.org/fhir/4.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/ValueSet
    l: ValueSet
  source version:
    v: 5.0.0
  target:
    v: http://hl7.org/fhir/StructureDefinition/ValueSet
    l: ValueSet
  target version:
    v: 4.0.1
  element:
    code:
      v: ValueSet.meta
    display:
      v: meta
    target:
      code:
        v: ValueSet.meta
      display:
        v: ValueSet.meta
      equivalence:
        v: equivalent
      comment:
        v: Element `ValueSet.meta` is mapped to FHIR R4 element `ValueSet.meta` as `Equivalent`.
  element:
    code:
      v: ValueSet.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: ValueSet.implicitRules
      display:
        v: ValueSet.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element `ValueSet.implicitRules` is mapped to FHIR R4 element `ValueSet.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:
    code:
      v: ValueSet.language
    display:
      v: language
    target:
      code:
        v: ValueSet.language
      display:
        v: ValueSet.language
      equivalence:
        v: equivalent
      comment:
        v: Element `ValueSet.language` is mapped to FHIR R4 element `ValueSet.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:
    code:
      v: ValueSet.text
    display:
      v: text
    target:
      code:
        v: ValueSet.text
      display:
        v: ValueSet.text
      equivalence:
        v: equivalent
      comment:
        v: Element `ValueSet.text` is mapped to FHIR R4 element `ValueSet.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:
    code:
      v: ValueSet.contained
    display:
      v: contained
    target:
      code:
        v: ValueSet.contained
      display:
        v: ValueSet.contained
      equivalence:
        v: equivalent
      comment:
        v: Element `ValueSet.contained` is mapped to FHIR R4 element `ValueSet.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
  element:
    code:
      v: ValueSet.url
    display:
      v: url
    target:
      code:
        v: ValueSet.url
      display:
        v: ValueSet.url
      equivalence:
        v: equivalent
      comment:
        v: Element `ValueSet.url` is mapped to FHIR R4 element `ValueSet.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:
    code:
      v: ValueSet.identifier
    display:
      v: identifier
    target:
      code:
        v: ValueSet.identifier
      display:
        v: ValueSet.identifier
      equivalence:
        v: equivalent
      comment:
        v: Element `ValueSet.identifier` is mapped to FHIR R4 element `ValueSet.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 value set outside of FHIR, where it is not possible to use the logical URI.
  element:
    code:
      v: ValueSet.version
    display:
      v: version
    target:
      code:
        v: ValueSet.version
      display:
        v: ValueSet.version
      equivalence:
        v: equivalent
      comment:
        v: Element `ValueSet.version` is mapped to FHIR R4 element `ValueSet.version` as `Equivalent`. There may be different value set 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 value set with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format).

code:
  v: ValueSet.name
display:
  v: name
target:
  code:
    v: ValueSet.name
  display:
    v: ValueSet.name
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.name` is mapped to FHIR R4 element `ValueSet.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.A name should be provided unless the value set is a contained resource (e.g. an anonymous value set in a profile). Most registries will require a name.

code:
  v: ValueSet.title
display:
  v: title
target:
  code:
    v: ValueSet.title
  display:
    v: ValueSet.title
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.title` is mapped to FHIR R4 element `ValueSet.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

code:
  v: ValueSet.status
display:
  v: status
target:
  code:
    v: ValueSet.status
  display:
    v: ValueSet.status
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.status` is mapped to FHIR R4 element `ValueSet.status` as `Equivalent`. Allows filtering of value sets that are appropriate for use versus not.See also the [http://hl7.org/fhir/StructureDefinition/valueset-workflowStatusDescription](http://hl7.org/fhir/extensions/StructureDefinition-valueset-workflowStatusDescription.html) extension for additional status information related to the editorial process. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

code:
  v: ValueSet.experimental
display:
  v: experimental
target:
  code:
    v: ValueSet.experimental
  display:
    v: ValueSet.experimental
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.experimental` is mapped to FHIR R4 element `ValueSet.experimental` as `Equivalent`. Allows filtering of value sets that are appropriate for use versus not.

code:
  v: ValueSet.date
display:
  v: date
target:
  code:
    v: ValueSet.date
  display:
    v: ValueSet.date
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.date` is mapped to FHIR R4 element `ValueSet.date` as `Equivalent`. Note that this is not the same as the meta.lastUpdated which is specific to an instance of a value set resource on a server. 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).

code:
  v: ValueSet.publisher
display:
  v: publisher
target:
  code:
    v: ValueSet.publisher
  display:
    v: ValueSet.publisher
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.publisher` is mapped to FHIR R4 element `ValueSet.publisher` as `Equivalent`. Usually an organization but may be an individual. 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 value set. This item SHOULD be populated unless the information is available from context.

code:
  v: ValueSet.contact
display:
  v: contact
target:
  code:
    v: ValueSet.contact
  display:
    v: ValueSet.contact
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.contact` is mapped to FHIR R4 element `ValueSet.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

code:
  v: ValueSet.description
display:
  v: description
target:
  code:
    v: ValueSet.description
  display:
    v: ValueSet.description
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.description` is mapped to FHIR R4 element `ValueSet.description` as `Equivalent`. Description SHOULD contain instructions for clinical or administrative use and interpretation and information about misuse. Description SHOULD be populated unless the information is available from context. Description SHOULD be populated unless the value set is a contained resource (e.g. a value set defined solely in the context of a profile).

code:
  v: ValueSet.useContext
display:
  v: useContext
target:
  code:
    v: ValueSet.useContext
  display:
    v: ValueSet.useContext
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.useContext` is mapped to FHIR R4 element `ValueSet.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.

code:
  v: ValueSet.jurisdiction
display:
  v: jurisdiction
target:
  code:
    v: ValueSet.jurisdiction
  display:
    v: ValueSet.jurisdiction
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.jurisdiction` is mapped to FHIR R4 element `ValueSet.jurisdiction` as `Equivalent`. Element `ValueSet.jurisdiction` has been flagged as deprecated. It may be possible for the value set 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.)

code:
  v: ValueSet.immutable
display:
  v: immutable
target:
  code:
    v: ValueSet.immutable
  display:
    v: ValueSet.immutable
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.immutable` is mapped to FHIR R4 element `ValueSet.immutable` as `Equivalent`. Normally immutability is set to 'false', which is the default assumption if it is not populated. Note that the implication is that if this is set to 'true', there may be only one ValueSet version for this definition. Immutability tends to be set to 'true' in one of two cases: - Where the value set, by the nature of its usage, cannot change. For example "All specializations of ACT in ActClassCode" - Where there's no safe way to express the "Purpose" such that someone else could safely make changes to the value set definition. Source workflow control must guarantee that the same URI always yields the same definition.

code:
  v: ValueSet.purpose
display:
  v: purpose
target:
  code:
    v: ValueSet.purpose
  display:
    v: ValueSet.purpose
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.purpose` is mapped to FHIR R4 element `ValueSet.purpose` as `Equivalent`. This element does not describe the usage of the value set. 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 value set.

code:
  v: ValueSet.copyright
display:
  v: copyright
target:
  code:
    v: ValueSet.copyright
  display:
    v: ValueSet.copyright
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.copyright` is mapped to FHIR R4 element `ValueSet.copyright` as `Equivalent`. Frequently, the copyright differs between the value set and the codes that are included. The copyright statement should clearly differentiate between these when required.

code:
  v: ValueSet.compose
display:
  v: compose
target:
  code:
    v: ValueSet.compose
  display:
    v: ValueSet.compose
  equivalence:
    v: wider
  comment:
    v: Element `ValueSet.compose` is mapped to FHIR R4 element `ValueSet.compose` as `Equivalent`.

code:
  v: ValueSet.compose.lockedDate
display:
  v: lockedDate
target:
  code:
    v: ValueSet.compose.lockedDate
  display:
    v: ValueSet.compose.lockedDate
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.compose.lockedDate` is mapped to FHIR R4 element `ValueSet.compose.lockedDate` as `Equivalent`. With a defined lockedDate the value set is considered "Locked". Otherwise, the value set may have different expansions as underlying code systems and/or value sets evolve. The interpretation of lockedDate is often dependent on the context - e.g. a SNOMED CT derived value set with a lockedDate will have a different expansion in USA than in UK. If a value set specifies a version for include and exclude statements, and also specifies a locked date, the specified versions need to be available that date, or the value set will not be usable.

code:
  v: ValueSet.compose.inactive
display:
  v: inactive
target:
  code:
    v: ValueSet.compose.inactive
  display:
    v: ValueSet.compose.inactive
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.compose.inactive` is mapped to FHIR R4 element `ValueSet.compose.inactive` as `Equivalent`. Note that in the FHIR terminology framework, "deprecated" does not mean inactive, but in some code systems, e.g. LOINC, "deprecated" does mean inactive. Code systems should define what codes are considered to be inactive. If this is not clearly defined (including in the FHIR code system resource), then all codes are assumed to be active. The Value Set Definition specification defines an ActiveOnly element, which is the reverse of this element e.g. (ValueSet.compose.inactive=FALSE) is the same as (VSD.ActiveOnly=TRUE).

code:
  v: ValueSet.compose.include
display:
  v: include
target:
  code:
    v: ValueSet.compose.include
  display:
    v: ValueSet.compose.include
  equivalence:
    v: wider
  comment:
    v: Element `ValueSet.compose.include` is mapped to FHIR R4 element `ValueSet.compose.include` as `Equivalent`. All the conditions in an include must be true. If a system is listed, all the codes from the system are listed. If one or more filters are listed, all of the filters must apply. If one or more value sets are listed, the codes must be in all the value sets. E.g. each include is 'include all the codes that meet all these conditions'.

code:
  v: ValueSet.compose.include.system
display:
  v: system
target:
  code:
    v: ValueSet.compose.include.system
  display:
    v: ValueSet.compose.include.system
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.compose.include.system` is mapped to FHIR R4 element `ValueSet.compose.include.system` as `Equivalent`. If there are no codes or filters, the entire code system is included. Note that the set of codes that are included may contain abstract codes. See ''Coding.system'' for further documentation about the correct value for the system element.

code:
  v: ValueSet.compose.include.version
display:
  v: version
target:
  code:
    v: ValueSet.compose.include.version
  display:
    v: ValueSet.compose.include.version
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.compose.include.version` is mapped to FHIR R4 element `ValueSet.compose.include.version` as `Equivalent`. This is used when selecting the descendants of a concept - they may change between versions. If no version is specified, then the exact contents of the value set might not be known until a context of use binds it to a particular version. The special value '*' means all versions; It is at server discretion regarding expansions and which versions must be supported.

code:
  v: ValueSet.compose.include.concept
display:
  v: concept
target:
  code:
    v: ValueSet.compose.include.concept
  display:
    v: ValueSet.compose.include.concept
  equivalence:
    v: wider
  comment:
    v: Element `ValueSet.compose.include.concept` is mapped to FHIR R4 element `ValueSet.compose.include.concept` as `Equivalent`. The list of concepts is considered ordered, though the order might not have any particular significance. Typically, the order of an expansion follows that defined in the compose element.

code:
  v: ValueSet.compose.include.concept.code
display:
  v: code
target:
  code:
    v: ValueSet.compose.include.concept.code
  display:
    v: ValueSet.compose.include.concept.code
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.compose.include.concept.code` is mapped to FHIR R4 element `ValueSet.compose.include.concept.code` as `Equivalent`. Expressions are allowed if defined by the underlying code system.

code:
  v: ValueSet.compose.include.concept.display
display:
  v: display
target:
  code:
    v: ValueSet.compose.include.concept.display
  display:
    v: ValueSet.compose.include.concept.display
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.compose.include.concept.display` is mapped to FHIR R4 element `ValueSet.compose.include.concept.display` as `Equivalent`. The value set resource allows for an alternative display to be specified for when this concept is used in this particular value set. See notes in the value set narrative about the correct use of this element.

code:
  v: ValueSet.compose.include.concept.designation
display:
  v: designation
target:
  code:
    v: ValueSet.compose.include.concept.designation
  display:
    v: ValueSet.compose.include.concept.designation
  equivalence:
    v: wider
  comment:
    v: Element `ValueSet.compose.include.concept.designation` is mapped to FHIR R4 element `ValueSet.compose.include.concept.designation` as `Equivalent`. Concepts have both a ```display``` and an array of ```designation```. The display is equivalent to a special designation with an implied ```designation.use``` of "primary code" and a language equal to the [Resource Language](https://hl7.org/fhir/resource..html#language).

code:
  v: ValueSet.compose.include.concept.designation.language
display:
  v: language
target:
  code:
    v: ValueSet.compose.include.concept.designation.language
  display:
    v: ValueSet.compose.include.concept.designation.language
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.compose.include.concept.designation.language` is mapped to FHIR R4 element `ValueSet.compose.include.concept.designation.language` as `Equivalent`. In the absence of a language, the resource language applies.

code:
  v: ValueSet.compose.include.concept.designation.use
display:
  v: use
target:
  code:
    v: ValueSet.compose.include.concept.designation.use
  display:
    v: ValueSet.compose.include.concept.designation.use
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.compose.include.concept.designation.use` is mapped to FHIR R4 element `ValueSet.compose.include.concept.designation.use` as `Equivalent`. If no use is provided, the designation can be assumed to be suitable for general display to a human user.

code:
  v: ValueSet.compose.include.concept.designation.value
display:
  v: value
target:
  code:
    v: ValueSet.compose.include.concept.designation.value
  display:
    v: ValueSet.compose.include.concept.designation.value
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.compose.include.concept.designation.value` is mapped to FHIR R4 element `ValueSet.compose.include.concept.designation.value` as `Equivalent`.

code:
  v: ValueSet.compose.include.filter
display:
  v: filter
target:
  code:
    v: ValueSet.compose.include.filter
  display:
    v: ValueSet.compose.include.filter
  equivalence:
    v: wider
  comment:
    v: Element `ValueSet.compose.include.filter` is mapped to FHIR R4 element `ValueSet.compose.include.filter` as `Equivalent`. Selecting codes by specifying filters based on properties is only possible where the underlying code system defines appropriate properties. Note that in some cases, the underlying code system defines the logical concepts but not the literal codes for the concepts. In such cases, the literal definitions may be provided by a third party.

code:
  v: ValueSet.compose.include.filter.property
display:
  v: property
target:
  code:
    v: ValueSet.compose.include.filter.property
  display:
    v: ValueSet.compose.include.filter.property
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.compose.include.filter.property` is mapped to FHIR R4 element `ValueSet.compose.include.filter.property` as `Equivalent`.

code:
  v: ValueSet.compose.include.filter.op
display:
  v: op
target:
  code:
    v: ValueSet.compose.include.filter.op
  display:
    v: ValueSet.compose.include.filter.op
  equivalence:
    v: wider
  comment:
    v: Element `ValueSet.compose.include.filter.op` is mapped to FHIR R4 element `ValueSet.compose.include.filter.op` as `SourceIsBroaderThanTarget`. In case filter.property represents a property of the system, the operation applies to the selected property. In case filter.property represents a filter of the system, the operation SHALL match one of the CodeSystem.filter.operator values.

code:
  v: ValueSet.compose.include.filter.value
display:
  v: value
target:
  code:
    v: ValueSet.compose.include.filter.value
  display:
    v: ValueSet.compose.include.filter.value
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.compose.include.filter.value` is mapped to FHIR R4 element `ValueSet.compose.include.filter.value` as `Equivalent`. Use regex matching with care - full regex matching on every SNOMED CT term is prohibitive, for example.

code:
  v: ValueSet.compose.include.valueSet
display:
  v: valueSet
target:
  code:
    v: ValueSet.compose.include.valueSet
  display:
    v: ValueSet.compose.include.valueSet
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.compose.include.valueSet` is mapped to FHIR R4 element `ValueSet.compose.include.valueSet` as `Equivalent`. The value set URI is either a logical reference to a defined value set such as a [SNOMED CT reference set](https://terminology.hl7.org/SNOMEDCT.html), or a direct reference to a value set definition using ValueSet.url. The reference might not refer to an actual FHIR ValueSet resource; in this case, whatever is referred to is an implicit definition of a value set that needs to be clear about how versions are resolved.

code:
  v: ValueSet.compose.exclude
display:
  v: exclude
target:
  code:
    v: ValueSet.compose.exclude
  display:
    v: ValueSet.compose.exclude
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.compose.exclude` is mapped to FHIR R4 element `ValueSet.compose.exclude` as `Equivalent`. Usually this is used to selectively exclude codes that were included by subsumption in the inclusions. Any display names specified for the codes are ignored.

code:
  v: ValueSet.expansion
display:
  v: expansion
target:
  code:
    v: ValueSet.expansion
  display:
    v: ValueSet.expansion
  equivalence:
    v: wider
  comment:
    v: Element `ValueSet.expansion` is mapped to FHIR R4 element `ValueSet.expansion` as `Equivalent`. Expansion is performed to produce a collection of codes that are ready to use for data entry or validation. Value set expansions are always considered to be stateless - they are a record of the set of codes in the value set at a point in time under a given set of conditions, and are not subject to ongoing maintenance. Expansion.parameter is a simplified list of parameters - a subset of the features of the [Parameters](https://hl7.org/fhir/parameters.html) resource.

code:
  v: ValueSet.expansion.identifier
display:
  v: identifier
target:
  code:
    v: ValueSet.expansion.identifier
  display:
    v: ValueSet.expansion.identifier
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.expansion.identifier` is mapped to FHIR R4 element `ValueSet.expansion.identifier` as `Equivalent`. Typically, this uri is a UUID (e.g. urn:uuid:8230ff20-c97a-4167-a59d-dc2cb9df16dd).

code:
  v: ValueSet.expansion.timestamp
display:
  v: timestamp
target:
  code:
    v: ValueSet.expansion.timestamp
  display:
    v: ValueSet.expansion.timestamp
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.expansion.timestamp` is mapped to FHIR R4 element `ValueSet.expansion.timestamp` as `Equivalent`. This SHOULD be a fully populated instant, but in some circumstances, value sets are expanded by hand, and the expansion is published without that precision.

code:
  v: ValueSet.expansion.total
display:
  v: total
target:
  code:
    v: ValueSet.expansion.total
  display:
    v: ValueSet.expansion.total
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.expansion.total` is mapped to FHIR R4 element `ValueSet.expansion.total` as `Equivalent`. Paging only applies to flat expansions.

code:
  v: ValueSet.expansion.offset
display:
  v: offset
target:
  code:
    v: ValueSet.expansion.offset
  display:
    v: ValueSet.expansion.offset
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.expansion.offset` is mapped to FHIR R4 element `ValueSet.expansion.offset` as `Equivalent`. Paging only applies to flat expansions. If a filter is applied, the count is the number of concepts that matched the filter, not the number of concepts in an unfiltered view of the expansion.

code:
  v: ValueSet.expansion.parameter
display:
  v: parameter
target:
  code:
    v: ValueSet.expansion.parameter
  display:
    v: ValueSet.expansion.parameter
  equivalence:
    v: wider
  comment:
    v: Element `ValueSet.expansion.parameter` is mapped to FHIR R4 element `ValueSet.expansion.parameter` as `Equivalent`. The server decides which parameters to include here, but at a minimum, the list SHOULD include all of the parameters that affect the $expand operation. If the expansion will be persisted all of these parameters SHALL be included. If the codeSystem on the server has a specified version then this version SHALL be provided as a parameter in the expansion (note that not all code systems have a version).

code:
  v: ValueSet.expansion.parameter.name
display:
  v: name
target:
  code:
    v: ValueSet.expansion.parameter.name
  display:
    v: ValueSet.expansion.parameter.name
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.expansion.parameter.name` is mapped to FHIR R4 element `ValueSet.expansion.parameter.name` as `Equivalent`. The names are assigned at the discretion of the server.

code:
  v: ValueSet.expansion.parameter.value[x]
display:
  v: value[x]
target:
  code:
    v: ValueSet.expansion.parameter.value[x]
  display:
    v: ValueSet.expansion.parameter.value[x]
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.expansion.parameter.value[x]` is mapped to FHIR R4 element `ValueSet.expansion.parameter.value[x]` as `RelatedTo`. The target context `ValueSet.expansion.parameter.value[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ValueSet.expansion.parameter`.

code:
  v: ValueSet.expansion.contains
display:
  v: contains
target:
  code:
    v: ValueSet.expansion.contains
  display:
    v: ValueSet.expansion.contains
  equivalence:
    v: wider
  comment:
    v: Element `ValueSet.expansion.contains` is mapped to FHIR R4 element `ValueSet.expansion.contains` as `Equivalent`.

code:
  v: ValueSet.expansion.contains.system
display:
  v: system
target:
  code:
    v: ValueSet.expansion.contains.system
  display:
    v: ValueSet.expansion.contains.system
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.expansion.contains.system` is mapped to FHIR R4 element `ValueSet.expansion.contains.system` as `Equivalent`.

code:
  v: ValueSet.expansion.contains.abstract
display:
  v: abstract
target:
  code:
    v: ValueSet.expansion.contains.abstract
  display:
    v: ValueSet.expansion.contains.abstract
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.expansion.contains.abstract` is mapped to FHIR R4 element `ValueSet.expansion.contains.abstract` as `Equivalent`. This should not be understood to exclude its use for searching (e.g. by subsumption testing). The client should know whether it is appropriate for the user to select an abstract code or not.

code:
  v: ValueSet.expansion.contains.inactive
display:
  v: inactive
target:
  code:
    v: ValueSet.expansion.contains.inactive
  display:
    v: ValueSet.expansion.contains.inactive
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.expansion.contains.inactive` is mapped to FHIR R4 element `ValueSet.expansion.contains.inactive` as `Equivalent`. This should only have a value if the concept is inactive.

code:
  v: ValueSet.expansion.contains.version
display:
  v: version
target:
  code:
    v: ValueSet.expansion.contains.version
  display:
    v: ValueSet.expansion.contains.version
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.expansion.contains.version` is mapped to FHIR R4 element `ValueSet.expansion.contains.version` as `Equivalent`. The exact value of the version string is specified by the system from which the code is derived.

code:
  v: ValueSet.expansion.contains.code
display:
  v: code
target:
  code:
    v: ValueSet.expansion.contains.code
  display:
    v: ValueSet.expansion.contains.code
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.expansion.contains.code` is mapped to FHIR R4 element `ValueSet.expansion.contains.code` as `Equivalent`.

code:
  v: ValueSet.expansion.contains.display
display:
  v: display
target:
  code:
    v: ValueSet.expansion.contains.display
  display:
    v: ValueSet.expansion.contains.display
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.expansion.contains.display` is mapped to FHIR R4 element `ValueSet.expansion.contains.display` as `Equivalent`.

code:
  v: ValueSet.expansion.contains.designation
display:
  v: designation
target:
  code:
    v: ValueSet.expansion.contains.designation
  display:
    v: ValueSet.expansion.contains.designation
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.expansion.contains.designation` is mapped to FHIR R4 element `ValueSet.expansion.contains.designation` as `Equivalent`. The designations provided must be based on the value set and code system definitions.

code:
  v: ValueSet.expansion.contains.contains
display:
  v: contains
target:
  code:
    v: ValueSet.expansion.contains.contains
  display:
    v: ValueSet.expansion.contains.contains
  equivalence:
    v: equivalent
  comment:
    v: Element `ValueSet.expansion.contains.contains` is mapped to FHIR R4 element `ValueSet.expansion.contains.contains` as `Equivalent`. If the expansion uses this element, there is no implication about the logical relationship between them, and the structure cannot be used for logical inferencing. The structure exists to provide navigational assistance for helping human users to locate codes in the expansion.

source:
  v: http://hl7.org/fhir/StructureDefinition/ValueSet
  l: ValueSet
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ValueSet.compose.include.concept.designation.additionalUse
  l: extension-ValueSet.compose.include.concept.designation.additionalUse
target version:
  v: 0.1.0
element:
  code:
    v: ValueSet.compose.include.concept.designation.additionalUse
  display:
    v: additionalUse
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ValueSet.compose.include.concept.designation.additionalUse` has a context of ValueSet.compose.include.concept.designation based on following the parent source element upwards and mapping to `ValueSet`. Element `ValueSet.compose.include.concept.designation.additionalUse` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This was added rather than increasing the cardinality of .use to 0..* in order to maintain backward compatibility.

source:
  v: http://hl7.org/fhir/StructureDefinition/ValueSet
  l: ValueSet
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ValueSet.compose.include.filter.op
  l: extension-ValueSet.compose.include.filter.op
target version:
  v: 0.1.0
element:
  code:
    v: ValueSet.compose.include.filter.op
  display:
    v: op
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `ValueSet.compose.include.filter.op` is mapped to FHIR R4 element `ValueSet.compose.include.filter.op` as `SourceIsBroaderThanTarget`. In case filter.property represents a property of the system, the operation applies to the selected property. In case filter.property represents a filter of the system, the operation SHALL match one of the CodeSystem.filter.operator values.

source:
  v: http://hl7.org/fhir/StructureDefinition/ValueSet
  l: ValueSet
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ValueSet.compose.include.copyright
  l: extension-ValueSet.compose.include.copyright
target version:
  v: 0.1.0
element:
  code:
    v: ValueSet.compose.include.copyright
  display:
    v: copyright
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ValueSet.compose.include.copyright` has a context of ValueSet.compose.include based on following the parent source element upwards and mapping to `ValueSet`. Element `ValueSet.compose.include.copyright` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/ValueSet
  l: ValueSet
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ValueSet.compose.property
  l: extension-ValueSet.compose.property
target version:
  v: 0.1.0
element:
  code:
    v: ValueSet.compose.property
  display:
    v: property
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ValueSet.compose.property` has a context of ValueSet.compose based on following the parent source element upwards and mapping to `ValueSet`. Element `ValueSet.compose.property` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Note that property names can clash, so using a URI is recommended.

source:
  v: http://hl7.org/fhir/StructureDefinition/ValueSet
  l: ValueSet
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ValueSet.expansion.next
  l: extension-ValueSet.expansion.next
target version:
  v: 0.1.0
element:
  code:
    v: ValueSet.expansion.next
  display:
    v: next
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ValueSet.expansion.next` has a context of ValueSet.expansion based on following the parent source element upwards and mapping to `ValueSet`. Element `ValueSet.expansion.next` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Clients SHOULD use the next link, if present, to page through expansion results in preference to using the offset and count parameters. Due to the optional nature of the next link, its absence does not necessarily indicate that it is the last page of results. Instead, as the offset and count parameters SHALL be populated when paging, clients can reliably use the count/offset parameters to determine whether the whole expansion is returned.

source:
  v: http://hl7.org/fhir/StructureDefinition/ValueSet
  l: ValueSet
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ValueSet.expansion.property
  l: extension-ValueSet.expansion.property
target version:
  v: 0.1.0
element:
  code:
    v: ValueSet.expansion.property
  display:
    v: property
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ValueSet.expansion.property` has a context of ValueSet.expansion based on following the parent source element upwards and mapping to `ValueSet`. Element `ValueSet.expansion.property` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ValueSet.expansion.property.code
  display:
    v: code
  target:
    code:
      v: Extension.extension:code
    equivalence:
      v: wider
    comment:
      v: Element `ValueSet.expansion.property.code` is part of an existing definition because parent element `ValueSet.expansion.property` requires a cross-version extension. Element `ValueSet.expansion.property.code` has a context of ValueSet.expansion based on following the parent source element upwards and mapping to `ValueSet`. Element `ValueSet.expansion.property.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ValueSet.expansion.property.uri
  display:
    v: uri
  target:
    code:
      v: Extension.extension:uri
    equivalence:
      v: wider
    comment:
      v: Element `ValueSet.expansion.property.uri` is part of an existing definition because parent element `ValueSet.expansion.property` requires a cross-version extension. Element `ValueSet.expansion.property.uri` has a context of ValueSet.expansion based on following the parent source element upwards and mapping to `ValueSet`. Element `ValueSet.expansion.property.uri` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/ValueSet
  l: ValueSet
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ValueSet.expansion.contains.property
  l: extension-ValueSet.expansion.contains.property
target version:
  v: 0.1.0
element:
  code:
    v: ValueSet.expansion.contains.property
  display:
    v: property
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ValueSet.expansion.contains.property` has a context of ValueSet.expansion.contains based on following the parent source element upwards and mapping to `ValueSet`. Element `ValueSet.expansion.contains.property` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ValueSet.expansion.contains.property.code
  display:
    v: code
  target:
    code:
      v: Extension.extension:code
    equivalence:
      v: wider
    comment:
      v: Element `ValueSet.expansion.contains.property.code` is part of an existing definition because parent element `ValueSet.expansion.contains.property` requires a cross-version extension. Element `ValueSet.expansion.contains.property.code` has a context of ValueSet.expansion.contains based on following the parent source element upwards and mapping to `ValueSet`. Element `ValueSet.expansion.contains.property.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ValueSet.expansion.contains.property.value[x]
  display:
    v: value[x]
  target:
    code:
      v: Extension.extension:value
    equivalence:
      v: wider
    comment:
      v: Element `ValueSet.expansion.contains.property.value[x]` is part of an existing definition because parent element `ValueSet.expansion.contains.property` requires a cross-version extension. Element `ValueSet.expansion.contains.property.value[x]` has a context of ValueSet.expansion.contains based on following the parent source element upwards and mapping to `ValueSet`. Element `ValueSet.expansion.contains.property.value[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ValueSet.expansion.contains.property.subProperty
  display:
    v: subProperty
  target:
    code:
      v: Extension.extension:subProperty
    equivalence:
      v: wider
    comment:
      v: Element `ValueSet.expansion.contains.property.subProperty` is part of an existing definition because parent element `ValueSet.expansion.contains.property` requires a cross-version extension. Element `ValueSet.expansion.contains.property.subProperty` has a context of ValueSet.expansion.contains based on following the parent source element upwards and mapping to `ValueSet`. Element `ValueSet.expansion.contains.property.subProperty` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ValueSet.expansion.contains.property.subProperty.code
  display:
    v: code
  target:
    code:
      v: Extension.extension:subProperty.extension:code
    equivalence:
      v: wider
    comment:
      v: Element `ValueSet.expansion.contains.property.subProperty.code` is part of an existing definition because parent element `ValueSet.expansion.contains.property.subProperty` requires a cross-version extension. Element `ValueSet.expansion.contains.property.subProperty.code` has a context of ValueSet.expansion.contains based on following the parent source element upwards and mapping to `ValueSet`. Element `ValueSet.expansion.contains.property.subProperty.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ValueSet.expansion.contains.property.subProperty.value[x]
  display:
    v: value[x]
  target:
    code:
      v: Extension.extension:subProperty.extension:value
    equivalence:
      v: wider
    comment:
      v: Element `ValueSet.expansion.contains.property.subProperty.value[x]` is part of an existing definition because parent element `ValueSet.expansion.contains.property.subProperty` requires a cross-version extension. Element `ValueSet.expansion.contains.property.subProperty.value[x]` has a context of ValueSet.expansion.contains based on following the parent source element upwards and mapping to `ValueSet`. Element `ValueSet.expansion.contains.property.subProperty.value[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/ValueSet
  l: ValueSet
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ValueSet.scope
  l: extension-ValueSet.scope
target version:
  v: 0.1.0
element:
  code:
    v: ValueSet.scope
  display:
    v: scope
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ValueSet.scope` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`. Element `ValueSet.scope` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ValueSet.scope.inclusionCriteria
  display:
    v: inclusionCriteria
  target:
    code:
      v: Extension.extension:inclusionCriteria
    equivalence:
      v: wider
    comment:
      v: Element `ValueSet.scope.inclusionCriteria` is part of an existing definition because parent element `ValueSet.scope` requires a cross-version extension. Element `ValueSet.scope.inclusionCriteria` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`. Element `ValueSet.scope.inclusionCriteria` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ValueSet.scope.exclusionCriteria
  display:
    v: exclusionCriteria
  target:
    code:
      v: Extension.extension:exclusionCriteria
    equivalence:
      v: wider
    comment:
      v: Element `ValueSet.scope.exclusionCriteria` is part of an existing definition because parent element `ValueSet.scope` requires a cross-version extension. Element `ValueSet.scope.exclusionCriteria` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`. Element `ValueSet.scope.exclusionCriteria` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).