Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R5-OperationDefinition-element-map-to-R4 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R5OperationDefinitionElementMapToR4 | ||
This ConceptMap represents cross-version mappings for elements from a FHIR R5 OperationDefinition to FHIR R4.
Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/OperationDefinition|5.0.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 its 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 a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. |
| 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 definitions that have the same url 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. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format). |
| 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 no-whitespace 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`. A nominal state-transition diagram can be found in the] documentation Unknown does not represent 'other' - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. |
| 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`. The date is often not tracked until the resource is published, but may be present on draft content. 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. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). |
| 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. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). |
| 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 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 even 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`. Element `OperationDefinition.jurisdiction` has been flagged as deprecated. It may be possible for the operation definition to be used in jurisdictions other than those for which it was originally designed or intended. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.) |
| 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 the GET method when the operation has affectsState = false and all required parameters for the operation are primitive. |
| OperationDefinition.code (code) | is equivalent to | OperationDefinition.code | Element `OperationDefinition.code` is mapped to FHIR R4 element `OperationDefinition.code` as `Equivalent`. For maximum compatibility, use only lowercase ASCII characters. Note that HL7 will never define multiple operations with the same code. See [Naming Rules & Guidelines](https://confluence.hl7.org/display/FHIR/Guide+to+Designing+Resources#GuidetoDesigningResources-NamingRules&Guidelines) for the internal HL7 rules around codes, which are useful additional advice for all implementers |
| 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, introduce new parameters (required or optional), and clarify documentation. |
| OperationDefinition.resource (resource) | is equivalent to | OperationDefinition.resource | Element `OperationDefinition.resource` is mapped to FHIR R4 element `OperationDefinition.resource` as `SourceIsNarrowerThanTarget`. 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) | is equivalent to | OperationDefinition.parameter.type | Element `OperationDefinition.parameter.type` is mapped to FHIR R4 element `OperationDefinition.parameter.type` as `RelatedTo`. 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`. Parameters that are search parameter usually - but not always - are also defined for use with general searches, and function in the operation to filter the set of resources in scope for the operation just like the do when searching. The searchType describes how the server processes the value. For an example, see the [Evaluate Measure Operation](https://hl7.org/fhir/measure-operation-evaluate-measure.html) |
| 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|5.0.0 to R5: instance | type | system (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| OperationDefinition.parameter.scope (scope) | maps to wider concept | Extension (R5: instance | type | system (new)) | Element `OperationDefinition.parameter.scope` has a context of OperationDefinition.parameter based on following the parent source element upwards and mapping to `OperationDefinition`. Element `OperationDefinition.parameter.scope` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/OperationDefinition|5.0.0 to R5: Allowed sub-type this parameter can have (if type is abstract) (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| OperationDefinition.parameter.allowedType (allowedType) | maps to wider concept | Extension (R5: Allowed sub-type this parameter can have (if type is abstract) (new)) | Element `OperationDefinition.parameter.allowedType` has a context of OperationDefinition.parameter based on following the parent source element upwards and mapping to `OperationDefinition`. Element `OperationDefinition.parameter.allowedType` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). In previous versions of FHIR, there was an extension for this: http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type |
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r5.r4#0.1.0 based on FHIR 4.0.1. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change