FHIR IG analytics| Package | hl7.fhir.uv.xver-r5.r4b |
| Resource Type | ConceptMap |
| Id | ConceptMap-R5-Condition-element-map-to-R4B.json |
| FHIR Version | R4B |
| Source | http://hl7.org/fhir/uv/xver-r5.r4b/0.1.0/ConceptMap-R5-Condition-element-map-to-R4B.html |
| URL | http://hl7.org/fhir/uv/xver/ConceptMap/R5-Condition-element-map-to-R4B |
| Version | 0.1.0 |
| Status | active |
| Date | 2026-03-17T16:03:56.0721558-05:00 |
| Name | R5ConditionElementMapToR4B |
| Title | Cross-version mapping for FHIR R5 Condition to FHIR R4B Condition |
| Realm | uv |
| Authority | hl7 |
| Description | This ConceptMap represents cross-version mappings for elements from a FHIR R5 Condition to FHIR R4B. |
No resources found
| StructureDefinition | ||
| hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 | extension-Condition.clinicalStatus | Cross-version Extension for R5.Condition.clinicalStatus for use in FHIR R4 |
| hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 | extension-Condition.participant | Cross-version Extension for R5.Condition.participant for use in FHIR R4 |
Note: links and images are rebased to the (stated) source
Generated Narrative: ConceptMap R5-Condition-element-map-to-R4B
Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.3
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Condition|5.0.0 to Conditionversion: 4.3.0)
| Source Code | Relationship | Target Code | Comment |
| Condition.meta (meta) | is equivalent to | Condition.meta | Element `Condition.meta` is mapped to FHIR R4B element `Condition.meta` as `Equivalent`. |
| Condition.implicitRules (implicitRules) | is equivalent to | Condition.implicitRules | Element `Condition.implicitRules` is mapped to FHIR R4B 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 its narrative along with other profiles, value sets, etc. |
| Condition.language (language) | is equivalent to | Condition.language | Element `Condition.language` is mapped to FHIR R4B 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). |
| Condition.text (text) | is equivalent to | Condition.text | Element `Condition.text` is mapped to FHIR R4B element `Condition.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. |
| Condition.contained (contained) | is equivalent to | Condition.contained | Element `Condition.contained` is mapped to FHIR R4B 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. |
| Condition.identifier (identifier) | is equivalent to | Condition.identifier | Element `Condition.identifier` is mapped to FHIR R4B 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. |
| Condition.clinicalStatus (clinicalStatus) | maps to wider concept | Condition.clinicalStatus | Element `Condition.clinicalStatus` is mapped to FHIR R4B element `Condition.clinicalStatus` as `SourceIsBroaderThanTarget`. The target context `Condition.clinicalStatus` is a modifier element, so this extension does not need to be defined as a modifier. 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. clinicalStatus is required since it is a modifier element. For conditions that are problems list items, the clinicalStatus should not be unknown. For conditions that are not problem list items, the clinicalStatus may be unknown. For example, conditions derived from a claim are point in time, so those conditions may have a clinicalStatus of unknown |
| Condition.verificationStatus (verificationStatus) | is equivalent to | Condition.verificationStatus | Element `Condition.verificationStatus` is mapped to FHIR R4B 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. |
| Condition.category (category) | is equivalent to | Condition.category | Element `Condition.category` is mapped to FHIR R4B element `Condition.category` as `Equivalent`. The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts. |
| Condition.severity (severity) | is equivalent to | Condition.severity | Element `Condition.severity` is mapped to FHIR R4B element `Condition.severity` as `Equivalent`. Coding of the severity with a terminology is preferred, where possible. |
| Condition.code (code) | is equivalent to | Condition.code | Element `Condition.code` is mapped to FHIR R4B element `Condition.code` as `Equivalent`. |
| Condition.bodySite (bodySite) | is equivalent to | Condition.bodySite | Element `Condition.bodySite` is mapped to FHIR R4B element `Condition.bodySite` as `Equivalent`. Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodyStructure resource (e.g. to identify and track separately) then use the standard extension [http://hl7.org/fhir/StructureDefinition/bodySite](http://hl7.org/fhir/extensions/StructureDefinition-bodySite.html). May be a summary code, or a reference to a very precise definition of the location, or both. |
| Condition.subject (subject) | is equivalent to | Condition.subject | Element `Condition.subject` is mapped to FHIR R4B element `Condition.subject` as `Equivalent`. |
| Condition.encounter (encounter) | is equivalent to | Condition.encounter | Element `Condition.encounter` is mapped to FHIR R4B 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". |
| Condition.onset[x] (onset[x]) | is equivalent to | Condition.onset[x] | Element `Condition.onset[x]` is mapped to FHIR R4B 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. Period is generally used to convey an imprecise onset that occurred within the time period. For example, Period is not intended to convey the transition period before the chronic bronchitis or COPD condition was diagnosed, but Period can be used to convey an imprecise diagnosis date. Range is generally used to convey an imprecise age range (e.g. 4 to 6 years old). Because a Condition.code can represent multiple levels of granularity and can be modified over time, the onset and abatement dates can have ambiguity whether those dates apply to the current Condition.code or an earlier representation of that Condition.code. For example, if the Condition.code was initially documented as severe asthma, then it is ambiguous whether the onset and abatement dates apply to asthma (overall in that subject's lifetime) or when asthma transitioned to become severe. |
| Condition.abatement[x] (abatement[x]) | is equivalent to | Condition.abatement[x] | Element `Condition.abatement[x]` is mapped to FHIR R4B 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. Because a Condition.code can represent multiple levels of granularity and can be modified over time, the onset and abatement dates can have ambiguity whether those dates apply to the current Condition.code or an earlier representation of that Condition.code. For example, if the Condition.code was initially documented as severe asthma, then it is ambiguous whether the onset and abatement dates apply to asthma (overall in that subject's lifetime) or when asthma transitioned to become severe. |
| Condition.recordedDate (recordedDate) | is equivalent to | Condition.recordedDate | Element `Condition.recordedDate` is mapped to FHIR R4B element `Condition.recordedDate` as `Equivalent`. When onset date is unknown, recordedDate can be used to establish if the condition was present on or before a given date. If the recordedDate is known and provided by a sending system, it is preferred that the receiving system preserve that recordedDate value. If the recordedDate is not provided by the sending system, the receipt timestamp is sometimes used as the recordedDate. |
| Condition.stage (stage) | maps to wider concept | Condition.stage | Element `Condition.stage` is mapped to FHIR R4B element `Condition.stage` as `Equivalent`. |
| Condition.stage.summary (summary) | is equivalent to | Condition.stage.summary | Element `Condition.stage.summary` is mapped to FHIR R4B element `Condition.stage.summary` as `Equivalent`. |
| Condition.stage.assessment (assessment) | is equivalent to | Condition.stage.assessment | Element `Condition.stage.assessment` is mapped to FHIR R4B element `Condition.stage.assessment` as `Equivalent`. |
| Condition.stage.type (type) | is equivalent to | Condition.stage.type | Element `Condition.stage.type` is mapped to FHIR R4B element `Condition.stage.type` as `Equivalent`. |
| Condition.evidence (evidence) | is equivalent to | Condition.evidence | Element `Condition.evidence` is mapped to FHIR R4B element `Condition.evidence` as `Equivalent`. If the condition was confirmed, but subsequently refuted, then the evidence can be cumulative including all evidence over time. The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both. For example, if the Condition.code is pneumonia, then there could be an evidence list where Condition.evidence.concept = fever (CodeableConcept), Condition.evidence.concept = cough (CodeableConcept), and Condition.evidence.reference = bronchitis (reference to Condition). |
| Condition.note (note) | is equivalent to | Condition.note | Element `Condition.note` is mapped to FHIR R4B element `Condition.note` as `Equivalent`. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Condition|5.0.0 to R5: active | recurrence | relapse | inactive | remission | resolved | unknownversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Condition.clinicalStatus (clinicalStatus) | is equivalent to | Extension (R5: active | recurrence | relapse | inactive | remission | resolved | unknown) | Element `Condition.clinicalStatus` is mapped to FHIR R4B element `Condition.clinicalStatus` as `SourceIsBroaderThanTarget`. The target context `Condition.clinicalStatus` is a modifier element, so this extension does not need to be defined as a modifier. 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. clinicalStatus is required since it is a modifier element. For conditions that are problems list items, the clinicalStatus should not be unknown. For conditions that are not problem list items, the clinicalStatus may be unknown. For example, conditions derived from a claim are point in time, so those conditions may have a clinicalStatus of unknown |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Condition|5.0.0 to R5: Who or what participated in the activities related to the condition and how they were involved (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Condition.participant (participant) | maps to wider concept | Extension (R5: Who or what participated in the activities related to the condition and how they were involved (new)) | Element `Condition.participant` has a context of Condition based on following the parent source element upwards and mapping to `Condition`. Element `Condition.participant` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
| Condition.participant.function (function) | maps to wider concept | Extension.extension:function (R5: Type of involvement (new)) | Element `Condition.participant.function` is part of an existing definition because parent element `Condition.participant` requires a cross-version extension. Element `Condition.participant.function` has a context of Condition based on following the parent source element upwards and mapping to `Condition`. Element `Condition.participant.function` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
| Condition.participant.actor (actor) | maps to wider concept | Extension.extension:actor (R5: Who or what participated in the activities related to the condition (new)) | Element `Condition.participant.actor` is part of an existing definition because parent element `Condition.participant` requires a cross-version extension. Element `Condition.participant.actor` has a context of Condition based on following the parent source element upwards and mapping to `Condition`. Element `Condition.participant.actor` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
{
"resourceType": "ConceptMap",
"id": "R5-Condition-element-map-to-R4B",
"text": {
"status": "generated",
"div": "<!-- snip (see above) -->"
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "fhir"
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger": 0,
"_valueInteger": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4b"
}
]
}
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode": "trial-use",
"_valueCode": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4b"
}
]
}
}
],
"url": "http://hl7.org/fhir/uv/xver/ConceptMap/R5-Condition-element-map-to-R4B",
"version": "0.1.0",
"name": "R5ConditionElementMapToR4B",
"title": "Cross-version mapping for FHIR R5 Condition to FHIR R4B Condition",
"status": "active",
"experimental": false,
"date": "2026-03-17T16:03:56.0721558-05:00",
"contact": [
{
"name": "FHIR Infrastructure",
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/fiwg"
}
]
}
],
"description": "This ConceptMap represents cross-version mappings for elements from a FHIR R5 Condition to FHIR R4B.",
"jurisdiction": [
{
"coding": [
{
"system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code": "001",
"display": "World"
}
]
}
],
"sourceCanonical": "http://hl7.org/fhir/5.0",
"targetUri": "http://hl7.org/fhir/4.3",
"group": [
{
"source": "http://hl7.org/fhir/StructureDefinition/Condition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/StructureDefinition/Condition",
"targetVersion": "4.3.0",
"element": [
{
"code": "Condition.meta",
"display": "meta",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.meta",
"display": "Condition.meta",
"equivalence": "equivalent",
"comment": "Element `Condition.meta` is mapped to FHIR R4B element `Condition.meta` as `Equivalent`."
}
]
},
{
"code": "Condition.implicitRules",
"display": "implicitRules",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.implicitRules",
"display": "Condition.implicitRules",
"equivalence": "equivalent",
"comment": "Element `Condition.implicitRules` is mapped to FHIR R4B element `Condition.implicitRules` as `Equivalent`.\nAsserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc."
}
]
},
{
"code": "Condition.language",
"display": "language",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.language",
"display": "Condition.language",
"equivalence": "equivalent",
"comment": "Element `Condition.language` is mapped to FHIR R4B element `Condition.language` as `Equivalent`.\nLanguage is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute)."
}
]
},
{
"code": "Condition.text",
"display": "text",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.text",
"display": "Condition.text",
"equivalence": "equivalent",
"comment": "Element `Condition.text` is mapped to FHIR R4B element `Condition.text` as `Equivalent`.\nContained 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."
}
]
},
{
"code": "Condition.contained",
"display": "contained",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.contained",
"display": "Condition.contained",
"equivalence": "equivalent",
"comment": "Element `Condition.contained` is mapped to FHIR R4B element `Condition.contained` as `Equivalent`.\nThis should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels."
}
]
},
{
"code": "Condition.identifier",
"display": "identifier",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.identifier",
"display": "Condition.identifier",
"equivalence": "equivalent",
"comment": "Element `Condition.identifier` is mapped to FHIR R4B element `Condition.identifier` as `Equivalent`.\nThis 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."
}
]
},
{
"code": "Condition.clinicalStatus",
"display": "clinicalStatus",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Condition.clinicalStatus",
"display": "Condition.clinicalStatus",
"equivalence": "wider",
"comment": "Element `Condition.clinicalStatus` is mapped to FHIR R4B element `Condition.clinicalStatus` as `SourceIsBroaderThanTarget`.\nThe target context `Condition.clinicalStatus` is a modifier element, so this extension does not need to be defined as a modifier.\nThe 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. clinicalStatus is required since it is a modifier element. For conditions that are problems list items, the clinicalStatus should not be unknown. For conditions that are not problem list items, the clinicalStatus may be unknown. For example, conditions derived from a claim are point in time, so those conditions may have a clinicalStatus of unknown"
}
]
},
{
"code": "Condition.verificationStatus",
"display": "verificationStatus",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.verificationStatus",
"display": "Condition.verificationStatus",
"equivalence": "equivalent",
"comment": "Element `Condition.verificationStatus` is mapped to FHIR R4B element `Condition.verificationStatus` as `Equivalent`.\nverificationStatus is not required. For example, when a patient has abdominal pain in the ED, there is not likely going to be a verification status.\nThe 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."
}
]
},
{
"code": "Condition.category",
"display": "category",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.category",
"display": "Condition.category",
"equivalence": "equivalent",
"comment": "Element `Condition.category` is mapped to FHIR R4B element `Condition.category` as `Equivalent`.\nThe categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts."
}
]
},
{
"code": "Condition.severity",
"display": "severity",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.severity",
"display": "Condition.severity",
"equivalence": "equivalent",
"comment": "Element `Condition.severity` is mapped to FHIR R4B element `Condition.severity` as `Equivalent`.\nCoding of the severity with a terminology is preferred, where possible."
}
]
},
{
"code": "Condition.code",
"display": "code",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.code",
"display": "Condition.code",
"equivalence": "equivalent",
"comment": "Element `Condition.code` is mapped to FHIR R4B element `Condition.code` as `Equivalent`."
}
]
},
{
"code": "Condition.bodySite",
"display": "bodySite",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.bodySite",
"display": "Condition.bodySite",
"equivalence": "equivalent",
"comment": "Element `Condition.bodySite` is mapped to FHIR R4B element `Condition.bodySite` as `Equivalent`.\nOnly used if not implicit in code found in Condition.code. If the use case requires attributes from the BodyStructure resource (e.g. to identify and track separately) then use the standard extension [http://hl7.org/fhir/StructureDefinition/bodySite](http://hl7.org/fhir/extensions/StructureDefinition-bodySite.html). May be a summary code, or a reference to a very precise definition of the location, or both."
}
]
},
{
"code": "Condition.subject",
"display": "subject",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.subject",
"display": "Condition.subject",
"equivalence": "equivalent",
"comment": "Element `Condition.subject` is mapped to FHIR R4B element `Condition.subject` as `Equivalent`."
}
]
},
{
"code": "Condition.encounter",
"display": "encounter",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.encounter",
"display": "Condition.encounter",
"equivalence": "equivalent",
"comment": "Element `Condition.encounter` is mapped to FHIR R4B element `Condition.encounter` as `Equivalent`.\nThis 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\"."
}
]
},
{
"code": "Condition.onset[x]",
"display": "onset[x]",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.onset[x]",
"display": "Condition.onset[x]",
"equivalence": "equivalent",
"comment": "Element `Condition.onset[x]` is mapped to FHIR R4B element `Condition.onset[x]` as `Equivalent`.\nThe target context `Condition.onset[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Condition`.\nAge is generally used when the patient reports an age at which the Condition began to occur. Period is generally used to convey an imprecise onset that occurred within the time period. For example, Period is not intended to convey the transition period before the chronic bronchitis or COPD condition was diagnosed, but Period can be used to convey an imprecise diagnosis date. Range is generally used to convey an imprecise age range (e.g. 4 to 6 years old). Because a Condition.code can represent multiple levels of granularity and can be modified over time, the onset and abatement dates can have ambiguity whether those dates apply to the current Condition.code or an earlier representation of that Condition.code. For example, if the Condition.code was initially documented as severe asthma, then it is ambiguous whether the onset and abatement dates apply to asthma (overall in that subject's lifetime) or when asthma transitioned to become severe."
}
]
},
{
"code": "Condition.abatement[x]",
"display": "abatement[x]",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.abatement[x]",
"display": "Condition.abatement[x]",
"equivalence": "equivalent",
"comment": "Element `Condition.abatement[x]` is mapped to FHIR R4B element `Condition.abatement[x]` as `Equivalent`.\nThe target context `Condition.abatement[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Condition`.\nThere 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.\nBecause a Condition.code can represent multiple levels of granularity and can be modified over time, the onset and abatement dates can have ambiguity whether those dates apply to the current Condition.code or an earlier representation of that Condition.code. For example, if the Condition.code was initially documented as severe asthma, then it is ambiguous whether the onset and abatement dates apply to asthma (overall in that subject's lifetime) or when asthma transitioned to become severe."
}
]
},
{
"code": "Condition.recordedDate",
"display": "recordedDate",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.recordedDate",
"display": "Condition.recordedDate",
"equivalence": "equivalent",
"comment": "Element `Condition.recordedDate` is mapped to FHIR R4B element `Condition.recordedDate` as `Equivalent`.\nWhen onset date is unknown, recordedDate can be used to establish if the condition was present on or before a given date. If the recordedDate is known and provided by a sending system, it is preferred that the receiving system preserve that recordedDate value. If the recordedDate is not provided by the sending system, the receipt timestamp is sometimes used as the recordedDate."
}
]
},
{
"code": "Condition.stage",
"display": "stage",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Condition.stage",
"display": "Condition.stage",
"equivalence": "wider",
"comment": "Element `Condition.stage` is mapped to FHIR R4B element `Condition.stage` as `Equivalent`."
}
]
},
{
"code": "Condition.stage.summary",
"display": "summary",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.stage.summary",
"display": "Condition.stage.summary",
"equivalence": "equivalent",
"comment": "Element `Condition.stage.summary` is mapped to FHIR R4B element `Condition.stage.summary` as `Equivalent`."
}
]
},
{
"code": "Condition.stage.assessment",
"display": "assessment",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.stage.assessment",
"display": "Condition.stage.assessment",
"equivalence": "equivalent",
"comment": "Element `Condition.stage.assessment` is mapped to FHIR R4B element `Condition.stage.assessment` as `Equivalent`."
}
]
},
{
"code": "Condition.stage.type",
"display": "type",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.stage.type",
"display": "Condition.stage.type",
"equivalence": "equivalent",
"comment": "Element `Condition.stage.type` is mapped to FHIR R4B element `Condition.stage.type` as `Equivalent`."
}
]
},
{
"code": "Condition.evidence",
"display": "evidence",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.evidence",
"display": "Condition.evidence",
"equivalence": "equivalent",
"comment": "Element `Condition.evidence` is mapped to FHIR R4B element `Condition.evidence` as `Equivalent`.\nIf the condition was confirmed, but subsequently refuted, then the evidence can be cumulative including all evidence over time. The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both. For example, if the Condition.code is pneumonia, then there could be an evidence list where Condition.evidence.concept = fever (CodeableConcept), Condition.evidence.concept = cough (CodeableConcept), and Condition.evidence.reference = bronchitis (reference to Condition)."
}
]
},
{
"code": "Condition.note",
"display": "note",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Condition.note",
"display": "Condition.note",
"equivalence": "equivalent",
"comment": "Element `Condition.note` is mapped to FHIR R4B element `Condition.note` as `Equivalent`."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/Condition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Condition.clinicalStatus",
"targetVersion": "0.1.0",
"element": [
{
"code": "Condition.clinicalStatus",
"display": "clinicalStatus",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Extension",
"equivalence": "equivalent",
"comment": "Element `Condition.clinicalStatus` is mapped to FHIR R4B element `Condition.clinicalStatus` as `SourceIsBroaderThanTarget`.\nThe target context `Condition.clinicalStatus` is a modifier element, so this extension does not need to be defined as a modifier.\nThe 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. clinicalStatus is required since it is a modifier element. For conditions that are problems list items, the clinicalStatus should not be unknown. For conditions that are not problem list items, the clinicalStatus may be unknown. For example, conditions derived from a claim are point in time, so those conditions may have a clinicalStatus of unknown"
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/Condition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Condition.participant",
"targetVersion": "0.1.0",
"element": [
{
"code": "Condition.participant",
"display": "participant",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `Condition.participant` has a context of Condition based on following the parent source element upwards and mapping to `Condition`.\nElement `Condition.participant` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."
}
]
},
{
"code": "Condition.participant.function",
"display": "function",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension.extension:function",
"equivalence": "wider",
"comment": "Element `Condition.participant.function` is part of an existing definition because parent element `Condition.participant` requires a cross-version extension.\nElement `Condition.participant.function` has a context of Condition based on following the parent source element upwards and mapping to `Condition`.\nElement `Condition.participant.function` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."
}
]
},
{
"code": "Condition.participant.actor",
"display": "actor",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension.extension:actor",
"equivalence": "wider",
"comment": "Element `Condition.participant.actor` is part of an existing definition because parent element `Condition.participant` requires a cross-version extension.\nElement `Condition.participant.actor` has a context of Condition based on following the parent source element upwards and mapping to `Condition`.\nElement `Condition.participant.actor` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."
}
]
}
]
}
]
}