Extensions for Using Data Elements from FHIR R4B in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4B in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4B in FHIR R5 - Downloaded Version null See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 0 |
<ConceptMap xmlns="http://hl7.org/fhir">
<id value="R4B-Condition-element-map-to-R5"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R4B-Condition-element-map-to-R5</b></p><a name="R4B-Condition-element-map-to-R5"> </a><a name="hcR4B-Condition-element-map-to-R5"> </a><p>Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/5.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Condition|4.3.0</code> to <a href="http://hl7.org/fhir/R5/condition.html">Conditionversion: 5.0.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Condition.meta (meta)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.meta</td><td>Element `Condition.meta` is mapped to FHIR R5 element `Condition.meta` as `Equivalent`.</td></tr><tr><td>Condition.implicitRules (implicitRules)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.implicitRules</td><td>Element `Condition.implicitRules` is mapped to FHIR R5 element `Condition.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.</td></tr><tr><td>Condition.language (language)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.language</td><td>Element `Condition.language` is mapped to FHIR R5 element `Condition.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).</td></tr><tr><td>Condition.text (text)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.text</td><td>Element `Condition.text` is mapped to FHIR R5 element `Condition.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.</td></tr><tr><td>Condition.contained (contained)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.contained</td><td>Element `Condition.contained` is mapped to FHIR R5 element `Condition.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.</td></tr><tr><td>Condition.identifier (identifier)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.identifier</td><td>Element `Condition.identifier` is mapped to FHIR R5 element `Condition.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 a Person resource instance might share the same social insurance number.</td></tr><tr><td>Condition.clinicalStatus (clinicalStatus)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.clinicalStatus</td><td>Element `Condition.clinicalStatus` is mapped to FHIR R5 element `Condition.clinicalStatus` as `SourceIsNarrowerThanTarget`.
The mappings for `Condition.clinicalStatus` do not allow expression of the necessary codes, per the bindings on the source and target.
The data type is CodeableConcept because clinicalStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.</td></tr><tr><td>Condition.verificationStatus (verificationStatus)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.verificationStatus</td><td>Element `Condition.verificationStatus` is mapped to FHIR R5 element `Condition.verificationStatus` as `Equivalent`.
verificationStatus is not required. For example, when a patient has abdominal pain in the ED, there is not likely going to be a verification status.
The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.</td></tr><tr><td>Condition.category (category)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.category</td><td>Element `Condition.category` is mapped to FHIR R5 element `Condition.category` as `Equivalent`.
The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts.</td></tr><tr><td>Condition.severity (severity)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.severity</td><td>Element `Condition.severity` is mapped to FHIR R5 element `Condition.severity` as `Equivalent`.
Coding of the severity with a terminology is preferred, where possible.</td></tr><tr><td>Condition.code (code)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.code</td><td>Element `Condition.code` is mapped to FHIR R5 element `Condition.code` as `Equivalent`.</td></tr><tr><td>Condition.bodySite (bodySite)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.bodySite</td><td>Element `Condition.bodySite` is mapped to FHIR R5 element `Condition.bodySite` as `Equivalent`.
Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [bodySite](https://hl7.org/fhir/extension-bodysite.html). May be a summary code, or a reference to a very precise definition of the location, or both.</td></tr><tr><td>Condition.subject (subject)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.subject</td><td>Element `Condition.subject` is mapped to FHIR R5 element `Condition.subject` as `Equivalent`.</td></tr><tr><td>Condition.encounter (encounter)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.encounter</td><td>Element `Condition.encounter` is mapped to FHIR R5 element `Condition.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. This record indicates the encounter this particular record is associated with. In the case of a "new" diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first "known".</td></tr><tr><td>Condition.onset[x] (onset[x])</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.onset[x]</td><td>Element `Condition.onset[x]` is mapped to FHIR R5 element `Condition.onset[x]` as `Equivalent`.
The target context `Condition.onset[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Condition`.
Age is generally used when the patient reports an age at which the Condition began to occur.</td></tr><tr><td>Condition.abatement[x] (abatement[x])</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.abatement[x]</td><td>Element `Condition.abatement[x]` is mapped to FHIR R5 element `Condition.abatement[x]` as `Equivalent`.
The target context `Condition.abatement[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Condition`.
There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated.</td></tr><tr><td>Condition.recordedDate (recordedDate)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.recordedDate</td><td>Element `Condition.recordedDate` is mapped to FHIR R5 element `Condition.recordedDate` as `Equivalent`.</td></tr><tr><td>Condition.recorder (recorder)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-narrower-than-target" title="source-is-narrower-than-target">is narrower than</a></td><td>Condition.participant</td><td>Element `Condition.recorder` is mapped to FHIR R5 element `Condition.participant` as `SourceIsNarrowerThanTarget`.</td></tr><tr><td>Condition.asserter (asserter)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-narrower-than-target" title="source-is-narrower-than-target">is narrower than</a></td><td>Condition.participant</td><td>Element `Condition.asserter` is mapped to FHIR R5 element `Condition.participant` as `SourceIsNarrowerThanTarget`.</td></tr><tr><td>Condition.stage (stage)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target" title="source-is-broader-than-target">is broader than</a></td><td>Condition.stage</td><td>Element `Condition.stage` is mapped to FHIR R5 element `Condition.stage` as `Equivalent`.</td></tr><tr><td>Condition.stage.summary (summary)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.stage.summary</td><td>Element `Condition.stage.summary` is mapped to FHIR R5 element `Condition.stage.summary` as `Equivalent`.</td></tr><tr><td>Condition.stage.assessment (assessment)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.stage.assessment</td><td>Element `Condition.stage.assessment` is mapped to FHIR R5 element `Condition.stage.assessment` as `Equivalent`.</td></tr><tr><td>Condition.stage.type (type)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.stage.type</td><td>Element `Condition.stage.type` is mapped to FHIR R5 element `Condition.stage.type` as `Equivalent`.</td></tr><tr><td>Condition.evidence (evidence)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target" title="source-is-broader-than-target">is broader than</a></td><td>Condition.evidence</td><td>Element `Condition.evidence` is mapped to FHIR R5 element `Condition.evidence` as `Equivalent`.
The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both.</td></tr><tr><td>Condition.note (note)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Condition.note</td><td>Element `Condition.note` is mapped to FHIR R5 element `Condition.note` as `Equivalent`.</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Condition|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Condition.evi.code.html">R4B: Manifestation/symptom (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Condition.evidence.code (code)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target" title="source-is-broader-than-target">is broader than</a></td><td>Extension (R4B: Manifestation/symptom (new))</td><td>Element `Condition.evidence.code` has a context of Condition.evidence based on following the parent source element upwards and mapping to `Condition`.
Element `Condition.evidence.code` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Condition|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Condition.evi.detail.html">R4B: Supporting information found elsewhere (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Condition.evidence.detail (detail)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target" title="source-is-broader-than-target">is broader than</a></td><td>Extension (R4B: Supporting information found elsewhere (new))</td><td>Element `Condition.evidence.detail` has a context of Condition.evidence based on following the parent source element upwards and mapping to `Condition`.
Element `Condition.evidence.detail` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).</td></tr></table></div>
</text>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="fhir"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
<valueInteger value="0">
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
<valueCanonical
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r5"/>
</extension>
</valueInteger>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
<valueCode value="trial-use">
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
<valueCanonical
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r5"/>
</extension>
</valueCode>
</extension>
<url
value="http://hl7.org/fhir/uv/xver/ConceptMap/R4B-Condition-element-map-to-R5"/>
<version value="0.1.0"/>
<name value="R4BConditionElementMapToR5"/>
<title
value="Cross-version mapping for FHIR R4B Condition to FHIR R5 Condition"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-03-17T16:03:51.6101414-05:00"/>
<contact>
<name value="FHIR Infrastructure"/>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/fiwg"/>
</telecom>
</contact>
<description
value="This ConceptMap represents cross-version mappings for elements from a FHIR R4B Condition to FHIR R5."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<sourceScopeCanonical value="http://hl7.org/fhir/4.3"/>
<targetScopeUri value="http://hl7.org/fhir/5.0"/>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Condition|4.3.0"/>
<target value="http://hl7.org/fhir/StructureDefinition/Condition|5.0.0"/>
<element>
<code value="Condition.meta"/>
<display value="meta"/>
<target>
<code value="Condition.meta"/>
<display value="Condition.meta"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.meta` is mapped to FHIR R5 element `Condition.meta` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Condition.implicitRules"/>
<display value="implicitRules"/>
<target>
<code value="Condition.implicitRules"/>
<display value="Condition.implicitRules"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.implicitRules` is mapped to FHIR R5 element `Condition.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."/>
</target>
</element>
<element>
<code value="Condition.language"/>
<display value="language"/>
<target>
<code value="Condition.language"/>
<display value="Condition.language"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.language` is mapped to FHIR R5 element `Condition.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)."/>
</target>
</element>
<element>
<code value="Condition.text"/>
<display value="text"/>
<target>
<code value="Condition.text"/>
<display value="Condition.text"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.text` is mapped to FHIR R5 element `Condition.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."/>
</target>
</element>
<element>
<code value="Condition.contained"/>
<display value="contained"/>
<target>
<code value="Condition.contained"/>
<display value="Condition.contained"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.contained` is mapped to FHIR R5 element `Condition.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."/>
</target>
</element>
<element>
<code value="Condition.identifier"/>
<display value="identifier"/>
<target>
<code value="Condition.identifier"/>
<display value="Condition.identifier"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.identifier` is mapped to FHIR R5 element `Condition.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 a Person resource instance might share the same social insurance number."/>
</target>
</element>
<element>
<code value="Condition.clinicalStatus"/>
<display value="clinicalStatus"/>
<target>
<code value="Condition.clinicalStatus"/>
<display value="Condition.clinicalStatus"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.clinicalStatus` is mapped to FHIR R5 element `Condition.clinicalStatus` as `SourceIsNarrowerThanTarget`.
The mappings for `Condition.clinicalStatus` do not allow expression of the necessary codes, per the bindings on the source and target.
The data type is CodeableConcept because clinicalStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity."/>
</target>
</element>
<element>
<code value="Condition.verificationStatus"/>
<display value="verificationStatus"/>
<target>
<code value="Condition.verificationStatus"/>
<display value="Condition.verificationStatus"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.verificationStatus` is mapped to FHIR R5 element `Condition.verificationStatus` as `Equivalent`.
verificationStatus is not required. For example, when a patient has abdominal pain in the ED, there is not likely going to be a verification status.
The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity."/>
</target>
</element>
<element>
<code value="Condition.category"/>
<display value="category"/>
<target>
<code value="Condition.category"/>
<display value="Condition.category"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.category` is mapped to FHIR R5 element `Condition.category` as `Equivalent`.
The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts."/>
</target>
</element>
<element>
<code value="Condition.severity"/>
<display value="severity"/>
<target>
<code value="Condition.severity"/>
<display value="Condition.severity"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.severity` is mapped to FHIR R5 element `Condition.severity` as `Equivalent`.
Coding of the severity with a terminology is preferred, where possible."/>
</target>
</element>
<element>
<code value="Condition.code"/>
<display value="code"/>
<target>
<code value="Condition.code"/>
<display value="Condition.code"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.code` is mapped to FHIR R5 element `Condition.code` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Condition.bodySite"/>
<display value="bodySite"/>
<target>
<code value="Condition.bodySite"/>
<display value="Condition.bodySite"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.bodySite` is mapped to FHIR R5 element `Condition.bodySite` as `Equivalent`.
Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [bodySite](https://hl7.org/fhir/extension-bodysite.html). May be a summary code, or a reference to a very precise definition of the location, or both."/>
</target>
</element>
<element>
<code value="Condition.subject"/>
<display value="subject"/>
<target>
<code value="Condition.subject"/>
<display value="Condition.subject"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.subject` is mapped to FHIR R5 element `Condition.subject` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Condition.encounter"/>
<display value="encounter"/>
<target>
<code value="Condition.encounter"/>
<display value="Condition.encounter"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.encounter` is mapped to FHIR R5 element `Condition.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. This record indicates the encounter this particular record is associated with. In the case of a "new" diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first "known"."/>
</target>
</element>
<element>
<code value="Condition.onset[x]"/>
<display value="onset[x]"/>
<target>
<code value="Condition.onset[x]"/>
<display value="Condition.onset[x]"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.onset[x]` is mapped to FHIR R5 element `Condition.onset[x]` as `Equivalent`.
The target context `Condition.onset[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Condition`.
Age is generally used when the patient reports an age at which the Condition began to occur."/>
</target>
</element>
<element>
<code value="Condition.abatement[x]"/>
<display value="abatement[x]"/>
<target>
<code value="Condition.abatement[x]"/>
<display value="Condition.abatement[x]"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.abatement[x]` is mapped to FHIR R5 element `Condition.abatement[x]` as `Equivalent`.
The target context `Condition.abatement[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Condition`.
There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated."/>
</target>
</element>
<element>
<code value="Condition.recordedDate"/>
<display value="recordedDate"/>
<target>
<code value="Condition.recordedDate"/>
<display value="Condition.recordedDate"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.recordedDate` is mapped to FHIR R5 element `Condition.recordedDate` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Condition.recorder"/>
<display value="recorder"/>
<target>
<code value="Condition.participant"/>
<display value="Condition.participant"/>
<relationship value="source-is-narrower-than-target"/>
<comment
value="Element `Condition.recorder` is mapped to FHIR R5 element `Condition.participant` as `SourceIsNarrowerThanTarget`."/>
</target>
</element>
<element>
<code value="Condition.asserter"/>
<display value="asserter"/>
<target>
<code value="Condition.participant"/>
<display value="Condition.participant"/>
<relationship value="source-is-narrower-than-target"/>
<comment
value="Element `Condition.asserter` is mapped to FHIR R5 element `Condition.participant` as `SourceIsNarrowerThanTarget`."/>
</target>
</element>
<element>
<code value="Condition.stage"/>
<display value="stage"/>
<target>
<code value="Condition.stage"/>
<display value="Condition.stage"/>
<relationship value="source-is-broader-than-target"/>
<comment
value="Element `Condition.stage` is mapped to FHIR R5 element `Condition.stage` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Condition.stage.summary"/>
<display value="summary"/>
<target>
<code value="Condition.stage.summary"/>
<display value="Condition.stage.summary"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.stage.summary` is mapped to FHIR R5 element `Condition.stage.summary` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Condition.stage.assessment"/>
<display value="assessment"/>
<target>
<code value="Condition.stage.assessment"/>
<display value="Condition.stage.assessment"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.stage.assessment` is mapped to FHIR R5 element `Condition.stage.assessment` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Condition.stage.type"/>
<display value="type"/>
<target>
<code value="Condition.stage.type"/>
<display value="Condition.stage.type"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.stage.type` is mapped to FHIR R5 element `Condition.stage.type` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Condition.evidence"/>
<display value="evidence"/>
<target>
<code value="Condition.evidence"/>
<display value="Condition.evidence"/>
<relationship value="source-is-broader-than-target"/>
<comment
value="Element `Condition.evidence` is mapped to FHIR R5 element `Condition.evidence` as `Equivalent`.
The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both."/>
</target>
</element>
<element>
<code value="Condition.note"/>
<display value="note"/>
<target>
<code value="Condition.note"/>
<display value="Condition.note"/>
<relationship value="equivalent"/>
<comment
value="Element `Condition.note` is mapped to FHIR R5 element `Condition.note` as `Equivalent`."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Condition|4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Condition.evidence.code|0.1.0"/>
<element>
<code value="Condition.evidence.code"/>
<display value="code"/>
<target>
<code value="Extension"/>
<relationship value="source-is-broader-than-target"/>
<comment
value="Element `Condition.evidence.code` has a context of Condition.evidence based on following the parent source element upwards and mapping to `Condition`.
Element `Condition.evidence.code` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Condition|4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Condition.evidence.detail|0.1.0"/>
<element>
<code value="Condition.evidence.detail"/>
<display value="detail"/>
<target>
<code value="Extension"/>
<relationship value="source-is-broader-than-target"/>
<comment
value="Element `Condition.evidence.detail` has a context of Condition.evidence based on following the parent source element upwards and mapping to `Condition`.
Element `Condition.evidence.detail` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
</ConceptMap>
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r4b.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