R3-OperationDefinition-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R3-OperationDefinition-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R3-OperationDefinition-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/OperationDefinition|3.0.2 to OperationDefinitionversion: 4.0.1) Source Code Relationship Target Code Comment OperationDefinition.meta (meta) is equivalent to OperationDefinition.meta Element `OperationDefinition.meta` is mapped to FHIR R4 element `OperationDefinition.meta` as `Equivalent`. OperationDefinition.implicitRules (implicitRules) is equivalent to OperationDefinition.implicitRules Element `OperationDefinition.implicitRules` is mapped to FHIR R4 element `OperationDefinition.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. OperationDefinition.language (language) is equivalent to OperationDefinition.language Element `OperationDefinition.language` is mapped to FHIR R4 element `OperationDefinition.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…
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-r3.r4
        l: hl7.fhir.uv.xver-r3.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-r3.r4
        l: hl7.fhir.uv.xver-r3.r4
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R3-OperationDefinition-element-map-to-R4
  l: R3-OperationDefinition-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R3OperationDefinitionElementMapToR4
title:
  v: Cross-version mapping for FHIR STU3 OperationDefinition to FHIR R4 OperationDefinition
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:03:24.073663-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 STU3 OperationDefinition 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/3.0
  l: http://hl7.org/fhir/3.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/OperationDefinition
    l: OperationDefinition
  source version:
    v: 3.0.2
  target:
    v: http://hl7.org/fhir/StructureDefinition/OperationDefinition
    l: OperationDefinition
  target version:
    v: 4.0.1
  element:
    code:
      v: OperationDefinition.meta
    display:
      v: meta
    target:
      code:
        v: OperationDefinition.meta
      display:
        v: OperationDefinition.meta
      equivalence:
        v: equivalent
      comment:
        v: Element `OperationDefinition.meta` is mapped to FHIR R4 element `OperationDefinition.meta` as `Equivalent`.
  element:
    code:
      v: OperationDefinition.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: OperationDefinition.implicitRules
      display:
        v: OperationDefinition.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element `OperationDefinition.implicitRules` is mapped to FHIR R4 element `OperationDefinition.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.
  element:
    code:
      v: OperationDefinition.language
    display:
      v: language
    target:
      code:
        v: OperationDefinition.language
      display:
        v: OperationDefinition.language
      equivalence:
        v: equivalent
      comment:
        v: Element `OperationDefinition.language` is mapped to FHIR R4 element `OperationDefinition.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: OperationDefinition.text
    display:
      v: text
    target:
      code:
        v: OperationDefinition.text
      display:
        v: OperationDefinition.text
      equivalence:
        v: equivalent
      comment:
        v: Element `OperationDefinition.text` is mapped to FHIR R4 element `OperationDefinition.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.
  element:
    code:
      v: OperationDefinition.contained
    display:
      v: contained
    target:
      code:
        v: OperationDefinition.contained
      display:
        v: OperationDefinition.contained
      equivalence:
        v: equivalent
      comment:
        v: Element `OperationDefinition.contained` is mapped to FHIR R4 element `OperationDefinition.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.
  element:
    code:
      v: OperationDefinition.url
    display:
      v: url
    target:
      code:
        v: OperationDefinition.url
      display:
        v: OperationDefinition.url
      equivalence:
        v: equivalent
      comment:
        v: Element `OperationDefinition.url` is mapped to FHIR R4 element `OperationDefinition.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.
  element:
    code:
      v: OperationDefinition.version
    display:
      v: version
    target:
      code:
        v: OperationDefinition.version
      display:
        v: OperationDefinition.version
      equivalence:
        v: equivalent
      comment:
        v: Element `OperationDefinition.version` is mapped to FHIR R4 element `OperationDefinition.version` as `Equivalent`. There may be different operation definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a refrence to a particular business version of the operation definition with the format [url]|[version].
  element:
    code:
      v: OperationDefinition.name
    display:
      v: name
    target:
      code:
        v: OperationDefinition.name
      display:
        v: OperationDefinition.name
      equivalence:
        v: equivalent
      comment:
        v: Element `OperationDefinition.name` is mapped to FHIR R4 element `OperationDefinition.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.

code:
  v: OperationDefinition.status
display:
  v: status
target:
  code:
    v: OperationDefinition.status
  display:
    v: OperationDefinition.status
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.status` is mapped to FHIR R4 element `OperationDefinition.status` as `Equivalent`. Allows filtering of operation definitions that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use a retired operation definition without due consideration.

code:
  v: OperationDefinition.kind
display:
  v: kind
target:
  code:
    v: OperationDefinition.kind
  display:
    v: OperationDefinition.kind
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.kind` is mapped to FHIR R4 element `OperationDefinition.kind` as `Equivalent`. Named queries are invoked differently, and have different capabilities.

