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 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). OperationDefinition.text (text) is equivalent to OperationDefinition.text 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. OperationDefinition.contained (contained) is equivalent to OperationDefinition.contained 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. OperationDefinition.url (url) is equivalent to OperationDefinition.url 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. OperationDefinition.version (version) is equivalent to OperationDefinition.version 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]. OperationDefinition.name (name) is equivalent to OperationDefinition.name 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. OperationDefinition.status (status) is equivalent to OperationDefinition.status 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. OperationDefinition.kind (kind) is equivalent to OperationDefinition.kind Element `OperationDefinition.kind` is mapped to FHIR R4 element `OperationDefinition.kind` as `Equivalent`. Named queries are invoked differently, and have different capabilities. OperationDefinition.experimental (experimental) is equivalent to OperationDefinition.experimental 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. OperationDefinition.date (date) is equivalent to OperationDefinition.date 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. OperationDefinition.publisher (publisher) is equivalent to OperationDefinition.publisher 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. OperationDefinition.contact (contact) is equivalent to OperationDefinition.contact 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. OperationDefinition.description (description) is equivalent to OperationDefinition.description 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). OperationDefinition.useContext (useContext) is equivalent to OperationDefinition.useContext 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. OperationDefinition.jurisdiction (jurisdiction) is equivalent to OperationDefinition.jurisdiction 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. OperationDefinition.purpose (purpose) is equivalent to OperationDefinition.purpose 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. OperationDefinition.idempotent (idempotent) is equivalent to OperationDefinition.affectsState Element `OperationDefinition.idempotent` is mapped to FHIR R4 element `OperationDefinition.affectsState` as `Equivalent`. OperationDefinition.code (code) is equivalent to OperationDefinition.code 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. OperationDefinition.comment (comment) is equivalent to OperationDefinition.comment Element `OperationDefinition.comment` is mapped to FHIR R4 element `OperationDefinition.comment` as `Equivalent`. OperationDefinition.base (base) maps to wider concept OperationDefinition.base 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. OperationDefinition.resource (resource) is equivalent to OperationDefinition.resource 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. OperationDefinition.system (system) is equivalent to OperationDefinition.system Element `OperationDefinition.system` is mapped to FHIR R4 element `OperationDefinition.system` as `Equivalent`. OperationDefinition.type (type) is equivalent to OperationDefinition.type Element `OperationDefinition.type` is mapped to FHIR R4 element `OperationDefinition.type` as `Equivalent`. OperationDefinition.instance (instance) is equivalent to OperationDefinition.instance Element `OperationDefinition.instance` is mapped to FHIR R4 element `OperationDefinition.instance` as `Equivalent`. OperationDefinition.parameter (parameter) maps to wider concept OperationDefinition.parameter 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. OperationDefinition.parameter.name (name) is equivalent to OperationDefinition.parameter.name 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. OperationDefinition.parameter.use (use) is equivalent to OperationDefinition.parameter.use 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. OperationDefinition.parameter.min (min) is equivalent to OperationDefinition.parameter.min Element `OperationDefinition.parameter.min` is mapped to FHIR R4 element `OperationDefinition.parameter.min` as `Equivalent`. OperationDefinition.parameter.max (max) is equivalent to OperationDefinition.parameter.max Element `OperationDefinition.parameter.max` is mapped to FHIR R4 element `OperationDefinition.parameter.max` as `Equivalent`. OperationDefinition.parameter.documentation (documentation) is equivalent to OperationDefinition.parameter.documentation Element `OperationDefinition.parameter.documentation` is mapped to FHIR R4 element `OperationDefinition.parameter.documentation` as `Equivalent`. OperationDefinition.parameter.type (type) maps to wider concept OperationDefinition.parameter.type 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. OperationDefinition.parameter.searchType (searchType) is equivalent to OperationDefinition.parameter.searchType 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. OperationDefinition.parameter.profile (profile) is related to OperationDefinition.parameter.targetProfile 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. OperationDefinition.parameter.binding (binding) maps to wider concept OperationDefinition.parameter.binding Element `OperationDefinition.parameter.binding` is mapped to FHIR R4 element `OperationDefinition.parameter.binding` as `Equivalent`. OperationDefinition.parameter.binding.strength (strength) is equivalent to OperationDefinition.parameter.binding.strength 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). OperationDefinition.parameter.binding.valueSet[x] (valueSet[x]) maps to wider concept OperationDefinition.parameter.binding.valueSet 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. OperationDefinition.parameter.part (part) is equivalent to OperationDefinition.parameter.part 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. OperationDefinition.overload (overload) maps to wider concept OperationDefinition.overload 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. OperationDefinition.overload.parameterName (parameterName) is equivalent to OperationDefinition.overload.parameterName Element `OperationDefinition.overload.parameterName` is mapped to FHIR R4 element `OperationDefinition.overload.parameterName` as `Equivalent`. OperationDefinition.overload.comment (comment) is equivalent to OperationDefinition.overload.comment Element `OperationDefinition.overload.comment` is mapped to FHIR R4 element `OperationDefinition.overload.comment` as `Equivalent`. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/OperationDefinition|3.0.2 to STU3: base additional typesversion: 0.1.0) Source Code Relationship Target Code Comment OperationDefinition.base (base) is equivalent to Extension (STU3: base additional types) 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. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/OperationDefinition|3.0.2 to STU3: type additional codesversion: 0.1.0) Source Code Relationship Target Code Comment OperationDefinition.parameter.type (type) is equivalent to Extension (STU3: type additional codes) 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. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/OperationDefinition|3.0.2 to STU3: Profile on the type additional typesversion: 0.1.0) Source Code Relationship Target Code Comment OperationDefinition.parameter.profile (profile) maps to wider concept Extension (STU3: Profile on the type additional types) 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. Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/OperationDefinition|3.0.2 to STU3: Source of value set additional typesversion: 0.1.0) Source Code Relationship Target Code Comment OperationDefinition.parameter.binding.valueSet[x] (valueSet[x]) maps to wider concept Extension (STU3: Source of value set additional types) 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.
Cross-version mapping for FHIR STU3 OperationDefinition to FHIR R4 OperationDefinition
This ConceptMap represents cross-version mappings for elements from a FHIR STU3 OperationDefinition to FHIR R4.
Element `OperationDefinition.meta` is mapped to FHIR R4 element `OperationDefinition.meta` as `Equivalent`.
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 `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 `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 `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 `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 `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 `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.
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.
Element `OperationDefinition.kind` is mapped to FHIR R4 element `OperationDefinition.kind` as `Equivalent`. Named queries are invoked differently, and have different capabilities.
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.
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.
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.
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.
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).
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.
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.
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.
Element `OperationDefinition.idempotent` is mapped to FHIR R4 element `OperationDefinition.affectsState` as `Equivalent`.
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.
Element `OperationDefinition.comment` is mapped to FHIR R4 element `OperationDefinition.comment` as `Equivalent`.
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.
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.
Element `OperationDefinition.system` is mapped to FHIR R4 element `OperationDefinition.system` as `Equivalent`.
Element `OperationDefinition.type` is mapped to FHIR R4 element `OperationDefinition.type` as `Equivalent`.
Element `OperationDefinition.instance` is mapped to FHIR R4 element `OperationDefinition.instance` as `Equivalent`.
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.
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.
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.
Element `OperationDefinition.parameter.min` is mapped to FHIR R4 element `OperationDefinition.parameter.min` as `Equivalent`.
Element `OperationDefinition.parameter.max` is mapped to FHIR R4 element `OperationDefinition.parameter.max` as `Equivalent`.
Element `OperationDefinition.parameter.documentation` is mapped to FHIR R4 element `OperationDefinition.parameter.documentation` as `Equivalent`.
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.
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.
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.
Element `OperationDefinition.parameter.binding` is mapped to FHIR R4 element `OperationDefinition.parameter.binding` as `Equivalent`.
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).
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.
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.
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.
Element `OperationDefinition.overload.parameterName` is mapped to FHIR R4 element `OperationDefinition.overload.parameterName` as `Equivalent`.
Element `OperationDefinition.overload.comment` is mapped to FHIR R4 element `OperationDefinition.overload.comment` as `Equivalent`.