Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions

ConceptMap: R5ConditionDefinitionElementMapToR4

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R5-ConditionDefinition-element-map-to-R4 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R5ConditionDefinitionElementMapToR4

This ConceptMap represents cross-version mappings for elements from a FHIR R5 ConditionDefinition to FHIR R4.

Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ConditionDefinition|5.0.0 to Basicversion: 4.0.1)

Source CodeRelationshipTarget CodeComment
ConditionDefinition.meta (meta)​is equivalent toBasic.metaElement matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `ConditionDefinition.meta` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
ConditionDefinition.implicitRules (implicitRules)​is equivalent toBasic.implicitRulesElement matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `ConditionDefinition.implicitRules` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.implicitRules` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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.
ConditionDefinition.language (language)​is equivalent toBasic.languageElement matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `ConditionDefinition.language` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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).
ConditionDefinition.text (text)​is equivalent toBasic.textElement matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `ConditionDefinition.text` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.text` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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.
ConditionDefinition.contained (contained)​is equivalent toBasic.containedElement matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `ConditionDefinition.contained` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.contained` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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.
ConditionDefinition.identifier (identifier)​is equivalent toBasic.identifierElement matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `ConditionDefinition.identifier` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). An externally-defined extension that has been mapped as the representation of FHIR R5 element `ConditionDefinition.identifier`: `http://hl7.org/fhir/StructureDefinition/artifact-identifier`. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this condition definition outside of FHIR, where it is not possible to use the logical URI.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/ConditionDefinition|5.0.0 to R5: Subordinate title of the event definition (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ConditionDefinition.subtitle (subtitle)​maps to wider conceptExtension (R5: Subordinate title of the event definition (new))Element `ConditionDefinition.subtitle` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.subtitle` 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/ConditionDefinition|5.0.0 to R5: Intended jurisdiction for condition definition (if applicable) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ConditionDefinition.jurisdiction (jurisdiction)​maps to wider conceptExtension (R5: Intended jurisdiction for condition definition (if applicable) (new))Element `ConditionDefinition.jurisdiction` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.jurisdiction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Element `ConditionDefinition.jurisdiction` has been flagged as deprecated. It may be possible for the condition definition to be used in jurisdictions other than those for which it was originally designed or intended. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/ConditionDefinition|5.0.0 to R5: Identification of the condition, problem or diagnosis (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ConditionDefinition.code (code)​maps to wider conceptExtension (R5: Identification of the condition, problem or diagnosis (new))Element `ConditionDefinition.code` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.code` 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/ConditionDefinition|5.0.0 to R5: Subjective severity of condition (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ConditionDefinition.severity (severity)​maps to wider conceptExtension (R5: Subjective severity of condition (new))Element `ConditionDefinition.severity` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.severity` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Coding of the severity with a terminology is preferred, where possible.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/ConditionDefinition|5.0.0 to R5: Anatomical location, if relevant (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ConditionDefinition.bodySite (bodySite)​maps to wider conceptExtension (R5: Anatomical location, if relevant (new))Element `ConditionDefinition.bodySite` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.bodySite` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Only used if not implicit in code found in ConditionDefinition.code. 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/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.

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/ConditionDefinition|5.0.0 to R5: Stage/grade, usually assessed formally (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ConditionDefinition.stage (stage)​maps to wider conceptExtension (R5: Stage/grade, usually assessed formally (new))Element `ConditionDefinition.stage` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.stage` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/ConditionDefinition|5.0.0 to R5: Whether Severity is appropriate (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ConditionDefinition.hasSeverity (hasSeverity)​maps to wider conceptExtension (R5: Whether Severity is appropriate (new))Element `ConditionDefinition.hasSeverity` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.hasSeverity` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/ConditionDefinition|5.0.0 to R5: Whether bodySite is appropriate (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ConditionDefinition.hasBodySite (hasBodySite)​maps to wider conceptExtension (R5: Whether bodySite is appropriate (new))Element `ConditionDefinition.hasBodySite` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.hasBodySite` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/ConditionDefinition|5.0.0 to R5: Whether stage is appropriate (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ConditionDefinition.hasStage (hasStage)​maps to wider conceptExtension (R5: Whether stage is appropriate (new))Element `ConditionDefinition.hasStage` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.hasStage` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/ConditionDefinition|5.0.0 to R5: Formal Definition for the condition (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ConditionDefinition.definition (definition)​maps to wider conceptExtension (R5: Formal Definition for the condition (new))Element `ConditionDefinition.definition` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.definition` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/ConditionDefinition|5.0.0 to R5: Observations particularly relevant to this condition (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ConditionDefinition.observation (observation)​maps to wider conceptExtension (R5: Observations particularly relevant to this condition (new))Element `ConditionDefinition.observation` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.observation` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
ConditionDefinition.observation.category (category)​maps to wider conceptExtension.extension:category (R5: Category that is relevant (new))Element `ConditionDefinition.observation.category` is part of an existing definition because parent element `ConditionDefinition.observation` requires a cross-version extension. Element `ConditionDefinition.observation.category` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.observation.category` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
ConditionDefinition.observation.code (code)​maps to wider conceptExtension.extension:code (R5: Code for relevant Observation (new))Element `ConditionDefinition.observation.code` is part of an existing definition because parent element `ConditionDefinition.observation` requires a cross-version extension. Element `ConditionDefinition.observation.code` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.observation.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/ConditionDefinition|5.0.0 to R5: Medications particularly relevant for this condition (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ConditionDefinition.medication (medication)​maps to wider conceptExtension (R5: Medications particularly relevant for this condition (new))Element `ConditionDefinition.medication` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.medication` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
ConditionDefinition.medication.category (category)​maps to wider conceptExtension.extension:category (R5: Category that is relevant (new))Element `ConditionDefinition.medication.category` is part of an existing definition because parent element `ConditionDefinition.medication` requires a cross-version extension. Element `ConditionDefinition.medication.category` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.medication.category` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
ConditionDefinition.medication.code (code)​maps to wider conceptExtension.extension:code (R5: Code for relevant Medication (new))Element `ConditionDefinition.medication.code` is part of an existing definition because parent element `ConditionDefinition.medication` requires a cross-version extension. Element `ConditionDefinition.medication.code` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.medication.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/ConditionDefinition|5.0.0 to R5: Observation that suggets this condition (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ConditionDefinition.precondition (precondition)​maps to wider conceptExtension (R5: Observation that suggets this condition (new))Element `ConditionDefinition.precondition` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.precondition` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
ConditionDefinition.precondition.type (type)​maps to wider conceptExtension.extension:type (R5: sensitive | specific (new))Element `ConditionDefinition.precondition.type` is part of an existing definition because parent element `ConditionDefinition.precondition` requires a cross-version extension. Element `ConditionDefinition.precondition.type` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.precondition.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
ConditionDefinition.precondition.code (code)​maps to wider conceptExtension.extension:code (R5: Code for relevant Observation (new))Element `ConditionDefinition.precondition.code` is part of an existing definition because parent element `ConditionDefinition.precondition` requires a cross-version extension. Element `ConditionDefinition.precondition.code` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.precondition.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
ConditionDefinition.precondition.value[x] (value[x])​maps to wider conceptExtension.extension:value (R5: Value of Observation (new))Element `ConditionDefinition.precondition.value[x]` is part of an existing definition because parent element `ConditionDefinition.precondition` requires a cross-version extension. Element `ConditionDefinition.precondition.value[x]` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.precondition.value[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/ConditionDefinition|5.0.0 to R5: Appropriate team for this condition (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ConditionDefinition.team (team)​maps to wider conceptExtension (R5: Appropriate team for this condition (new))Element `ConditionDefinition.team` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.team` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/ConditionDefinition|5.0.0 to R5: Questionnaire for this condition (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ConditionDefinition.questionnaire (questionnaire)​maps to wider conceptExtension (R5: Questionnaire for this condition (new))Element `ConditionDefinition.questionnaire` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.questionnaire` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
ConditionDefinition.questionnaire.purpose (purpose)​maps to wider conceptExtension.extension:purpose (R5: preadmit | diff-diagnosis | outcome (new))Element `ConditionDefinition.questionnaire.purpose` is part of an existing definition because parent element `ConditionDefinition.questionnaire` requires a cross-version extension. Element `ConditionDefinition.questionnaire.purpose` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.questionnaire.purpose` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
ConditionDefinition.questionnaire.reference (reference)​maps to wider conceptExtension.extension:reference (R5: Specific Questionnaire (new))Element `ConditionDefinition.questionnaire.reference` is part of an existing definition because parent element `ConditionDefinition.questionnaire` requires a cross-version extension. Element `ConditionDefinition.questionnaire.reference` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.questionnaire.reference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 17 Mapping from http://hl7.org/fhir/StructureDefinition/ConditionDefinition|5.0.0 to R5: Plan that is appropriate (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ConditionDefinition.plan (plan)​maps to wider conceptExtension (R5: Plan that is appropriate (new))Element `ConditionDefinition.plan` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.plan` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
ConditionDefinition.plan.role (role)​maps to wider conceptExtension.extension:role (R5: Use for the plan (new))Element `ConditionDefinition.plan.role` is part of an existing definition because parent element `ConditionDefinition.plan` requires a cross-version extension. Element `ConditionDefinition.plan.role` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.plan.role` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
ConditionDefinition.plan.reference (reference)​maps to wider conceptExtension.extension:reference (R5: The actual plan (new))Element `ConditionDefinition.plan.reference` is part of an existing definition because parent element `ConditionDefinition.plan` requires a cross-version extension. Element `ConditionDefinition.plan.reference` is not mapped to FHIR R4, since FHIR R5 `ConditionDefinition` is not mapped. Element `ConditionDefinition.plan.reference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).