Extensions for Using Data Elements from FHIR R4 in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4 in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4 in FHIR R5 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R4-Procedure-element-map-to-R5 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R4ProcedureElementMapToR5 | ||
This ConceptMap represents cross-version mappings for elements from a FHIR R4 Procedure to FHIR R5.
Mapping from http://hl7.org/fhir/4.0 to http://hl7.org/fhir/5.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Procedure|4.0.1 to Procedureversion: 5.0.0)
| Source Code | Relationship | Target Code | Comment |
| Procedure.meta (meta) | is equivalent to | Procedure.meta | Element `Procedure.meta` is mapped to FHIR R5 element `Procedure.meta` as `Equivalent`. |
| Procedure.implicitRules (implicitRules) | is equivalent to | Procedure.implicitRules | Element `Procedure.implicitRules` is mapped to FHIR R5 element `Procedure.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. |
| Procedure.language (language) | is equivalent to | Procedure.language | Element `Procedure.language` is mapped to FHIR R5 element `Procedure.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). |
| Procedure.text (text) | is equivalent to | Procedure.text | Element `Procedure.text` is mapped to FHIR R5 element `Procedure.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. |
| Procedure.contained (contained) | is equivalent to | Procedure.contained | Element `Procedure.contained` is mapped to FHIR R5 element `Procedure.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. |
| Procedure.identifier (identifier) | is equivalent to | Procedure.identifier | Element `Procedure.identifier` is mapped to FHIR R5 element `Procedure.identifier` as `Equivalent`. This is a business identifier, not a resource identifier (see [discussion](https://hl7.org/fhir/resource.htm#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and Person resource instances might share the same social insurance number. |
| Procedure.instantiatesCanonical (instantiatesCanonical) | is equivalent to | Procedure.instantiatesCanonical | Element `Procedure.instantiatesCanonical` is mapped to FHIR R5 element `Procedure.instantiatesCanonical` as `Equivalent`. |
| Procedure.instantiatesUri (instantiatesUri) | is equivalent to | Procedure.instantiatesUri | Element `Procedure.instantiatesUri` is mapped to FHIR R5 element `Procedure.instantiatesUri` as `Equivalent`. This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier. |
| Procedure.basedOn (basedOn) | is equivalent to | Procedure.basedOn | Element `Procedure.basedOn` is mapped to FHIR R5 element `Procedure.basedOn` as `Equivalent`. |
| Procedure.partOf (partOf) | is equivalent to | Procedure.partOf | Element `Procedure.partOf` is mapped to FHIR R5 element `Procedure.partOf` as `Equivalent`. The MedicationAdministration resource has a partOf reference to Procedure, but this is not a circular reference. For example, the anesthesia MedicationAdministration is part of the surgical Procedure (MedicationAdministration.partOf = Procedure). For example, the procedure to insert the IV port for an IV medication administration is part of the medication administration (Procedure.partOf = MedicationAdministration). |
| Procedure.status (status) | is equivalent to | Procedure.status | Element `Procedure.status` is mapped to FHIR R5 element `Procedure.status` as `Equivalent`. The "unknown" code is not to be used to convey other statuses. The "unknown" code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the procedure. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. |
| Procedure.statusReason (statusReason) | is equivalent to | Procedure.statusReason | Element `Procedure.statusReason` is mapped to FHIR R5 element `Procedure.statusReason` as `Equivalent`. This is generally only used for "exception" statuses such as "not-done", "suspended" or "aborted". The reason for performing the event at all is captured in reasonCode, not here. |
| Procedure.category (category) | is equivalent to | Procedure.category | Element `Procedure.category` is mapped to FHIR R5 element `Procedure.category` as `SourceIsNarrowerThanTarget`. |
| Procedure.code (code) | is equivalent to | Procedure.code | Element `Procedure.code` is mapped to FHIR R5 element `Procedure.code` as `Equivalent`. |
| Procedure.subject (subject) | is equivalent to | Procedure.subject | Element `Procedure.subject` is mapped to FHIR R5 element `Procedure.subject` as `Equivalent`. |
| Procedure.encounter (encounter) | is equivalent to | Procedure.encounter | Element `Procedure.encounter` is mapped to FHIR R5 element `Procedure.encounter` as `Equivalent`. This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. |
| Procedure.recorder (recorder) | is equivalent to | Procedure.recorder | Element `Procedure.recorder` is mapped to FHIR R5 element `Procedure.recorder` as `Equivalent`. |
| Procedure.performer (performer) | is broader than | Procedure.performer | Element `Procedure.performer` is mapped to FHIR R5 element `Procedure.performer` as `Equivalent`. |
| Procedure.performer.function (function) | is equivalent to | Procedure.performer.function | Element `Procedure.performer.function` is mapped to FHIR R5 element `Procedure.performer.function` as `Equivalent`. |
| Procedure.performer.actor (actor) | is equivalent to | Procedure.performer.actor | Element `Procedure.performer.actor` is mapped to FHIR R5 element `Procedure.performer.actor` as `Equivalent`. |
| Procedure.performer.onBehalfOf (onBehalfOf) | is equivalent to | Procedure.performer.onBehalfOf | Element `Procedure.performer.onBehalfOf` is mapped to FHIR R5 element `Procedure.performer.onBehalfOf` as `Equivalent`. |
| Procedure.location (location) | is equivalent to | Procedure.location | Element `Procedure.location` is mapped to FHIR R5 element `Procedure.location` as `Equivalent`. |
| Procedure.reasonCode (reasonCode) | is narrower than | Procedure.reason | Element `Procedure.reasonCode` is mapped to FHIR R5 element `Procedure.reason` as `SourceIsNarrowerThanTarget`. Use Procedure.reasonCode when a code sufficiently describes the reason. Use Procedure.reasonReference when referencing a resource, which allows more information to be conveyed, such as onset date. Procedure.reasonCode and Procedure.reasonReference are not meant to be duplicative. For a single reason, either Procedure.reasonCode or Procedure.reasonReference can be used. Procedure.reasonCode may be a summary code, or Procedure.reasonReference may be used to reference a very precise definition of the reason using Condition | Observation | Procedure | DiagnosticReport | DocumentReference. Both Procedure.reasonCode and Procedure.reasonReference can be used if they are describing different reasons for the procedure. |
| Procedure.reasonReference (reasonReference) | is related to | Procedure.reason | Element `Procedure.reasonReference` is mapped to FHIR R5 element `Procedure.reason` as `RelatedTo`. The mappings for `Procedure.reasonReference` do not cover the following types: Reference. It is possible for a procedure to be a reason (such as C-Section) for another procedure (such as an epidural). Other examples include endoscopy for dilatation and biopsy (a combination of diagnostic and therapeutic use). Use Procedure.reasonCode when a code sufficiently describes the reason. Use Procedure.reasonReference when referencing a resource, which allows more information to be conveyed, such as onset date. Procedure.reasonCode and Procedure.reasonReference are not meant to be duplicative. For a single reason, either Procedure.reasonCode or Procedure.reasonReference can be used. Procedure.reasonCode may be a summary code, or Procedure.reasonReference may be used to reference a very precise definition of the reason using Condition | Observation | Procedure | DiagnosticReport | DocumentReference. Both Procedure.reasonCode and Procedure.reasonReference can be used if they are describing different reasons for the procedure. |
| Procedure.bodySite (bodySite) | is equivalent to | Procedure.bodySite | Element `Procedure.bodySite` is mapped to FHIR R5 element `Procedure.bodySite` as `Equivalent`. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [procedure-targetbodystructure](https://hl7.org/fhir/extension-procedure-targetbodystructure.html). |
| Procedure.outcome (outcome) | is equivalent to | Procedure.outcome | Element `Procedure.outcome` is mapped to FHIR R5 element `Procedure.outcome` as `Equivalent`. If outcome contains narrative text only, it can be captured using the CodeableConcept.text. |
| Procedure.report (report) | is equivalent to | Procedure.report | Element `Procedure.report` is mapped to FHIR R5 element `Procedure.report` as `SourceIsNarrowerThanTarget`. There could potentially be multiple reports - e.g. if this was a procedure which took multiple biopsies resulting in a number of anatomical pathology reports. |
| Procedure.complication (complication) | is equivalent to | Procedure.complication | Element `Procedure.complication` is mapped to FHIR R5 element `Procedure.complication` as `SourceIsNarrowerThanTarget`. If complications are only expressed by the narrative text, they can be captured using the CodeableConcept.text. |
| Procedure.followUp (followUp) | is equivalent to | Procedure.followUp | Element `Procedure.followUp` is mapped to FHIR R5 element `Procedure.followUp` as `Equivalent`. |
| Procedure.note (note) | is equivalent to | Procedure.note | Element `Procedure.note` is mapped to FHIR R5 element `Procedure.note` as `Equivalent`. |
| Procedure.focalDevice (focalDevice) | is broader than | Procedure.focalDevice | Element `Procedure.focalDevice` is mapped to FHIR R5 element `Procedure.focalDevice` as `Equivalent`. |
| Procedure.focalDevice.action (action) | is equivalent to | Procedure.focalDevice.action | Element `Procedure.focalDevice.action` is mapped to FHIR R5 element `Procedure.focalDevice.action` as `Equivalent`. |
| Procedure.focalDevice.manipulated (manipulated) | is equivalent to | Procedure.focalDevice.manipulated | Element `Procedure.focalDevice.manipulated` is mapped to FHIR R5 element `Procedure.focalDevice.manipulated` as `Equivalent`. |
| Procedure.usedReference (usedReference) | is related to | Procedure.used | Element `Procedure.usedReference` is mapped to FHIR R5 element `Procedure.used` as `RelatedTo`. The mappings for `Procedure.usedReference` do not cover the following types: Reference. For devices actually implanted or removed, use Procedure.device. |
| Procedure.usedCode (usedCode) | is narrower than | Procedure.used | Element `Procedure.usedCode` is mapped to FHIR R5 element `Procedure.used` as `SourceIsNarrowerThanTarget`. For devices actually implanted or removed, use Procedure.device. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Procedure|4.0.1 to R4: When the procedure was performed (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Procedure.performed[x] (performed[x]) | is equivalent to | Extension (R4: When the procedure was performed (new)) | Element `Procedure.performed[x]` has a context of Procedure based on following the parent source element upwards and mapping to `Procedure`. Element `Procedure.performed[x]` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Age is generally used when the patient reports an age at which the procedure was performed. Range is generally used when the patient reports an age range when the procedure was performed, such as sometime between 20-25 years old. dateTime supports a range of precision due to some procedures being reported as past procedures that might not have millisecond precision while other procedures performed and documented during the encounter might have more precise UTC timestamps with timezone. |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Procedure|4.0.1 to R4: Person who asserts this procedure (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Procedure.asserter (asserter) | is equivalent to | Extension (R4: Person who asserts this procedure (new)) | Element `Procedure.asserter` has a context of Procedure based on following the parent source element upwards and mapping to `Procedure`. Element `Procedure.asserter` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Procedure|4.0.1 to R4: reasonReference additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Procedure.reasonReference (reasonReference) | is broader than | Extension (R4: reasonReference additional types) | Element `Procedure.reasonReference` is mapped to FHIR R5 element `Procedure.reason` as `RelatedTo`. The mappings for `Procedure.reasonReference` do not cover the following types: Reference. It is possible for a procedure to be a reason (such as C-Section) for another procedure (such as an epidural). Other examples include endoscopy for dilatation and biopsy (a combination of diagnostic and therapeutic use). Use Procedure.reasonCode when a code sufficiently describes the reason. Use Procedure.reasonReference when referencing a resource, which allows more information to be conveyed, such as onset date. Procedure.reasonCode and Procedure.reasonReference are not meant to be duplicative. For a single reason, either Procedure.reasonCode or Procedure.reasonReference can be used. Procedure.reasonCode may be a summary code, or Procedure.reasonReference may be used to reference a very precise definition of the reason using Condition | Observation | Procedure | DiagnosticReport | DocumentReference. Both Procedure.reasonCode and Procedure.reasonReference can be used if they are describing different reasons for the procedure. |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Procedure|4.0.1 to R4: A condition that is a result of the procedure (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Procedure.complicationDetail (complicationDetail) | is equivalent to | Extension (R4: A condition that is a result of the procedure (new)) | Element `Procedure.complicationDetail` has a context of Procedure based on following the parent source element upwards and mapping to `Procedure`. Element `Procedure.complicationDetail` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Procedure|4.0.1 to R4: usedReference additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Procedure.usedReference (usedReference) | is broader than | Extension (R4: usedReference additional types) | Element `Procedure.usedReference` is mapped to FHIR R5 element `Procedure.used` as `RelatedTo`. The mappings for `Procedure.usedReference` do not cover the following types: Reference. For devices actually implanted or removed, use Procedure.device. |
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r4.r5#0.1.0 based on FHIR 5.0.0. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change