code:
  v: OperationDefinition.experimental
display:
  v: experimental
target:
  code:
    v: OperationDefinition.experimental
  display:
    v: OperationDefinition.experimental
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.experimental` is mapped to FHIR R4 element `OperationDefinition.experimental` as `Equivalent`. Allows filtering of operation definition that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use an experimental operation definition in production.

code:
  v: OperationDefinition.date
display:
  v: date
target:
  code:
    v: OperationDefinition.date
  display:
    v: OperationDefinition.date
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.date` is mapped to FHIR R4 element `OperationDefinition.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 operation definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.

code:
  v: OperationDefinition.publisher
display:
  v: publisher
target:
  code:
    v: OperationDefinition.publisher
  display:
    v: OperationDefinition.publisher
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.publisher` is mapped to FHIR R4 element `OperationDefinition.publisher` as `Equivalent`. Usually an organization, but may be an individual. The publisher (or steward) of the operation definition is the organization or individual primarily responsible for the maintenance and upkeep of the operation 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 operation definition. This item SHOULD be populated unless the information is available from context.

code:
  v: OperationDefinition.contact
display:
  v: contact
target:
  code:
    v: OperationDefinition.contact
  display:
    v: OperationDefinition.contact
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.contact` is mapped to FHIR R4 element `OperationDefinition.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.

code:
  v: OperationDefinition.description
display:
  v: description
target:
  code:
    v: OperationDefinition.description
  display:
    v: OperationDefinition.description
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.description` is mapped to FHIR R4 element `OperationDefinition.description` as `Equivalent`. This description can be used to capture details such as why the operation 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 operation 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:
  v: OperationDefinition.useContext
display:
  v: useContext
target:
  code:
    v: OperationDefinition.useContext
  display:
    v: OperationDefinition.useContext
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.useContext` is mapped to FHIR R4 element `OperationDefinition.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.

code:
  v: OperationDefinition.jurisdiction
display:
  v: jurisdiction
target:
  code:
    v: OperationDefinition.jurisdiction
  display:
    v: OperationDefinition.jurisdiction
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.jurisdiction` is mapped to FHIR R4 element `OperationDefinition.jurisdiction` as `Equivalent`. It may be possible for the operation definition to be used in jurisdictions other than those for which it was originally designed or intended.

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

code:
  v: OperationDefinition.idempotent
display:
  v: idempotent
target:
  code:
    v: OperationDefinition.affectsState
  display:
    v: OperationDefinition.affectsState
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.idempotent` is mapped to FHIR R4 element `OperationDefinition.affectsState` as `Equivalent`.

code:
  v: OperationDefinition.code
display:
  v: code
target:
  code:
    v: OperationDefinition.code
  display:
    v: OperationDefinition.code
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.code` is mapped to FHIR R4 element `OperationDefinition.code` as `Equivalent`. The code does not include the '$' prefix that is always included in the URL when the operation is invoked.

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

code:
  v: OperationDefinition.base
display:
  v: base
target:
  code:
    v: OperationDefinition.base
  display:
    v: OperationDefinition.base
  equivalence:
    v: wider
  comment:
    v: Element `OperationDefinition.base` is mapped to FHIR R4 element `OperationDefinition.base` as `SourceIsBroaderThanTarget`. The mappings for `OperationDefinition.base` do not cover the following types: Reference. The mappings for `OperationDefinition.base` do not cover the following types based on type expansion: display, identifier, reference. A constrained profile can make optional parameters required or not used and clarify documentation.

code:
  v: OperationDefinition.resource
display:
  v: resource
target:
  code:
    v: OperationDefinition.resource
  display:
    v: OperationDefinition.resource
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.resource` is mapped to FHIR R4 element `OperationDefinition.resource` as `SourceIsNarrowerThanTarget`. The mappings for `OperationDefinition.resource` do not allow expression of the necessary codes, per the bindings on the source and target. If the type is an abstract resource ("Resource" or "DomainResource") then the operation can be invoked on any concrete specialization.

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

code:
  v: OperationDefinition.type
display:
  v: type
target:
  code:
    v: OperationDefinition.type
  display:
    v: OperationDefinition.type
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.type` is mapped to FHIR R4 element `OperationDefinition.type` as `Equivalent`.

code:
  v: OperationDefinition.instance
display:
  v: instance
