Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R5-DetectedIssue-element-map-to-R4 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R5DetectedIssueElementMapToR4 | ||
This ConceptMap represents cross-version mappings for elements from a FHIR R5 DetectedIssue 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/DetectedIssue|5.0.0 to DetectedIssueversion: 4.0.1)
| Source Code | Relationship | Target Code | Comment |
| DetectedIssue.meta (meta) | is equivalent to | DetectedIssue.meta | Element `DetectedIssue.meta` is mapped to FHIR R4 element `DetectedIssue.meta` as `Equivalent`. |
| DetectedIssue.implicitRules (implicitRules) | is equivalent to | DetectedIssue.implicitRules | Element `DetectedIssue.implicitRules` is mapped to FHIR R4 element `DetectedIssue.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. |
| DetectedIssue.language (language) | is equivalent to | DetectedIssue.language | Element `DetectedIssue.language` is mapped to FHIR R4 element `DetectedIssue.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). |
| DetectedIssue.text (text) | is equivalent to | DetectedIssue.text | Element `DetectedIssue.text` is mapped to FHIR R4 element `DetectedIssue.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. |
| DetectedIssue.contained (contained) | is equivalent to | DetectedIssue.contained | Element `DetectedIssue.contained` is mapped to FHIR R4 element `DetectedIssue.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. |
| DetectedIssue.identifier (identifier) | is equivalent to | DetectedIssue.identifier | Element `DetectedIssue.identifier` is mapped to FHIR R4 element `DetectedIssue.identifier` as `Equivalent`. |
| DetectedIssue.status (status) | maps to wider concept | DetectedIssue.status | Element `DetectedIssue.status` is mapped to FHIR R4 element `DetectedIssue.status` as `RelatedTo`. The mappings for `DetectedIssue.status` do not allow expression of the necessary codes, per the bindings on the source and target. The target context `DetectedIssue.status` is a modifier element, so this extension does not need to be defined as a modifier. This element is labeled as a modifier because the status contains the code entered-in-error that marks the issue as not currently valid. |
| DetectedIssue.code (code) | is equivalent to | DetectedIssue.code | Element `DetectedIssue.code` is mapped to FHIR R4 element `DetectedIssue.code` as `Equivalent`. |
| DetectedIssue.severity (severity) | is equivalent to | DetectedIssue.severity | Element `DetectedIssue.severity` is mapped to FHIR R4 element `DetectedIssue.severity` as `Equivalent`. |
| DetectedIssue.subject (subject) | maps to wider concept | DetectedIssue.patient | Element `DetectedIssue.subject` is mapped to FHIR R4 element `DetectedIssue.patient` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DetectedIssue.subject` with unmapped reference targets: BiologicallyDerivedProduct, Device, Group, Location, Medication, NutritionProduct, Organization, Practitioner, Procedure, Substance. |
| DetectedIssue.identified[x] (identified[x]) | is equivalent to | DetectedIssue.identified[x] | Element `DetectedIssue.identified[x]` is mapped to FHIR R4 element `DetectedIssue.identified[x]` as `Equivalent`. The target context `DetectedIssue.identified[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DetectedIssue`. |
| DetectedIssue.author (author) | maps to wider concept | DetectedIssue.author | Element `DetectedIssue.author` is mapped to FHIR R4 element `DetectedIssue.author` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DetectedIssue.author` with unmapped reference targets: Patient, RelatedPerson. |
| DetectedIssue.implicated (implicated) | is equivalent to | DetectedIssue.implicated | Element `DetectedIssue.implicated` is mapped to FHIR R4 element `DetectedIssue.implicated` as `Equivalent`. There's an implicit constraint on the number of implicated resources based on DetectedIssue.type; e.g. For drug-drug, there would be more than one. For timing, there would typically only be one. |
| DetectedIssue.evidence (evidence) | maps to wider concept | DetectedIssue.evidence | Element `DetectedIssue.evidence` is mapped to FHIR R4 element `DetectedIssue.evidence` as `Equivalent`. |
| DetectedIssue.evidence.code (code) | is equivalent to | DetectedIssue.evidence.code | Element `DetectedIssue.evidence.code` is mapped to FHIR R4 element `DetectedIssue.evidence.code` as `Equivalent`. |
| DetectedIssue.evidence.detail (detail) | is equivalent to | DetectedIssue.evidence.detail | Element `DetectedIssue.evidence.detail` is mapped to FHIR R4 element `DetectedIssue.evidence.detail` as `Equivalent`. |
| DetectedIssue.detail (detail) | is equivalent to | DetectedIssue.detail | Element `DetectedIssue.detail` is mapped to FHIR R4 element `DetectedIssue.detail` as `Equivalent`. Should focus on information not covered elsewhere as discrete data - no need to duplicate the narrative. |
| DetectedIssue.reference (reference) | is equivalent to | DetectedIssue.reference | Element `DetectedIssue.reference` is mapped to FHIR R4 element `DetectedIssue.reference` as `Equivalent`. |
| DetectedIssue.mitigation (mitigation) | maps to wider concept | DetectedIssue.mitigation | Element `DetectedIssue.mitigation` is mapped to FHIR R4 element `DetectedIssue.mitigation` as `Equivalent`. |
| DetectedIssue.mitigation.action (action) | is equivalent to | DetectedIssue.mitigation.action | Element `DetectedIssue.mitigation.action` is mapped to FHIR R4 element `DetectedIssue.mitigation.action` as `Equivalent`. The "text" component can be used for detail or when no appropriate code exists. |
| DetectedIssue.mitigation.date (date) | is equivalent to | DetectedIssue.mitigation.date | Element `DetectedIssue.mitigation.date` is mapped to FHIR R4 element `DetectedIssue.mitigation.date` as `Equivalent`. This might not be the same as when the mitigating step was actually taken. |
| DetectedIssue.mitigation.author (author) | is equivalent to | DetectedIssue.mitigation.author | Element `DetectedIssue.mitigation.author` is mapped to FHIR R4 element `DetectedIssue.mitigation.author` as `Equivalent`. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/DetectedIssue|5.0.0 to R5: preliminary | final | entered-in-error | mitigated additional codesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DetectedIssue.status (status) | is equivalent to | Extension (R5: preliminary | final | entered-in-error | mitigated additional codes) | Element `DetectedIssue.status` is mapped to FHIR R4 element `DetectedIssue.status` as `RelatedTo`. The mappings for `DetectedIssue.status` do not allow expression of the necessary codes, per the bindings on the source and target. The target context `DetectedIssue.status` is a modifier element, so this extension does not need to be defined as a modifier. This element is labeled as a modifier because the status contains the code entered-in-error that marks the issue as not currently valid. |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/DetectedIssue|5.0.0 to R5: Type of detected issue, e.g. drug-drug, duplicate therapy, etc (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DetectedIssue.category (category) | maps to wider concept | Extension (R5: Type of detected issue, e.g. drug-drug, duplicate therapy, etc (new)) | Element `DetectedIssue.category` has a context of DetectedIssue based on following the parent source element upwards and mapping to `DetectedIssue`. Element `DetectedIssue.category` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). In addition to the required category valueset, this element allows various categorization schemes based on the owner’s definition of the category and effectively multiple categories can be used at once. The level of granularity is defined by the category concepts in the value set. |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/DetectedIssue|5.0.0 to R5: Encounter detected issue is part of (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DetectedIssue.encounter (encounter) | maps to wider concept | Extension (R5: Encounter detected issue is part of (new)) | Element `DetectedIssue.encounter` has a context of DetectedIssue based on following the parent source element upwards and mapping to `DetectedIssue`. Element `DetectedIssue.encounter` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This will typically be the encounter the DetectedIssue was created during, but some DetectedIssues may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission lab tests). |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/DetectedIssue|5.0.0 to R5: Additional notes about the mitigation (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DetectedIssue.mitigation.note (note) | maps to wider concept | Extension (R5: Additional notes about the mitigation (new)) | Element `DetectedIssue.mitigation.note` has a context of DetectedIssue.mitigation based on following the parent source element upwards and mapping to `DetectedIssue`. Element `DetectedIssue.mitigation.note` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r5.r4#0.1.0 based on FHIR 4.0.1. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change