FHIR IG analytics| Package | hl7.fhir.uv.xver-r4b.r4 |
| Resource Type | ConceptMap |
| Id | ConceptMap-R4B-OperationDefinition-element-map-to-R4.json |
| FHIR Version | R4 |
| Source | http://hl7.org/fhir/uv/xver-r4b.r4/0.1.0/ConceptMap-R4B-OperationDefinition-element-map-to-R4.html |
| URL | http://hl7.org/fhir/uv/xver/ConceptMap/R4B-OperationDefinition-element-map-to-R4 |
| Version | 0.1.0 |
| Status | active |
| Date | 2026-03-17T16:03:46.1904284-05:00 |
| Name | R4BOperationDefinitionElementMapToR4 |
| Title | Cross-version mapping for FHIR R4B OperationDefinition to FHIR R4 OperationDefinition |
| Realm | uv |
| Authority | hl7 |
| Description | This ConceptMap represents cross-version mappings for elements from a FHIR R4B OperationDefinition to FHIR R4. |
No resources found
| StructureDefinition | ||
| hl7.fhir.uv.xver-r4b.r4#0.1.0 | extension-OperationDefinition.parameter.type | R4B: type additional codes |
Note: links and images are rebased to the (stated) source
Generated Narrative: ConceptMap R4B-OperationDefinition-element-map-to-R4
Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/4.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/OperationDefinition|4.3.0 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. |
| 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 information 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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. |
| 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. 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. |
| 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 reference 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 alphanumeric type name to ensure that it is machine-processing friendly. |
| OperationDefinition.title (title) | is equivalent to | OperationDefinition.title | Element `OperationDefinition.title` is mapped to FHIR R4 element `OperationDefinition.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc. |
| 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 versus not. |
| 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 definitions that are appropriate for use versus not. |
| 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 operation definition is presumed to be the predominant language in the place the operation definition 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 that 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.affectsState (affectsState) | is equivalent to | OperationDefinition.affectsState | Element `OperationDefinition.affectsState` is mapped to FHIR R4 element `OperationDefinition.affectsState` as `Equivalent`. What http methods can be used for the operation depends on the .affectsState value and whether the input parameters are primitive or complex: 1. Servers SHALL support POST method for all operations. 2. Servers SHALL support GET method if all the parameters for the operation are primitive or there are no parameters and the operation has affectsState = false. |
| OperationDefinition.code (code) | is equivalent to | OperationDefinition.code | Element `OperationDefinition.code` is mapped to FHIR R4 element `OperationDefinition.code` as `Equivalent`. |
| OperationDefinition.comment (comment) | is equivalent to | OperationDefinition.comment | Element `OperationDefinition.comment` is mapped to FHIR R4 element `OperationDefinition.comment` as `Equivalent`. |
| OperationDefinition.base (base) | is equivalent to | OperationDefinition.base | Element `OperationDefinition.base` is mapped to FHIR R4 element `OperationDefinition.base` as `Equivalent`. 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.inputProfile (inputProfile) | is equivalent to | OperationDefinition.inputProfile | Element `OperationDefinition.inputProfile` is mapped to FHIR R4 element `OperationDefinition.inputProfile` as `Equivalent`. If present the profile shall not conflict with what is specified in the parameters in the operation definition (max/min etc.), though it may provide additional constraints. The constraints expressed in the profile apply whether the operation is invoked by a POST wih parameters or not. |
| OperationDefinition.outputProfile (outputProfile) | is equivalent to | OperationDefinition.outputProfile | Element `OperationDefinition.outputProfile` is mapped to FHIR R4 element `OperationDefinition.outputProfile` as `Equivalent`. If present the profile shall not conflict with what is specified in the parameters in the operation definition (max/min etc.), though it may provide additional constraints. The constraints expressed in the profile apply whether the operation is invoked by a POST wih parameters or not. |
| 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 might 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.targetProfile (targetProfile) | is equivalent to | OperationDefinition.parameter.targetProfile | Element `OperationDefinition.parameter.targetProfile` is mapped to FHIR R4 element `OperationDefinition.parameter.targetProfile` as `Equivalent`. Often, these profiles are the base definitions from the spec (e.g. http://hl7.org/fhir/StructureDefinition/Patient). |
| OperationDefinition.parameter.searchType (searchType) | is equivalent to | OperationDefinition.parameter.searchType | Element `OperationDefinition.parameter.searchType` is mapped to FHIR R4 element `OperationDefinition.parameter.searchType` as `Equivalent`. |
| 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 (valueSet) | is equivalent to | OperationDefinition.parameter.binding.valueSet | Element `OperationDefinition.parameter.binding.valueSet` is mapped to FHIR R4 element `OperationDefinition.parameter.binding.valueSet` as `Equivalent`. For value sets with a referenceResource, the display can contain the value set description. The reference may be version-specific or not. |
| OperationDefinition.parameter.referencedFrom (referencedFrom) | maps to wider concept | OperationDefinition.parameter.referencedFrom | Element `OperationDefinition.parameter.referencedFrom` is mapped to FHIR R4 element `OperationDefinition.parameter.referencedFrom` as `Equivalent`. Resolution applies if the referenced parameter exists. |
| OperationDefinition.parameter.referencedFrom.source (source) | is equivalent to | OperationDefinition.parameter.referencedFrom.source | Element `OperationDefinition.parameter.referencedFrom.source` is mapped to FHIR R4 element `OperationDefinition.parameter.referencedFrom.source` as `Equivalent`. |
| OperationDefinition.parameter.referencedFrom.sourceId (sourceId) | is equivalent to | OperationDefinition.parameter.referencedFrom.sourceId | Element `OperationDefinition.parameter.referencedFrom.sourceId` is mapped to FHIR R4 element `OperationDefinition.parameter.referencedFrom.sourceId` as `Equivalent`. |
| 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 might 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|4.3.0 to R4B: type additional codesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| OperationDefinition.parameter.type (type) | is equivalent to | Extension (R4B: 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. |
{
"resourceType": "ConceptMap",
"id": "R4B-OperationDefinition-element-map-to-R4",
"text": {
"status": "generated",
"div": "<!-- snip (see above) -->"
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "fhir"
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger": 0,
"_valueInteger": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r4"
}
]
}
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode": "trial-use",
"_valueCode": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r4"
}
]
}
}
],
"url": "http://hl7.org/fhir/uv/xver/ConceptMap/R4B-OperationDefinition-element-map-to-R4",
"version": "0.1.0",
"name": "R4BOperationDefinitionElementMapToR4",
"title": "Cross-version mapping for FHIR R4B OperationDefinition to FHIR R4 OperationDefinition",
"status": "active",
"experimental": false,
"date": "2026-03-17T16:03:46.1904284-05:00",
"contact": [
{
"name": "FHIR Infrastructure",
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/fiwg"
}
]
}
],
"description": "This ConceptMap represents cross-version mappings for elements from a FHIR R4B OperationDefinition to FHIR R4.",
"jurisdiction": [
{
"coding": [
{
"system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code": "001",
"display": "World"
}
]
}
],
"sourceCanonical": "http://hl7.org/fhir/4.3",
"targetUri": "http://hl7.org/fhir/4.0",
"group": [
{
"source": "http://hl7.org/fhir/StructureDefinition/OperationDefinition",
"sourceVersion": "4.3.0",
"target": "http://hl7.org/fhir/StructureDefinition/OperationDefinition",
"targetVersion": "4.0.1",
"element": [
{
"code": "OperationDefinition.meta",
"display": "meta",
"target": [
{
"code": "OperationDefinition.meta",
"display": "OperationDefinition.meta",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.meta` is mapped to FHIR R4 element `OperationDefinition.meta` as `Equivalent`."
}
]
},
{
"code": "OperationDefinition.implicitRules",
"display": "implicitRules",
"target": [
{
"code": "OperationDefinition.implicitRules",
"display": "OperationDefinition.implicitRules",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.implicitRules` is mapped to FHIR R4 element `OperationDefinition.implicitRules` as `Equivalent`.\nAsserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc."
}
]
},
{
"code": "OperationDefinition.language",
"display": "language",
"target": [
{
"code": "OperationDefinition.language",
"display": "OperationDefinition.language",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.language` is mapped to FHIR R4 element `OperationDefinition.language` as `Equivalent`.\nLanguage is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute)."
}
]
},
{
"code": "OperationDefinition.text",
"display": "text",
"target": [
{
"code": "OperationDefinition.text",
"display": "OperationDefinition.text",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.text` is mapped to FHIR R4 element `OperationDefinition.text` as `Equivalent`.\nContained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a \"text blob\" or where text is additionally entered raw or narrated and encoded information is added later."
}
]
},
{
"code": "OperationDefinition.contained",
"display": "contained",
"target": [
{
"code": "OperationDefinition.contained",
"display": "OperationDefinition.contained",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.contained` is mapped to FHIR R4 element `OperationDefinition.contained` as `Equivalent`.\nThis should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels."
}
]
},
{
"code": "OperationDefinition.url",
"display": "url",
"target": [
{
"code": "OperationDefinition.url",
"display": "OperationDefinition.url",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.url` is mapped to FHIR R4 element `OperationDefinition.url` as `Equivalent`.\nCan be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.\n\nThe determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions). \n\nIn some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found."
}
]
},
{
"code": "OperationDefinition.version",
"display": "version",
"target": [
{
"code": "OperationDefinition.version",
"display": "OperationDefinition.version",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.version` is mapped to FHIR R4 element `OperationDefinition.version` as `Equivalent`.\nThere 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 reference to a particular business version of the operation definition with the format [url]|[version]."
}
]
},
{
"code": "OperationDefinition.name",
"display": "name",
"target": [
{
"code": "OperationDefinition.name",
"display": "OperationDefinition.name",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.name` is mapped to FHIR R4 element `OperationDefinition.name` as `Equivalent`.\nThe name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly."
}
]
},
{
"code": "OperationDefinition.title",
"display": "title",
"target": [
{
"code": "OperationDefinition.title",
"display": "OperationDefinition.title",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.title` is mapped to FHIR R4 element `OperationDefinition.title` as `Equivalent`.\nThis name does not need to be machine-processing friendly and may contain punctuation, white-space, etc."
}
]
},
{
"code": "OperationDefinition.status",
"display": "status",
"target": [
{
"code": "OperationDefinition.status",
"display": "OperationDefinition.status",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.status` is mapped to FHIR R4 element `OperationDefinition.status` as `Equivalent`.\nAllows filtering of operation definitions that are appropriate for use versus not."
}
]
},
{
"code": "OperationDefinition.kind",
"display": "kind",
"target": [
{
"code": "OperationDefinition.kind",
"display": "OperationDefinition.kind",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.kind` is mapped to FHIR R4 element `OperationDefinition.kind` as `Equivalent`.\nNamed queries are invoked differently, and have different capabilities."
}
]
},
{
"code": "OperationDefinition.experimental",
"display": "experimental",
"target": [
{
"code": "OperationDefinition.experimental",
"display": "OperationDefinition.experimental",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.experimental` is mapped to FHIR R4 element `OperationDefinition.experimental` as `Equivalent`.\nAllows filtering of operation definitions that are appropriate for use versus not."
}
]
},
{
"code": "OperationDefinition.date",
"display": "date",
"target": [
{
"code": "OperationDefinition.date",
"display": "OperationDefinition.date",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.date` is mapped to FHIR R4 element `OperationDefinition.date` as `Equivalent`.\nNote that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the operation definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource."
}
]
},
{
"code": "OperationDefinition.publisher",
"display": "publisher",
"target": [
{
"code": "OperationDefinition.publisher",
"display": "OperationDefinition.publisher",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.publisher` is mapped to FHIR R4 element `OperationDefinition.publisher` as `Equivalent`.\nUsually 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": "OperationDefinition.contact",
"display": "contact",
"target": [
{
"code": "OperationDefinition.contact",
"display": "OperationDefinition.contact",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.contact` is mapped to FHIR R4 element `OperationDefinition.contact` as `Equivalent`.\nMay be a web site, an email address, a telephone number, etc."
}
]
},
{
"code": "OperationDefinition.description",
"display": "description",
"target": [
{
"code": "OperationDefinition.description",
"display": "OperationDefinition.description",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.description` is mapped to FHIR R4 element `OperationDefinition.description` as `Equivalent`.\nThis 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 operation definition is presumed to be the predominant language in the place the operation definition was created)."
}
]
},
{
"code": "OperationDefinition.useContext",
"display": "useContext",
"target": [
{
"code": "OperationDefinition.useContext",
"display": "OperationDefinition.useContext",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.useContext` is mapped to FHIR R4 element `OperationDefinition.useContext` as `Equivalent`.\nWhen multiple useContexts are specified, there is no expectation that all or any of the contexts apply."
}
]
},
{
"code": "OperationDefinition.jurisdiction",
"display": "jurisdiction",
"target": [
{
"code": "OperationDefinition.jurisdiction",
"display": "OperationDefinition.jurisdiction",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.jurisdiction` is mapped to FHIR R4 element `OperationDefinition.jurisdiction` as `Equivalent`.\nIt may be possible for the operation definition to be used in jurisdictions other than those for which it was originally designed or intended."
}
]
},
{
"code": "OperationDefinition.purpose",
"display": "purpose",
"target": [
{
"code": "OperationDefinition.purpose",
"display": "OperationDefinition.purpose",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.purpose` is mapped to FHIR R4 element `OperationDefinition.purpose` as `Equivalent`.\nThis 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": "OperationDefinition.affectsState",
"display": "affectsState",
"target": [
{
"code": "OperationDefinition.affectsState",
"display": "OperationDefinition.affectsState",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.affectsState` is mapped to FHIR R4 element `OperationDefinition.affectsState` as `Equivalent`.\nWhat http methods can be used for the operation depends on the .affectsState value and whether the input parameters are primitive or complex:\n\n1. Servers SHALL support POST method for all operations.\n\n2. Servers SHALL support GET method if all the parameters for the operation are primitive or there are no parameters and the operation has affectsState = false."
}
]
},
{
"code": "OperationDefinition.code",
"display": "code",
"target": [
{
"code": "OperationDefinition.code",
"display": "OperationDefinition.code",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.code` is mapped to FHIR R4 element `OperationDefinition.code` as `Equivalent`."
}
]
},
{
"code": "OperationDefinition.comment",
"display": "comment",
"target": [
{
"code": "OperationDefinition.comment",
"display": "OperationDefinition.comment",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.comment` is mapped to FHIR R4 element `OperationDefinition.comment` as `Equivalent`."
}
]
},
{
"code": "OperationDefinition.base",
"display": "base",
"target": [
{
"code": "OperationDefinition.base",
"display": "OperationDefinition.base",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.base` is mapped to FHIR R4 element `OperationDefinition.base` as `Equivalent`.\nA constrained profile can make optional parameters required or not used and clarify documentation."
}
]
},
{
"code": "OperationDefinition.resource",
"display": "resource",
"target": [
{
"code": "OperationDefinition.resource",
"display": "OperationDefinition.resource",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.resource` is mapped to FHIR R4 element `OperationDefinition.resource` as `SourceIsNarrowerThanTarget`.\nThe mappings for `OperationDefinition.resource` do not allow expression of the necessary codes, per the bindings on the source and target.\nIf the type is an abstract resource (\"Resource\" or \"DomainResource\") then the operation can be invoked on any concrete specialization."
}
]
},
{
"code": "OperationDefinition.system",
"display": "system",
"target": [
{
"code": "OperationDefinition.system",
"display": "OperationDefinition.system",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.system` is mapped to FHIR R4 element `OperationDefinition.system` as `Equivalent`."
}
]
},
{
"code": "OperationDefinition.type",
"display": "type",
"target": [
{
"code": "OperationDefinition.type",
"display": "OperationDefinition.type",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.type` is mapped to FHIR R4 element `OperationDefinition.type` as `Equivalent`."
}
]
},
{
"code": "OperationDefinition.instance",
"display": "instance",
"target": [
{
"code": "OperationDefinition.instance",
"display": "OperationDefinition.instance",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.instance` is mapped to FHIR R4 element `OperationDefinition.instance` as `Equivalent`."
}
]
},
{
"code": "OperationDefinition.inputProfile",
"display": "inputProfile",
"target": [
{
"code": "OperationDefinition.inputProfile",
"display": "OperationDefinition.inputProfile",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.inputProfile` is mapped to FHIR R4 element `OperationDefinition.inputProfile` as `Equivalent`.\nIf present the profile shall not conflict with what is specified in the parameters in the operation definition (max/min etc.), though it may provide additional constraints. The constraints expressed in the profile apply whether the operation is invoked by a POST wih parameters or not."
}
]
},
{
"code": "OperationDefinition.outputProfile",
"display": "outputProfile",
"target": [
{
"code": "OperationDefinition.outputProfile",
"display": "OperationDefinition.outputProfile",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.outputProfile` is mapped to FHIR R4 element `OperationDefinition.outputProfile` as `Equivalent`.\nIf present the profile shall not conflict with what is specified in the parameters in the operation definition (max/min etc.), though it may provide additional constraints. The constraints expressed in the profile apply whether the operation is invoked by a POST wih parameters or not."
}
]
},
{
"code": "OperationDefinition.parameter",
"display": "parameter",
"target": [
{
"code": "OperationDefinition.parameter",
"display": "OperationDefinition.parameter",
"equivalence": "wider",
"comment": "Element `OperationDefinition.parameter` is mapped to FHIR R4 element `OperationDefinition.parameter` as `Equivalent`.\nQuery Definitions only have one output parameter, named \"result\". This might not be described, but can be to allow a profile to be defined."
}
]
},
{
"code": "OperationDefinition.parameter.name",
"display": "name",
"target": [
{
"code": "OperationDefinition.parameter.name",
"display": "OperationDefinition.parameter.name",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.parameter.name` is mapped to FHIR R4 element `OperationDefinition.parameter.name` as `Equivalent`.\nThis 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": "OperationDefinition.parameter.use",
"display": "use",
"target": [
{
"code": "OperationDefinition.parameter.use",
"display": "OperationDefinition.parameter.use",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.parameter.use` is mapped to FHIR R4 element `OperationDefinition.parameter.use` as `Equivalent`.\nIf a parameter name is used for both an input and an output parameter, the parameter should be defined twice."
}
]
},
{
"code": "OperationDefinition.parameter.min",
"display": "min",
"target": [
{
"code": "OperationDefinition.parameter.min",
"display": "OperationDefinition.parameter.min",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.parameter.min` is mapped to FHIR R4 element `OperationDefinition.parameter.min` as `Equivalent`."
}
]
},
{
"code": "OperationDefinition.parameter.max",
"display": "max",
"target": [
{
"code": "OperationDefinition.parameter.max",
"display": "OperationDefinition.parameter.max",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.parameter.max` is mapped to FHIR R4 element `OperationDefinition.parameter.max` as `Equivalent`."
}
]
},
{
"code": "OperationDefinition.parameter.documentation",
"display": "documentation",
"target": [
{
"code": "OperationDefinition.parameter.documentation",
"display": "OperationDefinition.parameter.documentation",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.parameter.documentation` is mapped to FHIR R4 element `OperationDefinition.parameter.documentation` as `Equivalent`."
}
]
},
{
"code": "OperationDefinition.parameter.type",
"display": "type",
"target": [
{
"code": "OperationDefinition.parameter.type",
"display": "OperationDefinition.parameter.type",
"equivalence": "wider",
"comment": "Element `OperationDefinition.parameter.type` is mapped to FHIR R4 element `OperationDefinition.parameter.type` as `RelatedTo`.\nThe mappings for `OperationDefinition.parameter.type` do not allow expression of the necessary codes, per the bindings on the source and target.\nif there is no stated parameter, then the parameter is a multi-part parameter; type and must have at least one part defined."
}
]
},
{
"code": "OperationDefinition.parameter.targetProfile",
"display": "targetProfile",
"target": [
{
"code": "OperationDefinition.parameter.targetProfile",
"display": "OperationDefinition.parameter.targetProfile",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.parameter.targetProfile` is mapped to FHIR R4 element `OperationDefinition.parameter.targetProfile` as `Equivalent`.\nOften, these profiles are the base definitions from the spec (e.g. http://hl7.org/fhir/StructureDefinition/Patient)."
}
]
},
{
"code": "OperationDefinition.parameter.searchType",
"display": "searchType",
"target": [
{
"code": "OperationDefinition.parameter.searchType",
"display": "OperationDefinition.parameter.searchType",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.parameter.searchType` is mapped to FHIR R4 element `OperationDefinition.parameter.searchType` as `Equivalent`."
}
]
},
{
"code": "OperationDefinition.parameter.binding",
"display": "binding",
"target": [
{
"code": "OperationDefinition.parameter.binding",
"display": "OperationDefinition.parameter.binding",
"equivalence": "wider",
"comment": "Element `OperationDefinition.parameter.binding` is mapped to FHIR R4 element `OperationDefinition.parameter.binding` as `Equivalent`."
}
]
},
{
"code": "OperationDefinition.parameter.binding.strength",
"display": "strength",
"target": [
{
"code": "OperationDefinition.parameter.binding.strength",
"display": "OperationDefinition.parameter.binding.strength",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.parameter.binding.strength` is mapped to FHIR R4 element `OperationDefinition.parameter.binding.strength` as `Equivalent`.\nFor further discussion, see [Using Terminologies](https://hl7.org/fhir/terminologies.html)."
}
]
},
{
"code": "OperationDefinition.parameter.binding.valueSet",
"display": "valueSet",
"target": [
{
"code": "OperationDefinition.parameter.binding.valueSet",
"display": "OperationDefinition.parameter.binding.valueSet",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.parameter.binding.valueSet` is mapped to FHIR R4 element `OperationDefinition.parameter.binding.valueSet` as `Equivalent`.\nFor value sets with a referenceResource, the display can contain the value set description. The reference may be version-specific or not."
}
]
},
{
"code": "OperationDefinition.parameter.referencedFrom",
"display": "referencedFrom",
"target": [
{
"code": "OperationDefinition.parameter.referencedFrom",
"display": "OperationDefinition.parameter.referencedFrom",
"equivalence": "wider",
"comment": "Element `OperationDefinition.parameter.referencedFrom` is mapped to FHIR R4 element `OperationDefinition.parameter.referencedFrom` as `Equivalent`.\nResolution applies if the referenced parameter exists."
}
]
},
{
"code": "OperationDefinition.parameter.referencedFrom.source",
"display": "source",
"target": [
{
"code": "OperationDefinition.parameter.referencedFrom.source",
"display": "OperationDefinition.parameter.referencedFrom.source",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.parameter.referencedFrom.source` is mapped to FHIR R4 element `OperationDefinition.parameter.referencedFrom.source` as `Equivalent`."
}
]
},
{
"code": "OperationDefinition.parameter.referencedFrom.sourceId",
"display": "sourceId",
"target": [
{
"code": "OperationDefinition.parameter.referencedFrom.sourceId",
"display": "OperationDefinition.parameter.referencedFrom.sourceId",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.parameter.referencedFrom.sourceId` is mapped to FHIR R4 element `OperationDefinition.parameter.referencedFrom.sourceId` as `Equivalent`."
}
]
},
{
"code": "OperationDefinition.parameter.part",
"display": "part",
"target": [
{
"code": "OperationDefinition.parameter.part",
"display": "OperationDefinition.parameter.part",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.parameter.part` is mapped to FHIR R4 element `OperationDefinition.parameter.part` as `Equivalent`.\nQuery Definitions only have one output parameter, named \"result\". This might not be described, but can be to allow a profile to be defined."
}
]
},
{
"code": "OperationDefinition.overload",
"display": "overload",
"target": [
{
"code": "OperationDefinition.overload",
"display": "OperationDefinition.overload",
"equivalence": "wider",
"comment": "Element `OperationDefinition.overload` is mapped to FHIR R4 element `OperationDefinition.overload` as `Equivalent`.\nThe combinations are suggestions as to which sets of parameters to use together, but the combinations are not intended to be authoritative."
}
]
},
{
"code": "OperationDefinition.overload.parameterName",
"display": "parameterName",
"target": [
{
"code": "OperationDefinition.overload.parameterName",
"display": "OperationDefinition.overload.parameterName",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.overload.parameterName` is mapped to FHIR R4 element `OperationDefinition.overload.parameterName` as `Equivalent`."
}
]
},
{
"code": "OperationDefinition.overload.comment",
"display": "comment",
"target": [
{
"code": "OperationDefinition.overload.comment",
"display": "OperationDefinition.overload.comment",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.overload.comment` is mapped to FHIR R4 element `OperationDefinition.overload.comment` as `Equivalent`."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/OperationDefinition",
"sourceVersion": "4.3.0",
"target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-OperationDefinition.parameter.type",
"targetVersion": "0.1.0",
"element": [
{
"code": "OperationDefinition.parameter.type",
"display": "type",
"target": [
{
"code": "Extension",
"equivalence": "equivalent",
"comment": "Element `OperationDefinition.parameter.type` is mapped to FHIR R4 element `OperationDefinition.parameter.type` as `RelatedTo`.\nThe mappings for `OperationDefinition.parameter.type` do not allow expression of the necessary codes, per the bindings on the source and target.\nif there is no stated parameter, then the parameter is a multi-part parameter; type and must have at least one part defined."
}
]
}
]
}
]
}