Generated Narrative: ConceptMap R5-Procedure-element-map-to-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/Procedure|5.0.0 to Procedureversion: 4.0.1) Source Concept Details Relationship Target Concept Details Comment Codes from http://hl7.org/fhir/StructureDefinition/Procedure|5.0.0 Codes from Procedure Procedure.meta meta is equivalent to Procedure.meta Procedure.meta Element `Procedure.meta` is mapped to FHIR R4 element `Procedure.meta` as `Equivalent`. Procedure.implicitRules implicitRules is equivalent to Procedure.implicitRules Procedure.implicitRules Element `Procedure.implicitRules` is mapped to FHIR R4 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 its narrative along with other profiles, value sets, etc. Procedure.language language is equivalent to Procedure.language Procedure.language Element `Procedure.language` is mapped to FHIR R4 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 Procedure.text Element `Procedure.text` is mapped to FHIR R4 element `Procedure.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. Procedure.contained contained is equivalent to Procedure.contained Procedure.contained Element `Procedure.contained` is mapped to FHIR R4 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 Procedure.identifier Element `Procedure.identifier` is mapped to FHIR R4 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 Procedure.instantiatesCanonical Element `Procedure.instantiatesCanonical` is mapped to FHIR R4 element `Procedure.instantiatesCanonical` as `Equivalent`. Procedure.instantiatesUri instantiatesUri is equivalent to Procedure.instantiatesUri Procedure.instantiatesUri Element `Procedure.instantiatesUri` is mapped to FHIR R4 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 Procedure.basedOn Element `Procedure.basedOn` is mapped to FHIR R4 element `Procedure.basedOn` as `Equivalent`. Procedure.partOf partOf is equivalent to Procedure.partOf Procedure.partOf Element `Procedure.partOf` is mapped to FHIR R4 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 Procedure.status Element `Procedure.status` is mapped to FHIR R4 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 Procedure.statusReason Element `Procedure.statusReason` is mapped to FHIR R4 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 Procedure.category Element `Procedure.category` is mapped to FHIR R4 element `Procedure.category` as `SourceIsBroaderThanTarget`. Procedure.code code is equivalent to Procedure.code Procedure.code Element `Procedure.code` is mapped to FHIR R4 element `Procedure.code` as `Equivalent`. Procedure.subject subject maps to wider concept Procedure.subject Procedure.subject Element `Procedure.subject` is mapped to FHIR R4 element `Procedure.subject` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Procedure.subject` with unmapped reference targets: Device, Location, Organization, Practitioner. Procedure.encounter encounter is equivalent to Procedure.encounter Procedure.encounter Element `Procedure.encounter` is mapped to FHIR R4 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.occurrence[x] occurrence[x] maps to wider concept Procedure.performed[x] Procedure.performed[x] Element `Procedure.occurrence[x]` is mapped to FHIR R4 element `Procedure.performed[x]` as `SourceIsBroaderThanTarget`. The mappings for `Procedure.occurrence[x]` do not cover the following types: Timing. The target context `Procedure.performed[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Procedure`. This indicates when the procedure actually occurred or is occurring, not when it was asked/requested/ordered to occur. For the latter, look at the occurence element of the Request this Procedure is "basedOn". The status code allows differentiation of whether the timing reflects a historic event or an ongoing event. Ongoing events should not include an upper bound in the Period or Timing.bounds. 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. Procedure.recorder recorder is equivalent to Procedure.recorder Procedure.recorder Element `Procedure.recorder` is mapped to FHIR R4 element `Procedure.recorder` as `Equivalent`. Procedure.performer performer maps to wider concept Procedure.performer Procedure.performer Element `Procedure.performer` is mapped to FHIR R4 element `Procedure.performer` as `Equivalent`. Procedure.performer.function function is equivalent to Procedure.performer.function Procedure.performer.function Element `Procedure.performer.function` is mapped to FHIR R4 element `Procedure.performer.function` as `Equivalent`. Procedure.performer.actor actor maps to wider concept Procedure.performer.actor Procedure.performer.actor Element `Procedure.performer.actor` is mapped to FHIR R4 element `Procedure.performer.actor` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Procedure.performer.actor` with unmapped reference targets: CareTeam, HealthcareService. Procedure.performer.onBehalfOf onBehalfOf is equivalent to Procedure.performer.onBehalfOf Procedure.performer.onBehalfOf Element `Procedure.performer.onBehalfOf` is mapped to FHIR R4 element `Procedure.performer.onBehalfOf` as `Equivalent`. Organization, Patient, RelatedPerson, Device, CareTeam, and HealthcareService can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when performing the action. Procedure.location location is equivalent to Procedure.location Procedure.location Element `Procedure.location` is mapped to FHIR R4 element `Procedure.location` as `Equivalent`. Procedure.reason reason is related to Procedure.reasonCode Procedure.reasonCode Element `Procedure.reason` is mapped to FHIR R4 element `Procedure.reasonCode` as `SourceIsBroaderThanTarget`. Element `Procedure.reason` is mapped to FHIR R4 element `Procedure.reasonReference` as `SourceIsBroaderThanTarget`. The mappings for `Procedure.reason` do not cover the following types: CodeableReference. Use Procedure.reason.concept when a code sufficiently describes the reason. Use Procedure.reason.reference when referencing a resource, which allows more information to be conveyed, such as onset date. For a single Procedure.reason, if both Procedure.reason.concept and Procedure.reason.reference are present, they are expected to be consistent with each other. is related to Procedure.reasonReference Procedure.reasonReference Element `Procedure.reason` is mapped to FHIR R4 element `Procedure.reasonCode` as `SourceIsBroaderThanTarget`. Element `Procedure.reason` is mapped to FHIR R4 element `Procedure.reasonReference` as `SourceIsBroaderThanTarget`. The mappings for `Procedure.reason` do not cover the following types: CodeableReference. Use Procedure.reason.concept when a code sufficiently describes the reason. Use Procedure.reason.reference when referencing a resource, which allows more information to be conveyed, such as onset date. For a single Procedure.reason, if both Procedure.reason.concept and Procedure.reason.reference are present, they are expected to be consistent with each other. Procedure.bodySite bodySite is equivalent to Procedure.bodySite Procedure.bodySite Element `Procedure.bodySite` is mapped to FHIR R4 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 [http://hl7.org/fhir/StructureDefinition/procedure-targetBodyStructure](http://hl7.org/fhir/extensions/StructureDefinition-procedure-targetBodyStructure.html). Procedure.outcome outcome is equivalent to Procedure.outcome Procedure.outcome Element `Procedure.outcome` is mapped to FHIR R4 element `Procedure.outcome` as `Equivalent`. If outcome contains narrative text only, it can be captured using the CodeableConcept.text. Procedure.report report maps to wider concept Procedure.report Procedure.report Element `Procedure.report` is mapped to FHIR R4 element `Procedure.report` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Procedure.report` with unmapped reference targets: DocumentReference. 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 Procedure.complication Element `Procedure.complication` is mapped to FHIR R4 element `Procedure.complication` as `SourceIsBroaderThanTarget`. If complications are only expressed by the narrative text, they can be captured using the CodeableReference.concept.text. Procedure.followUp followUp is equivalent to Procedure.followUp Procedure.followUp Element `Procedure.followUp` is mapped to FHIR R4 element `Procedure.followUp` as `Equivalent`. Procedure.note note is equivalent to Procedure.note Procedure.note Element `Procedure.note` is mapped to FHIR R4 element `Procedure.note` as `Equivalent`. Procedure.focalDevice focalDevice maps to wider concept Procedure.focalDevice Procedure.focalDevice Element `Procedure.focalDevice` is mapped to FHIR R4 element `Procedure.focalDevice` as `Equivalent`. Procedure.focalDevice.action action is equivalent to Procedure.focalDevice.action Procedure.focalDevice.action Element `Procedure.focalDevice.action` is mapped to FHIR R4 element `Procedure.focalDevice.action` as `Equivalent`. Procedure.focalDevice.manipulated manipulated is equivalent to Procedure.focalDevice.manipulated Procedure.focalDevice.manipulated Element `Procedure.focalDevice.manipulated` is mapped to FHIR R4 element `Procedure.focalDevice.manipulated` as `Equivalent`. Procedure.used used is related to Procedure.usedCode Procedure.usedCode Element `Procedure.used` is mapped to FHIR R4 element `Procedure.usedReference` as `SourceIsBroaderThanTarget`. Element `Procedure.used` is mapped to FHIR R4 element `Procedure.usedCode` as `SourceIsBroaderThanTarget`. The mappings for `Procedure.used` do not cover the following types: CodeableReference. For devices actually implanted or removed, use Procedure.focalDevice.manipulated. is related to Procedure.usedReference Procedure.usedReference Element `Procedure.used` is mapped to FHIR R4 element `Procedure.usedReference` as `SourceIsBroaderThanTarget`. Element `Procedure.used` is mapped to FHIR R4 element `Procedure.usedCode` as `SourceIsBroaderThanTarget`. The mappings for `Procedure.used` do not cover the following types: CodeableReference. For devices actually implanted or removed, use Procedure.focalDevice.manipulated. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Procedure|5.0.0 to R5: Who is the target of the procedure when it is not the subject of record only (new)version: 0.1.0) Source Code Relationship Target Code Comment Procedure.focus (focus) maps to wider concept Extension (R5: Who is the target of the procedure when it is not the subject of record only (new)) Element `Procedure.focus` has a context of Procedure based on following the parent source element upwards and mapping to `Procedure`. Element `Procedure.focus` 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/Procedure|5.0.0 to R5: When the procedure occurred or is occurring additional typesversion: 0.1.0) Source Code Relationship Target Code Comment Procedure.occurrence[x] (occurrence[x]) maps to wider concept Extension (R5: When the procedure occurred or is occurring additional types) Element `Procedure.occurrence[x]` is mapped to FHIR R4 element `Procedure.performed[x]` as `SourceIsBroaderThanTarget`. The mappings for `Procedure.occurrence[x]` do not cover the following types: Timing. The target context `Procedure.performed[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Procedure`. This indicates when the procedure actually occurred or is occurring, not when it was asked/requested/ordered to occur. For the latter, look at the occurence element of the Request this Procedure is "basedOn". The status code allows differentiation of whether the timing reflects a historic event or an ongoing event. Ongoing events should not include an upper bound in the Period or Timing.bounds. 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 4 Mapping from http://hl7.org/fhir/StructureDefinition/Procedure|5.0.0 to R5: When the procedure was first captured in the subject's record (new)version: 0.1.0) Source Code Relationship Target Code Comment Procedure.recorded (recorded) maps to wider concept Extension (R5: When the procedure was first captured in the subject's record (new)) Element `Procedure.recorded` has a context of Procedure based on following the parent source element upwards and mapping to `Procedure`. Element `Procedure.recorded` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Procedure|5.0.0 to R5: Reported rather than primary record (new)version: 0.1.0) Source Code Relationship Target Code Comment Procedure.reported[x] (reported[x]) maps to wider concept Extension (R5: Reported rather than primary record (new)) Element `Procedure.reported[x]` has a context of Procedure based on following the parent source element upwards and mapping to `Procedure`. Element `Procedure.reported[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Procedure|5.0.0 to R5: When the performer performed the procedure (new)version: 0.1.0) Source Code Relationship Target Code Comment Procedure.performer.period (period) maps to wider concept Extension (R5: When the performer performed the procedure (new)) Element `Procedure.performer.period` has a context of Procedure.performer based on following the parent source element upwards and mapping to `Procedure`. Element `Procedure.performer.period` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/Procedure|5.0.0 to R5: The justification that the procedure was performed additional typesversion: 0.1.0) Source Code Relationship Target Code Comment Procedure.reason (reason) maps to wider concept Extension (R5: The justification that the procedure was performed additional types) Element `Procedure.reason` is mapped to FHIR R4 element `Procedure.reasonCode` as `SourceIsBroaderThanTarget`. Element `Procedure.reason` is mapped to FHIR R4 element `Procedure.reasonReference` as `SourceIsBroaderThanTarget`. The mappings for `Procedure.reason` do not cover the following types: CodeableReference. Use Procedure.reason.concept when a code sufficiently describes the reason. Use Procedure.reason.reference when referencing a resource, which allows more information to be conveyed, such as onset date. For a single Procedure.reason, if both Procedure.reason.concept and Procedure.reason.reference are present, they are expected to be consistent with each other. Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/Procedure|5.0.0 to R5: Items used during procedure additional typesversion: 0.1.0) Source Code Relationship Target Code Comment Procedure.used (used) maps to wider concept Extension (R5: Items used during procedure additional types) Element `Procedure.used` is mapped to FHIR R4 element `Procedure.usedReference` as `SourceIsBroaderThanTarget`. Element `Procedure.used` is mapped to FHIR R4 element `Procedure.usedCode` as `SourceIsBroaderThanTarget`. The mappings for `Procedure.used` do not cover the following types: CodeableReference. For devices actually implanted or removed, use Procedure.focalDevice.manipulated. Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/Procedure|5.0.0 to R5: Extra information relevant to the procedure (new)version: 0.1.0) Source Code Relationship Target Code Comment Procedure.supportingInfo (supportingInfo) maps to wider concept Extension (R5: Extra information relevant to the procedure (new)) Element `Procedure.supportingInfo` has a context of Procedure based on following the parent source element upwards and mapping to `Procedure`. Element `Procedure.supportingInfo` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Cross-version mapping for FHIR R5 Procedure to FHIR R4 Procedure
This ConceptMap represents cross-version mappings for elements from a FHIR R5 Procedure to FHIR R4.
Element `Procedure.meta` is mapped to FHIR R4 element `Procedure.meta` as `Equivalent`.
Element `Procedure.implicitRules` is mapped to FHIR R4 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 its narrative along with other profiles, value sets, etc.
Element `Procedure.language` is mapped to FHIR R4 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).
Element `Procedure.text` is mapped to FHIR R4 element `Procedure.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.
Element `Procedure.contained` is mapped to FHIR R4 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.
Element `Procedure.identifier` is mapped to FHIR R4 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.
Element `Procedure.instantiatesCanonical` is mapped to FHIR R4 element `Procedure.instantiatesCanonical` as `Equivalent`.
Element `Procedure.instantiatesUri` is mapped to FHIR R4 element `Procedure.instantiatesUri` as `Equivalent`. This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.
Element `Procedure.basedOn` is mapped to FHIR R4 element `Procedure.basedOn` as `Equivalent`.
Element `Procedure.partOf` is mapped to FHIR R4 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).
Element `Procedure.status` is mapped to FHIR R4 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.
Element `Procedure.statusReason` is mapped to FHIR R4 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.
Element `Procedure.category` is mapped to FHIR R4 element `Procedure.category` as `SourceIsBroaderThanTarget`.
Element `Procedure.code` is mapped to FHIR R4 element `Procedure.code` as `Equivalent`.
Element `Procedure.subject` is mapped to FHIR R4 element `Procedure.subject` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Procedure.subject` with unmapped reference targets: Device, Location, Organization, Practitioner.
Element `Procedure.encounter` is mapped to FHIR R4 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.
Element `Procedure.occurrence[x]` is mapped to FHIR R4 element `Procedure.performed[x]` as `SourceIsBroaderThanTarget`. The mappings for `Procedure.occurrence[x]` do not cover the following types: Timing. The target context `Procedure.performed[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Procedure`. This indicates when the procedure actually occurred or is occurring, not when it was asked/requested/ordered to occur. For the latter, look at the occurence element of the Request this Procedure is "basedOn". The status code allows differentiation of whether the timing reflects a historic event or an ongoing event. Ongoing events should not include an upper bound in the Period or Timing.bounds. 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.
Element `Procedure.recorder` is mapped to FHIR R4 element `Procedure.recorder` as `Equivalent`.
Element `Procedure.performer` is mapped to FHIR R4 element `Procedure.performer` as `Equivalent`.
Element `Procedure.performer.function` is mapped to FHIR R4 element `Procedure.performer.function` as `Equivalent`.
Element `Procedure.performer.actor` is mapped to FHIR R4 element `Procedure.performer.actor` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Procedure.performer.actor` with unmapped reference targets: CareTeam, HealthcareService.
Element `Procedure.performer.onBehalfOf` is mapped to FHIR R4 element `Procedure.performer.onBehalfOf` as `Equivalent`. Organization, Patient, RelatedPerson, Device, CareTeam, and HealthcareService can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when performing the action.
Element `Procedure.location` is mapped to FHIR R4 element `Procedure.location` as `Equivalent`.
Element `Procedure.reason` is mapped to FHIR R4 element `Procedure.reasonCode` as `SourceIsBroaderThanTarget`. Element `Procedure.reason` is mapped to FHIR R4 element `Procedure.reasonReference` as `SourceIsBroaderThanTarget`. The mappings for `Procedure.reason` do not cover the following types: CodeableReference. Use Procedure.reason.concept when a code sufficiently describes the reason. Use Procedure.reason.reference when referencing a resource, which allows more information to be conveyed, such as onset date. For a single Procedure.reason, if both Procedure.reason.concept and Procedure.reason.reference are present, they are expected to be consistent with each other.
Element `Procedure.bodySite` is mapped to FHIR R4 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 [http://hl7.org/fhir/StructureDefinition/procedure-targetBodyStructure](http://hl7.org/fhir/extensions/StructureDefinition-procedure-targetBodyStructure.html).
Element `Procedure.outcome` is mapped to FHIR R4 element `Procedure.outcome` as `Equivalent`. If outcome contains narrative text only, it can be captured using the CodeableConcept.text.
Element `Procedure.report` is mapped to FHIR R4 element `Procedure.report` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Procedure.report` with unmapped reference targets: DocumentReference. 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.
Element `Procedure.complication` is mapped to FHIR R4 element `Procedure.complication` as `SourceIsBroaderThanTarget`. If complications are only expressed by the narrative text, they can be captured using the CodeableReference.concept.text.
Element `Procedure.followUp` is mapped to FHIR R4 element `Procedure.followUp` as `Equivalent`.
Element `Procedure.note` is mapped to FHIR R4 element `Procedure.note` as `Equivalent`.
Element `Procedure.focalDevice` is mapped to FHIR R4 element `Procedure.focalDevice` as `Equivalent`.
Element `Procedure.focalDevice.action` is mapped to FHIR R4 element `Procedure.focalDevice.action` as `Equivalent`.
Element `Procedure.focalDevice.manipulated` is mapped to FHIR R4 element `Procedure.focalDevice.manipulated` as `Equivalent`.
Element `Procedure.used` is mapped to FHIR R4 element `Procedure.usedReference` as `SourceIsBroaderThanTarget`. Element `Procedure.used` is mapped to FHIR R4 element `Procedure.usedCode` as `SourceIsBroaderThanTarget`. The mappings for `Procedure.used` do not cover the following types: CodeableReference. For devices actually implanted or removed, use Procedure.focalDevice.manipulated.
Element `Procedure.focus` has a context of Procedure based on following the parent source element upwards and mapping to `Procedure`. Element `Procedure.focus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `Procedure.recorded` has a context of Procedure based on following the parent source element upwards and mapping to `Procedure`. Element `Procedure.recorded` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `Procedure.reported[x]` has a context of Procedure based on following the parent source element upwards and mapping to `Procedure`. Element `Procedure.reported[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `Procedure.performer.period` has a context of Procedure.performer based on following the parent source element upwards and mapping to `Procedure`. Element `Procedure.performer.period` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `Procedure.supportingInfo` has a context of Procedure based on following the parent source element upwards and mapping to `Procedure`. Element `Procedure.supportingInfo` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).