target:
  code:
    v: OperationDefinition.instance
  display:
    v: OperationDefinition.instance
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.instance` is mapped to FHIR R4 element `OperationDefinition.instance` as `Equivalent`.

code:
  v: OperationDefinition.parameter
display:
  v: parameter
target:
  code:
    v: OperationDefinition.parameter
  display:
    v: OperationDefinition.parameter
  equivalence:
    v: wider
  comment:
    v: Element `OperationDefinition.parameter` is mapped to FHIR R4 element `OperationDefinition.parameter` as `Equivalent`. Query Definitions only have one output parameter, named "result". This may not be described, but can be to allow a profile to be defined.

code:
  v: OperationDefinition.parameter.name
display:
  v: name
target:
  code:
    v: OperationDefinition.parameter.name
  display:
    v: OperationDefinition.parameter.name
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.parameter.name` is mapped to FHIR R4 element `OperationDefinition.parameter.name` as `Equivalent`. This name must be a token (start with a letter in a..z, and only contain letters, numerals, and underscore. Note that for search parameters (type = string, with a search type), the name may be altered by the search modifiers.

code:
  v: OperationDefinition.parameter.use
display:
  v: use
target:
  code:
    v: OperationDefinition.parameter.use
  display:
    v: OperationDefinition.parameter.use
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.parameter.use` is mapped to FHIR R4 element `OperationDefinition.parameter.use` as `Equivalent`. If a parameter name is used for both an input and an output parameter, the parameter should be defined twice.

code:
  v: OperationDefinition.parameter.min
display:
  v: min
target:
  code:
    v: OperationDefinition.parameter.min
  display:
    v: OperationDefinition.parameter.min
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.parameter.min` is mapped to FHIR R4 element `OperationDefinition.parameter.min` as `Equivalent`.

code:
  v: OperationDefinition.parameter.max
display:
  v: max
target:
  code:
    v: OperationDefinition.parameter.max
  display:
    v: OperationDefinition.parameter.max
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.parameter.max` is mapped to FHIR R4 element `OperationDefinition.parameter.max` as `Equivalent`.

code:
  v: OperationDefinition.parameter.documentation
display:
  v: documentation
target:
  code:
    v: OperationDefinition.parameter.documentation
  display:
    v: OperationDefinition.parameter.documentation
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.parameter.documentation` is mapped to FHIR R4 element `OperationDefinition.parameter.documentation` as `Equivalent`.

code:
  v: OperationDefinition.parameter.type
display:
  v: type
target:
  code:
    v: OperationDefinition.parameter.type
  display:
    v: OperationDefinition.parameter.type
  equivalence:
    v: wider
  comment:
    v: Element `OperationDefinition.parameter.type` is mapped to FHIR R4 element `OperationDefinition.parameter.type` as `RelatedTo`. The mappings for `OperationDefinition.parameter.type` do not allow expression of the necessary codes, per the bindings on the source and target. if there is no stated parameter, then the parameter is a multi-part parameter; type and must have at least one part defined.

code:
  v: OperationDefinition.parameter.searchType
display:
  v: searchType
target:
  code:
    v: OperationDefinition.parameter.searchType
  display:
    v: OperationDefinition.parameter.searchType
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.parameter.searchType` is mapped to FHIR R4 element `OperationDefinition.parameter.searchType` as `SourceIsNarrowerThanTarget`. The mappings for `OperationDefinition.parameter.searchType` do not allow expression of the necessary codes, per the bindings on the source and target.

code:
  v: OperationDefinition.parameter.profile
display:
  v: profile
target:
  code:
    v: OperationDefinition.parameter.targetProfile
  display:
    v: OperationDefinition.parameter.targetProfile
  equivalence:
    v: relatedto
  comment:
    v: Element `OperationDefinition.parameter.profile` is mapped to FHIR R4 element `OperationDefinition.parameter.targetProfile` as `RelatedTo`. The mappings for `OperationDefinition.parameter.profile` do not cover the following types: Reference. The mappings for `OperationDefinition.parameter.profile` do not cover the following types based on type expansion: display, identifier, reference.

code:
  v: OperationDefinition.parameter.binding
display:
  v: binding
target:
  code:
    v: OperationDefinition.parameter.binding
  display:
    v: OperationDefinition.parameter.binding
  equivalence:
    v: wider
  comment:
    v: Element `OperationDefinition.parameter.binding` is mapped to FHIR R4 element `OperationDefinition.parameter.binding` as `Equivalent`.

code:
  v: OperationDefinition.parameter.binding.strength
display:
  v: strength
target:
  code:
    v: OperationDefinition.parameter.binding.strength
  display:
    v: OperationDefinition.parameter.binding.strength
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.parameter.binding.strength` is mapped to FHIR R4 element `OperationDefinition.parameter.binding.strength` as `Equivalent`. For further discussion, see [Using Terminologies](https://hl7.org/fhir/terminologies.html).

code:
  v: OperationDefinition.parameter.binding.valueSet[x]
display:
  v: valueSet[x]
target:
  code:
    v: OperationDefinition.parameter.binding.valueSet
  display:
    v: OperationDefinition.parameter.binding.valueSet
  equivalence:
    v: wider
  comment:
    v: Element `OperationDefinition.parameter.binding.valueSet[x]` is mapped to FHIR R4 element `OperationDefinition.parameter.binding.valueSet` as `SourceIsBroaderThanTarget`. The mappings for `OperationDefinition.parameter.binding.valueSet[x]` do not cover the following types: Reference. The mappings for `OperationDefinition.parameter.binding.valueSet[x]` do not cover the following types based on type expansion: display, identifier, reference. For value sets with a referenceResource, the display can contain the value set description. The reference may be version-specific or not.

code:
  v: OperationDefinition.parameter.part
display:
  v: part
target:
  code:
    v: OperationDefinition.parameter.part
  display:
    v: OperationDefinition.parameter.part
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.parameter.part` is mapped to FHIR R4 element `OperationDefinition.parameter.part` as `Equivalent`. Query Definitions only have one output parameter, named "result". This may not be described, but can be to allow a profile to be defined.

code:
  v: OperationDefinition.overload
display:
  v: overload
target:
  code:
    v: OperationDefinition.overload
  display:
    v: OperationDefinition.overload
  equivalence:
    v: wider
  comment:
    v: Element `OperationDefinition.overload` is mapped to FHIR R4 element `OperationDefinition.overload` as `Equivalent`. The combinations are suggestions as to which sets of parameters to use together, but the combinations are not intended to be authoritative.

code:
  v: OperationDefinition.overload.parameterName
display:
  v: parameterName
target:
  code:
    v: OperationDefinition.overload.parameterName
  display:
    v: OperationDefinition.overload.parameterName
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.overload.parameterName` is mapped to FHIR R4 element `OperationDefinition.overload.parameterName` as `Equivalent`.

code:
  v: OperationDefinition.overload.comment
display:
  v: comment
target:
  code:
    v: OperationDefinition.overload.comment
  display:
    v: OperationDefinition.overload.comment
  equivalence:
    v: equivalent
  comment:
    v: Element `OperationDefinition.overload.comment` is mapped to FHIR R4 element `OperationDefinition.overload.comment` as `Equivalent`.

source:
  v: http://hl7.org/fhir/StructureDefinition/OperationDefinition
  l: OperationDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-OperationDefinition.base
  l: extension-OperationDefinition.base
target version:
  v: 0.1.0
element:
  code:
    v: OperationDefinition.base
  display:
    v: base
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `OperationDefinition.base` is mapped to FHIR R4 element `OperationDefinition.base` as `SourceIsBroaderThanTarget`. The mappings for `OperationDefinition.base` do not cover the following types: Reference. The mappings for `OperationDefinition.base` do not cover the following types based on type expansion: display, identifier, reference. A constrained profile can make optional parameters required or not used and clarify documentation.

source:
  v: http://hl7.org/fhir/StructureDefinition/OperationDefinition
  l: OperationDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-OperationDefinition.parameter.type
  l: extension-OperationDefinition.parameter.type
target version:
  v: 0.1.0
element:
  code:
    v: OperationDefinition.parameter.type
  display:
    v: type
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `OperationDefinition.parameter.type` is mapped to FHIR R4 element `OperationDefinition.parameter.type` as `RelatedTo`. The mappings for `OperationDefinition.parameter.type` do not allow expression of the necessary codes, per the bindings on the source and target. if there is no stated parameter, then the parameter is a multi-part parameter; type and must have at least one part defined.

source:
  v: http://hl7.org/fhir/StructureDefinition/OperationDefinition
  l: OperationDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-OperationDefinition.parameter.profile
  l: extension-OperationDefinition.parameter.profile
target version:
  v: 0.1.0
element:
  code:
    v: OperationDefinition.parameter.profile
  display:
    v: profile
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `OperationDefinition.parameter.profile` is mapped to FHIR R4 element `OperationDefinition.parameter.targetProfile` as `RelatedTo`. The mappings for `OperationDefinition.parameter.profile` do not cover the following types: Reference. The mappings for `OperationDefinition.parameter.profile` do not cover the following types based on type expansion: display, identifier, reference.

source:
  v: http://hl7.org/fhir/StructureDefinition/OperationDefinition
  l: OperationDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-OperationDefinition.parameter.binding.valueSet
  l: extension-OperationDefinition.parameter.binding.valueSet
target version:
  v: 0.1.0
element:
  code:
    v: OperationDefinition.parameter.binding.valueSet[x]
  display:
    v: valueSet[x]
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `OperationDefinition.parameter.binding.valueSet[x]` is mapped to FHIR R4 element `OperationDefinition.parameter.binding.valueSet` as `SourceIsBroaderThanTarget`. The mappings for `OperationDefinition.parameter.binding.valueSet[x]` do not cover the following types: Reference. The mappings for `OperationDefinition.parameter.binding.valueSet[x]` do not cover the following types based on type expansion: display, identifier, reference. For value sets with a referenceResource, the display can contain the value set description. The reference may be version-specific or not.