Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4 - 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="R2-AllergyIntolerance-element-map-to-R4"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R2-AllergyIntolerance-element-map-to-R4</b></p><a name="R2-AllergyIntolerance-element-map-to-R4"> </a><a name="hcR2-AllergyIntolerance-element-map-to-R4"> </a><p>Mapping from http://hl7.org/fhir/1.0 to http://hl7.org/fhir/4.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/AllergyIntolerance|1.0.2</code> to <a href="http://hl7.org/fhir/R4/allergyintolerance.html">AllergyIntoleranceversion: 4.0.1)</a></p><table class="grid"><tr><td colspan="2"><b>Source Concept Details</b></td><td><b>Relationship</b></td><td colspan="2"><b>Target Concept Details</b></td><td><b>Comment</b></td></tr><tr><td colspan="2"><b>Codes</b> from http://hl7.org/fhir/StructureDefinition/AllergyIntolerance|1.0.2</td><td/><td colspan="2" title="http://hl7.org/fhir/StructureDefinition/AllergyIntolerance|4.0.1"><b>Codes</b> from AllergyIntolerance</td><td/></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.meta</td><td style="border-left-width: 0px">meta</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">AllergyIntolerance.meta</td><td style="border-left-width: 0px">AllergyIntolerance.meta</td><td>Element `AllergyIntolerance.meta` is mapped to FHIR R4 element `AllergyIntolerance.meta` as `SourceIsBroaderThanTarget`.
The mappings for `AllergyIntolerance.meta` do not cover the following types: Meta.
The mappings for `AllergyIntolerance.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.implicitRules</td><td style="border-left-width: 0px">implicitRules</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">AllergyIntolerance.implicitRules</td><td style="border-left-width: 0px">AllergyIntolerance.implicitRules</td><td>Element `AllergyIntolerance.implicitRules` is mapped to FHIR R4 element `AllergyIntolerance.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 as much as possible.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.language</td><td style="border-left-width: 0px">language</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">AllergyIntolerance.language</td><td style="border-left-width: 0px">AllergyIntolerance.language</td><td>Element `AllergyIntolerance.language` is mapped to FHIR R4 element `AllergyIntolerance.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 style="border-right-width: 0px">AllergyIntolerance.text</td><td style="border-left-width: 0px">text</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">AllergyIntolerance.text</td><td style="border-left-width: 0px">AllergyIntolerance.text</td><td>Element `AllergyIntolerance.text` is mapped to FHIR R4 element `AllergyIntolerance.text` as `SourceIsBroaderThanTarget`.
The mappings for `AllergyIntolerance.text` do not cover the following types: Narrative.
The mappings for `AllergyIntolerance.text` do not cover the following types based on type expansion: div, status.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.contained</td><td style="border-left-width: 0px">contained</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">AllergyIntolerance.contained</td><td style="border-left-width: 0px">AllergyIntolerance.contained</td><td>Element `AllergyIntolerance.contained` is mapped to FHIR R4 element `AllergyIntolerance.contained` as `SourceIsBroaderThanTarget`.
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.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.identifier</td><td style="border-left-width: 0px">identifier</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">AllergyIntolerance.identifier</td><td style="border-left-width: 0px">AllergyIntolerance.identifier</td><td>Element `AllergyIntolerance.identifier` is mapped to FHIR R4 element `AllergyIntolerance.identifier` as `SourceIsBroaderThanTarget`.
The mappings for `AllergyIntolerance.identifier` do not cover the following types: Identifier.
The mappings for `AllergyIntolerance.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.onset</td><td style="border-left-width: 0px">onset</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">AllergyIntolerance.onset[x]</td><td style="border-left-width: 0px">AllergyIntolerance.onset[x]</td><td>Element `AllergyIntolerance.onset` is mapped to FHIR R4 element `AllergyIntolerance.onset[x]` as `Equivalent`.
The target context `AllergyIntolerance.onset[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `AllergyIntolerance`.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.recorder</td><td style="border-left-width: 0px">recorder</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">AllergyIntolerance.recorder</td><td style="border-left-width: 0px">AllergyIntolerance.recorder</td><td>Element `AllergyIntolerance.recorder` is mapped to FHIR R4 element `AllergyIntolerance.recorder` as `RelatedTo`.
The mappings for `AllergyIntolerance.recorder` do not cover the following types based on type expansion: display, reference.
The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `AllergyIntolerance.recorder` with unmapped reference targets: Patient, Practitioner.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.patient</td><td style="border-left-width: 0px">patient</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">AllergyIntolerance.patient</td><td style="border-left-width: 0px">AllergyIntolerance.patient</td><td>Element `AllergyIntolerance.patient` is mapped to FHIR R4 element `AllergyIntolerance.patient` as `SourceIsBroaderThanTarget`.
The mappings for `AllergyIntolerance.patient` do not cover the following types based on type expansion: display, reference.
The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `AllergyIntolerance.patient` with unmapped reference targets: Patient.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.reporter</td><td style="border-left-width: 0px">reporter</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">AllergyIntolerance.asserter</td><td style="border-left-width: 0px">AllergyIntolerance.asserter</td><td>Element `AllergyIntolerance.reporter` is mapped to FHIR R4 element `AllergyIntolerance.asserter` as `RelatedTo`.
The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `AllergyIntolerance.reporter` with unmapped reference targets: Patient, Practitioner, RelatedPerson.
The recorder takes repsonsibility for the content, but can reference the source from where they got it.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.substance</td><td style="border-left-width: 0px">substance</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">AllergyIntolerance.code</td><td style="border-left-width: 0px">AllergyIntolerance.code</td><td>Element `AllergyIntolerance.substance` is mapped to FHIR R4 element `AllergyIntolerance.code` as `Equivalent`.
It is strongly recommended that the substance be coded with a terminology, where possible. For example, some terminologies used include RxNorm, SNOMED CT, DM+D, NDFRT, ICD-9, IDC-10, UNI, ATC and CPT. Plain text should only be used if there is no appropriate terminology available. Additional details about a substance can be specified in the text.</td></tr><tr><td style="border-right-width: 0px; border-bottom-style: none">AllergyIntolerance.status</td><td style="border-left-width: 0px; border-bottom-style: none">status</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">AllergyIntolerance.clinicalStatus</td><td style="border-left-width: 0px">AllergyIntolerance.clinicalStatus</td><td>Element `AllergyIntolerance.status` is mapped to FHIR R4 element `AllergyIntolerance.clinicalStatus` as `RelatedTo`.
Element `AllergyIntolerance.status` is mapped to FHIR R4 element `AllergyIntolerance.verificationStatus` as `RelatedTo`.
Decision support would typically raise alerts for 'Unconfirmed', 'Confirmed', and 'Resolved' and ignore a 'Refuted' reaction. In particular, 'Refuted' may be useful for reconciliation of the Adverse Reaction List. Some implementations may choose to make this field mandatory.</td></tr><tr><td style="border-right-width: 0px; border-top-style: none"/><td style="border-top-style: none; border-left-width: 0px"/><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">AllergyIntolerance.verificationStatus</td><td style="border-left-width: 0px">AllergyIntolerance.verificationStatus</td><td>Element `AllergyIntolerance.status` is mapped to FHIR R4 element `AllergyIntolerance.clinicalStatus` as `RelatedTo`.
Element `AllergyIntolerance.status` is mapped to FHIR R4 element `AllergyIntolerance.verificationStatus` as `RelatedTo`.
Decision support would typically raise alerts for 'Unconfirmed', 'Confirmed', and 'Resolved' and ignore a 'Refuted' reaction. In particular, 'Refuted' may be useful for reconciliation of the Adverse Reaction List. Some implementations may choose to make this field mandatory.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.criticality</td><td style="border-left-width: 0px">criticality</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">AllergyIntolerance.criticality</td><td style="border-left-width: 0px">AllergyIntolerance.criticality</td><td>Element `AllergyIntolerance.criticality` is mapped to FHIR R4 element `AllergyIntolerance.criticality` as `Equivalent`.
The default criticality value for any propensity to an adverse reaction should be 'Low Risk', indicating at the very least a relative contraindication to deliberate or voluntary exposure to the Substance. 'High Risk' is flagged if the clinician has identified a propensity for a more serious or potentially life-threatening reaction, such as anaphylaxis, and implies an absolute contraindication to deliberate or voluntary exposure to the substance. If this element is missing, the criticality is unknown (though it may be known elsewhere).</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.type</td><td style="border-left-width: 0px">type</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">AllergyIntolerance.type</td><td style="border-left-width: 0px">AllergyIntolerance.type</td><td>Element `AllergyIntolerance.type` is mapped to FHIR R4 element `AllergyIntolerance.type` as `Equivalent`.
Allergic (typically immune-mediated) reactions have been traditionally regarded as an indicator for potential escalation to significant future risk. Contemporary knowledge suggests that some reactions previously thought to be immune-mediated are, in fact, non-immune, but in some cases can still pose a life threatening risk. It is acknowledged that many clinicians may not be in a position to distinguish the mechanism of a particular reaction. Often the term "allergy" is used rather generically and may overlap with the use of "intolerance" - in practice the boundaries between these two concepts may not be well-defined or understood. This data element is included nevertheless, because many legacy systems have captured this attribute. Immunologic testing may provide supporting evidence for the basis of the reaction and the causative substance, but no tests are 100% sensitive or specific for sensitivity to a particular substance. If, as is commonly the case, it is unclear whether the reaction is due to an allergy or an intolerance, then the type element should be omitted from the resource.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.category</td><td style="border-left-width: 0px">category</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">AllergyIntolerance.category</td><td style="border-left-width: 0px">AllergyIntolerance.category</td><td>Element `AllergyIntolerance.category` is mapped to FHIR R4 element `AllergyIntolerance.category` as `RelatedTo`.
This data element has been included because it is currently being captured in some clinical systems. This data can be derived from the Substance where coding systems are used, and is effectively redundant in that situation.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.lastOccurence</td><td style="border-left-width: 0px">lastOccurence</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">AllergyIntolerance.lastOccurrence</td><td style="border-left-width: 0px">AllergyIntolerance.lastOccurrence</td><td>Element `AllergyIntolerance.lastOccurence` is mapped to FHIR R4 element `AllergyIntolerance.lastOccurrence` as `Equivalent`.
This date may be replicated by one of the Onset of Reaction dates. Where a textual representation of the date of last occurrence is required e.g. 'In Childhood, '10 years ago' the Comment element should be used.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.note</td><td style="border-left-width: 0px">note</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">AllergyIntolerance.note</td><td style="border-left-width: 0px">AllergyIntolerance.note</td><td>Element `AllergyIntolerance.note` is mapped to FHIR R4 element `AllergyIntolerance.note` as `RelatedTo`.
The mappings for `AllergyIntolerance.note` do not cover the following types: Annotation.
The mappings for `AllergyIntolerance.note` do not cover the following types based on type expansion: author[x], text, time.
For example: including reason for flagging a seriousness of 'High Risk'; and instructions related to future exposure or administration of the Substance, such as administration within an Intensive Care Unit or under corticosteroid cover. The notes should be related to an allergy or intolerance as a condition in general and not related to any particular episode of it. For episode notes and descriptions, use AllergyIntolerance.event.description and AllergyIntolerance.event.notes.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.reaction</td><td style="border-left-width: 0px">reaction</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">AllergyIntolerance.reaction</td><td style="border-left-width: 0px">AllergyIntolerance.reaction</td><td>Element `AllergyIntolerance.reaction` is mapped to FHIR R4 element `AllergyIntolerance.reaction` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.reaction.substance</td><td style="border-left-width: 0px">substance</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">AllergyIntolerance.reaction.substance</td><td style="border-left-width: 0px">AllergyIntolerance.reaction.substance</td><td>Element `AllergyIntolerance.reaction.substance` is mapped to FHIR R4 element `AllergyIntolerance.reaction.substance` as `Equivalent`.
Coding of the specific substance with a terminology capable of triggering decision support should be used wherever possible. The substance field allows for the use of a specific substance or a group or class of substances, for example "Penicillins". The specific substance field could be used for Amoxycillin. Duplication is acceptable when a specific substance has been recorded in the 'substance' field.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.reaction.manifestation</td><td style="border-left-width: 0px">manifestation</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">AllergyIntolerance.reaction.manifestation</td><td style="border-left-width: 0px">AllergyIntolerance.reaction.manifestation</td><td>Element `AllergyIntolerance.reaction.manifestation` is mapped to FHIR R4 element `AllergyIntolerance.reaction.manifestation` as `Equivalent`.
Manifestation can be expressed as a single word, phrase or brief description. For example: nausea, rash or no reaction. It is preferable that manifestation should be coded with a terminology, where possible. The values entered here may be used to display on an application screen as part of a list of adverse reactions, as recommended in the UK NHS CUI guidelines. Terminologies commonly used include, but are not limited to, SNOMED CT or ICD10.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.reaction.description</td><td style="border-left-width: 0px">description</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">AllergyIntolerance.reaction.description</td><td style="border-left-width: 0px">AllergyIntolerance.reaction.description</td><td>Element `AllergyIntolerance.reaction.description` is mapped to FHIR R4 element `AllergyIntolerance.reaction.description` as `Equivalent`.
Use the description to provide any details of a particular event of the occurred reaction such as circumstances, reaction specifics, what happened before/after. Information, related to the event, but not describing a particular care should be captured in the comment field. For example: at the age of four, the patient was given penicillin for strep throat and subsequently developed severe hives.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.reaction.onset</td><td style="border-left-width: 0px">onset</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">AllergyIntolerance.reaction.onset</td><td style="border-left-width: 0px">AllergyIntolerance.reaction.onset</td><td>Element `AllergyIntolerance.reaction.onset` is mapped to FHIR R4 element `AllergyIntolerance.reaction.onset` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.reaction.severity</td><td style="border-left-width: 0px">severity</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">AllergyIntolerance.reaction.severity</td><td style="border-left-width: 0px">AllergyIntolerance.reaction.severity</td><td>Element `AllergyIntolerance.reaction.severity` is mapped to FHIR R4 element `AllergyIntolerance.reaction.severity` as `Equivalent`.
It is acknowledged that this assessment is very subjective. There may be some some specific practice domains where objective scales have been applied. Objective scales can be included in this model as extensions.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.reaction.exposureRoute</td><td style="border-left-width: 0px">exposureRoute</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">AllergyIntolerance.reaction.exposureRoute</td><td style="border-left-width: 0px">AllergyIntolerance.reaction.exposureRoute</td><td>Element `AllergyIntolerance.reaction.exposureRoute` is mapped to FHIR R4 element `AllergyIntolerance.reaction.exposureRoute` as `Equivalent`.
Coding of the route of exposure with a terminology should be used wherever possible.</td></tr><tr><td style="border-right-width: 0px">AllergyIntolerance.reaction.note</td><td style="border-left-width: 0px">note</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">AllergyIntolerance.reaction.note</td><td style="border-left-width: 0px">AllergyIntolerance.reaction.note</td><td>Element `AllergyIntolerance.reaction.note` is mapped to FHIR R4 element `AllergyIntolerance.reaction.note` as `RelatedTo`.
The mappings for `AllergyIntolerance.reaction.note` do not cover the following types: Annotation.
The mappings for `AllergyIntolerance.reaction.note` do not cover the following types based on type expansion: author[x], text, time.
Use this field to record information indirectly related to a particular event and not captured in the description. For example: Clinical records are no longer available, recorded based on information provided to the patient by her mother and her mother is deceased.</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/AllergyIntolerance|1.0.2</code> to <a href="StructureDefinition-ext-R2-AllergyIntolerance.meta.html">DSTU2: meta additional typesversion: 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>AllergyIntolerance.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>Extension (DSTU2: meta additional types)</td><td>Element `AllergyIntolerance.meta` is mapped to FHIR R4 element `AllergyIntolerance.meta` as `SourceIsBroaderThanTarget`.
The mappings for `AllergyIntolerance.meta` do not cover the following types: Meta.
The mappings for `AllergyIntolerance.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/AllergyIntolerance|1.0.2</code> to <a href="StructureDefinition-ext-R2-AllergyIntolerance.text.html">DSTU2: text additional typesversion: 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>AllergyIntolerance.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>Extension (DSTU2: text additional types)</td><td>Element `AllergyIntolerance.text` is mapped to FHIR R4 element `AllergyIntolerance.text` as `SourceIsBroaderThanTarget`.
The mappings for `AllergyIntolerance.text` do not cover the following types: Narrative.
The mappings for `AllergyIntolerance.text` do not cover the following types based on type expansion: div, status.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.</td></tr></table><hr/><p><b>Group 4 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/AllergyIntolerance|1.0.2</code> to <a href="StructureDefinition-ext-R2-AllergyIntolerance.identifier.html">DSTU2: identifier additional typesversion: 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>AllergyIntolerance.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>Extension (DSTU2: identifier additional types)</td><td>Element `AllergyIntolerance.identifier` is mapped to FHIR R4 element `AllergyIntolerance.identifier` as `SourceIsBroaderThanTarget`.
The mappings for `AllergyIntolerance.identifier` do not cover the following types: Identifier.
The mappings for `AllergyIntolerance.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.</td></tr></table><hr/><p><b>Group 5 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/AllergyIntolerance|1.0.2</code> to <a href="StructureDefinition-ext-R2-AllergyIntolerance.recordedDate.html">DSTU2: When recorded (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>AllergyIntolerance.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>Extension (DSTU2: When recorded (new))</td><td>Element `AllergyIntolerance.recordedDate` has a context of AllergyIntolerance based on following the parent source element upwards and mapping to `AllergyIntolerance`.
Element `AllergyIntolerance.recordedDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 6 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/AllergyIntolerance|1.0.2</code> to <a href="StructureDefinition-ext-R2-AllergyIntolerance.status.html">DSTU2: active | unconfirmed | confirmed | inactive | resolved | refuted | entered-in-errorversion: 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>AllergyIntolerance.status (status)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (DSTU2: active | unconfirmed | confirmed | inactive | resolved | refuted | entered-in-error)</td><td>Element `AllergyIntolerance.status` is mapped to FHIR R4 element `AllergyIntolerance.clinicalStatus` as `RelatedTo`.
Element `AllergyIntolerance.status` is mapped to FHIR R4 element `AllergyIntolerance.verificationStatus` as `RelatedTo`.
Decision support would typically raise alerts for 'Unconfirmed', 'Confirmed', and 'Resolved' and ignore a 'Refuted' reaction. In particular, 'Refuted' may be useful for reconciliation of the Adverse Reaction List. Some implementations may choose to make this field mandatory.</td></tr></table><hr/><p><b>Group 7 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/AllergyIntolerance|1.0.2</code> to <a href="StructureDefinition-ext-R2-AllergyIntolerance.category.html">DSTU2: food | medication | environment | other - Category of Substanceversion: 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>AllergyIntolerance.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>Extension (DSTU2: food | medication | environment | other - Category of Substance)</td><td>Element `AllergyIntolerance.category` is mapped to FHIR R4 element `AllergyIntolerance.category` as `RelatedTo`.
This data element has been included because it is currently being captured in some clinical systems. This data can be derived from the Substance where coding systems are used, and is effectively redundant in that situation.</td></tr></table><hr/><p><b>Group 8 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/AllergyIntolerance|1.0.2</code> to <a href="StructureDefinition-ext-R2-AllergyIntolerance.note.html">DSTU2: note additional typesversion: 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>AllergyIntolerance.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>Extension (DSTU2: note additional types)</td><td>Element `AllergyIntolerance.note` is mapped to FHIR R4 element `AllergyIntolerance.note` as `RelatedTo`.
The mappings for `AllergyIntolerance.note` do not cover the following types: Annotation.
The mappings for `AllergyIntolerance.note` do not cover the following types based on type expansion: author[x], text, time.
For example: including reason for flagging a seriousness of 'High Risk'; and instructions related to future exposure or administration of the Substance, such as administration within an Intensive Care Unit or under corticosteroid cover. The notes should be related to an allergy or intolerance as a condition in general and not related to any particular episode of it. For episode notes and descriptions, use AllergyIntolerance.event.description and AllergyIntolerance.event.notes.</td></tr></table><hr/><p><b>Group 9 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/AllergyIntolerance|1.0.2</code> to <a href="StructureDefinition-ext-R2-AllergyIntolerance.rea.certainty.html">DSTU2: unlikely | likely | confirmed - clinical certainty about the specific substance (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>AllergyIntolerance.reaction.certainty (certainty)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (DSTU2: unlikely | likely | confirmed - clinical certainty about the specific substance (new))</td><td>Element `AllergyIntolerance.reaction.certainty` has a context of AllergyIntolerance.reaction based on following the parent source element upwards and mapping to `AllergyIntolerance`.
Element `AllergyIntolerance.reaction.certainty` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 10 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/AllergyIntolerance|1.0.2</code> to <a href="StructureDefinition-ext-R2-AllergyIntolerance.rea.note.html">DSTU2: note additional typesversion: 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>AllergyIntolerance.reaction.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>Extension (DSTU2: note additional types)</td><td>Element `AllergyIntolerance.reaction.note` is mapped to FHIR R4 element `AllergyIntolerance.reaction.note` as `RelatedTo`.
The mappings for `AllergyIntolerance.reaction.note` do not cover the following types: Annotation.
The mappings for `AllergyIntolerance.reaction.note` do not cover the following types based on type expansion: author[x], text, time.
Use this field to record information indirectly related to a particular event and not captured in the description. For example: Clinical records are no longer available, recorded based on information provided to the patient by her mother and her mother is deceased.</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-r2.r4"/>
</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-r2.r4"/>
</extension>
</valueCode>
</extension>
<url
value="http://hl7.org/fhir/uv/xver/ConceptMap/R2-AllergyIntolerance-element-map-to-R4"/>
<version value="0.1.0"/>
<name value="R2AllergyIntoleranceElementMapToR4"/>
<title
value="Cross-version mapping for FHIR DSTU2 AllergyIntolerance to FHIR R4 AllergyIntolerance"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-03-17T16:04:02.8266005-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 DSTU2 AllergyIntolerance to FHIR R4."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<sourceCanonical value="http://hl7.org/fhir/1.0"/>
<targetUri value="http://hl7.org/fhir/4.0"/>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/AllergyIntolerance"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/StructureDefinition/AllergyIntolerance"/>
<targetVersion value="4.0.1"/>
<element>
<code value="AllergyIntolerance.meta"/>
<display value="meta"/>
<target>
<code value="AllergyIntolerance.meta"/>
<display value="AllergyIntolerance.meta"/>
<equivalence value="wider"/>
<comment
value="Element `AllergyIntolerance.meta` is mapped to FHIR R4 element `AllergyIntolerance.meta` as `SourceIsBroaderThanTarget`.
The mappings for `AllergyIntolerance.meta` do not cover the following types: Meta.
The mappings for `AllergyIntolerance.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.implicitRules"/>
<display value="implicitRules"/>
<target>
<code value="AllergyIntolerance.implicitRules"/>
<display value="AllergyIntolerance.implicitRules"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.implicitRules` is mapped to FHIR R4 element `AllergyIntolerance.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 as much as possible."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.language"/>
<display value="language"/>
<target>
<code value="AllergyIntolerance.language"/>
<display value="AllergyIntolerance.language"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.language` is mapped to FHIR R4 element `AllergyIntolerance.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="AllergyIntolerance.text"/>
<display value="text"/>
<target>
<code value="AllergyIntolerance.text"/>
<display value="AllergyIntolerance.text"/>
<equivalence value="wider"/>
<comment
value="Element `AllergyIntolerance.text` is mapped to FHIR R4 element `AllergyIntolerance.text` as `SourceIsBroaderThanTarget`.
The mappings for `AllergyIntolerance.text` do not cover the following types: Narrative.
The mappings for `AllergyIntolerance.text` do not cover the following types based on type expansion: div, status.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.contained"/>
<display value="contained"/>
<target>
<code value="AllergyIntolerance.contained"/>
<display value="AllergyIntolerance.contained"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.contained` is mapped to FHIR R4 element `AllergyIntolerance.contained` as `SourceIsBroaderThanTarget`.
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."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.identifier"/>
<display value="identifier"/>
<target>
<code value="AllergyIntolerance.identifier"/>
<display value="AllergyIntolerance.identifier"/>
<equivalence value="wider"/>
<comment
value="Element `AllergyIntolerance.identifier` is mapped to FHIR R4 element `AllergyIntolerance.identifier` as `SourceIsBroaderThanTarget`.
The mappings for `AllergyIntolerance.identifier` do not cover the following types: Identifier.
The mappings for `AllergyIntolerance.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.onset"/>
<display value="onset"/>
<target>
<code value="AllergyIntolerance.onset[x]"/>
<display value="AllergyIntolerance.onset[x]"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.onset` is mapped to FHIR R4 element `AllergyIntolerance.onset[x]` as `Equivalent`.
The target context `AllergyIntolerance.onset[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `AllergyIntolerance`."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.recorder"/>
<display value="recorder"/>
<target>
<code value="AllergyIntolerance.recorder"/>
<display value="AllergyIntolerance.recorder"/>
<equivalence value="wider"/>
<comment
value="Element `AllergyIntolerance.recorder` is mapped to FHIR R4 element `AllergyIntolerance.recorder` as `RelatedTo`.
The mappings for `AllergyIntolerance.recorder` do not cover the following types based on type expansion: display, reference.
The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `AllergyIntolerance.recorder` with unmapped reference targets: Patient, Practitioner."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.patient"/>
<display value="patient"/>
<target>
<code value="AllergyIntolerance.patient"/>
<display value="AllergyIntolerance.patient"/>
<equivalence value="wider"/>
<comment
value="Element `AllergyIntolerance.patient` is mapped to FHIR R4 element `AllergyIntolerance.patient` as `SourceIsBroaderThanTarget`.
The mappings for `AllergyIntolerance.patient` do not cover the following types based on type expansion: display, reference.
The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `AllergyIntolerance.patient` with unmapped reference targets: Patient."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.reporter"/>
<display value="reporter"/>
<target>
<code value="AllergyIntolerance.asserter"/>
<display value="AllergyIntolerance.asserter"/>
<equivalence value="relatedto"/>
<comment
value="Element `AllergyIntolerance.reporter` is mapped to FHIR R4 element `AllergyIntolerance.asserter` as `RelatedTo`.
The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `AllergyIntolerance.reporter` with unmapped reference targets: Patient, Practitioner, RelatedPerson.
The recorder takes repsonsibility for the content, but can reference the source from where they got it."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.substance"/>
<display value="substance"/>
<target>
<code value="AllergyIntolerance.code"/>
<display value="AllergyIntolerance.code"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.substance` is mapped to FHIR R4 element `AllergyIntolerance.code` as `Equivalent`.
It is strongly recommended that the substance be coded with a terminology, where possible. For example, some terminologies used include RxNorm, SNOMED CT, DM+D, NDFRT, ICD-9, IDC-10, UNI, ATC and CPT. Plain text should only be used if there is no appropriate terminology available. Additional details about a substance can be specified in the text."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.status"/>
<display value="status"/>
<target>
<code value="AllergyIntolerance.clinicalStatus"/>
<display value="AllergyIntolerance.clinicalStatus"/>
<equivalence value="relatedto"/>
<comment
value="Element `AllergyIntolerance.status` is mapped to FHIR R4 element `AllergyIntolerance.clinicalStatus` as `RelatedTo`.
Element `AllergyIntolerance.status` is mapped to FHIR R4 element `AllergyIntolerance.verificationStatus` as `RelatedTo`.
Decision support would typically raise alerts for 'Unconfirmed', 'Confirmed', and 'Resolved' and ignore a 'Refuted' reaction. In particular, 'Refuted' may be useful for reconciliation of the Adverse Reaction List. Some implementations may choose to make this field mandatory."/>
</target>
<target>
<code value="AllergyIntolerance.verificationStatus"/>
<display value="AllergyIntolerance.verificationStatus"/>
<equivalence value="relatedto"/>
<comment
value="Element `AllergyIntolerance.status` is mapped to FHIR R4 element `AllergyIntolerance.clinicalStatus` as `RelatedTo`.
Element `AllergyIntolerance.status` is mapped to FHIR R4 element `AllergyIntolerance.verificationStatus` as `RelatedTo`.
Decision support would typically raise alerts for 'Unconfirmed', 'Confirmed', and 'Resolved' and ignore a 'Refuted' reaction. In particular, 'Refuted' may be useful for reconciliation of the Adverse Reaction List. Some implementations may choose to make this field mandatory."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.criticality"/>
<display value="criticality"/>
<target>
<code value="AllergyIntolerance.criticality"/>
<display value="AllergyIntolerance.criticality"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.criticality` is mapped to FHIR R4 element `AllergyIntolerance.criticality` as `Equivalent`.
The default criticality value for any propensity to an adverse reaction should be 'Low Risk', indicating at the very least a relative contraindication to deliberate or voluntary exposure to the Substance. 'High Risk' is flagged if the clinician has identified a propensity for a more serious or potentially life-threatening reaction, such as anaphylaxis, and implies an absolute contraindication to deliberate or voluntary exposure to the substance. If this element is missing, the criticality is unknown (though it may be known elsewhere)."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.type"/>
<display value="type"/>
<target>
<code value="AllergyIntolerance.type"/>
<display value="AllergyIntolerance.type"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.type` is mapped to FHIR R4 element `AllergyIntolerance.type` as `Equivalent`.
Allergic (typically immune-mediated) reactions have been traditionally regarded as an indicator for potential escalation to significant future risk. Contemporary knowledge suggests that some reactions previously thought to be immune-mediated are, in fact, non-immune, but in some cases can still pose a life threatening risk. It is acknowledged that many clinicians may not be in a position to distinguish the mechanism of a particular reaction. Often the term "allergy" is used rather generically and may overlap with the use of "intolerance" - in practice the boundaries between these two concepts may not be well-defined or understood. This data element is included nevertheless, because many legacy systems have captured this attribute. Immunologic testing may provide supporting evidence for the basis of the reaction and the causative substance, but no tests are 100% sensitive or specific for sensitivity to a particular substance. If, as is commonly the case, it is unclear whether the reaction is due to an allergy or an intolerance, then the type element should be omitted from the resource."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.category"/>
<display value="category"/>
<target>
<code value="AllergyIntolerance.category"/>
<display value="AllergyIntolerance.category"/>
<equivalence value="wider"/>
<comment
value="Element `AllergyIntolerance.category` is mapped to FHIR R4 element `AllergyIntolerance.category` as `RelatedTo`.
This data element has been included because it is currently being captured in some clinical systems. This data can be derived from the Substance where coding systems are used, and is effectively redundant in that situation."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.lastOccurence"/>
<display value="lastOccurence"/>
<target>
<code value="AllergyIntolerance.lastOccurrence"/>
<display value="AllergyIntolerance.lastOccurrence"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.lastOccurence` is mapped to FHIR R4 element `AllergyIntolerance.lastOccurrence` as `Equivalent`.
This date may be replicated by one of the Onset of Reaction dates. Where a textual representation of the date of last occurrence is required e.g. 'In Childhood, '10 years ago' the Comment element should be used."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.note"/>
<display value="note"/>
<target>
<code value="AllergyIntolerance.note"/>
<display value="AllergyIntolerance.note"/>
<equivalence value="wider"/>
<comment
value="Element `AllergyIntolerance.note` is mapped to FHIR R4 element `AllergyIntolerance.note` as `RelatedTo`.
The mappings for `AllergyIntolerance.note` do not cover the following types: Annotation.
The mappings for `AllergyIntolerance.note` do not cover the following types based on type expansion: author[x], text, time.
For example: including reason for flagging a seriousness of 'High Risk'; and instructions related to future exposure or administration of the Substance, such as administration within an Intensive Care Unit or under corticosteroid cover. The notes should be related to an allergy or intolerance as a condition in general and not related to any particular episode of it. For episode notes and descriptions, use AllergyIntolerance.event.description and AllergyIntolerance.event.notes."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.reaction"/>
<display value="reaction"/>
<target>
<code value="AllergyIntolerance.reaction"/>
<display value="AllergyIntolerance.reaction"/>
<equivalence value="wider"/>
<comment
value="Element `AllergyIntolerance.reaction` is mapped to FHIR R4 element `AllergyIntolerance.reaction` as `Equivalent`."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.reaction.substance"/>
<display value="substance"/>
<target>
<code value="AllergyIntolerance.reaction.substance"/>
<display value="AllergyIntolerance.reaction.substance"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.reaction.substance` is mapped to FHIR R4 element `AllergyIntolerance.reaction.substance` as `Equivalent`.
Coding of the specific substance with a terminology capable of triggering decision support should be used wherever possible. The substance field allows for the use of a specific substance or a group or class of substances, for example "Penicillins". The specific substance field could be used for Amoxycillin. Duplication is acceptable when a specific substance has been recorded in the 'substance' field."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.reaction.manifestation"/>
<display value="manifestation"/>
<target>
<code value="AllergyIntolerance.reaction.manifestation"/>
<display value="AllergyIntolerance.reaction.manifestation"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.reaction.manifestation` is mapped to FHIR R4 element `AllergyIntolerance.reaction.manifestation` as `Equivalent`.
Manifestation can be expressed as a single word, phrase or brief description. For example: nausea, rash or no reaction. It is preferable that manifestation should be coded with a terminology, where possible. The values entered here may be used to display on an application screen as part of a list of adverse reactions, as recommended in the UK NHS CUI guidelines. Terminologies commonly used include, but are not limited to, SNOMED CT or ICD10."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.reaction.description"/>
<display value="description"/>
<target>
<code value="AllergyIntolerance.reaction.description"/>
<display value="AllergyIntolerance.reaction.description"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.reaction.description` is mapped to FHIR R4 element `AllergyIntolerance.reaction.description` as `Equivalent`.
Use the description to provide any details of a particular event of the occurred reaction such as circumstances, reaction specifics, what happened before/after. Information, related to the event, but not describing a particular care should be captured in the comment field. For example: at the age of four, the patient was given penicillin for strep throat and subsequently developed severe hives."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.reaction.onset"/>
<display value="onset"/>
<target>
<code value="AllergyIntolerance.reaction.onset"/>
<display value="AllergyIntolerance.reaction.onset"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.reaction.onset` is mapped to FHIR R4 element `AllergyIntolerance.reaction.onset` as `Equivalent`."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.reaction.severity"/>
<display value="severity"/>
<target>
<code value="AllergyIntolerance.reaction.severity"/>
<display value="AllergyIntolerance.reaction.severity"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.reaction.severity` is mapped to FHIR R4 element `AllergyIntolerance.reaction.severity` as `Equivalent`.
It is acknowledged that this assessment is very subjective. There may be some some specific practice domains where objective scales have been applied. Objective scales can be included in this model as extensions."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.reaction.exposureRoute"/>
<display value="exposureRoute"/>
<target>
<code value="AllergyIntolerance.reaction.exposureRoute"/>
<display value="AllergyIntolerance.reaction.exposureRoute"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.reaction.exposureRoute` is mapped to FHIR R4 element `AllergyIntolerance.reaction.exposureRoute` as `Equivalent`.
Coding of the route of exposure with a terminology should be used wherever possible."/>
</target>
</element>
<element>
<code value="AllergyIntolerance.reaction.note"/>
<display value="note"/>
<target>
<code value="AllergyIntolerance.reaction.note"/>
<display value="AllergyIntolerance.reaction.note"/>
<equivalence value="wider"/>
<comment
value="Element `AllergyIntolerance.reaction.note` is mapped to FHIR R4 element `AllergyIntolerance.reaction.note` as `RelatedTo`.
The mappings for `AllergyIntolerance.reaction.note` do not cover the following types: Annotation.
The mappings for `AllergyIntolerance.reaction.note` do not cover the following types based on type expansion: author[x], text, time.
Use this field to record information indirectly related to a particular event and not captured in the description. For example: Clinical records are no longer available, recorded based on information provided to the patient by her mother and her mother is deceased."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/AllergyIntolerance"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-AllergyIntolerance.meta"/>
<targetVersion value="0.1.0"/>
<element>
<code value="AllergyIntolerance.meta"/>
<display value="meta"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.meta` is mapped to FHIR R4 element `AllergyIntolerance.meta` as `SourceIsBroaderThanTarget`.
The mappings for `AllergyIntolerance.meta` do not cover the following types: Meta.
The mappings for `AllergyIntolerance.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/AllergyIntolerance"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-AllergyIntolerance.text"/>
<targetVersion value="0.1.0"/>
<element>
<code value="AllergyIntolerance.text"/>
<display value="text"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.text` is mapped to FHIR R4 element `AllergyIntolerance.text` as `SourceIsBroaderThanTarget`.
The mappings for `AllergyIntolerance.text` do not cover the following types: Narrative.
The mappings for `AllergyIntolerance.text` do not cover the following types based on type expansion: div, status.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/AllergyIntolerance"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-AllergyIntolerance.identifier"/>
<targetVersion value="0.1.0"/>
<element>
<code value="AllergyIntolerance.identifier"/>
<display value="identifier"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.identifier` is mapped to FHIR R4 element `AllergyIntolerance.identifier` as `SourceIsBroaderThanTarget`.
The mappings for `AllergyIntolerance.identifier` do not cover the following types: Identifier.
The mappings for `AllergyIntolerance.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/AllergyIntolerance"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-AllergyIntolerance.recordedDate"/>
<targetVersion value="0.1.0"/>
<element>
<code value="AllergyIntolerance.recordedDate"/>
<display value="recordedDate"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.recordedDate` has a context of AllergyIntolerance based on following the parent source element upwards and mapping to `AllergyIntolerance`.
Element `AllergyIntolerance.recordedDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/AllergyIntolerance"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-AllergyIntolerance.status"/>
<targetVersion value="0.1.0"/>
<element>
<code value="AllergyIntolerance.status"/>
<display value="status"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `AllergyIntolerance.status` is mapped to FHIR R4 element `AllergyIntolerance.clinicalStatus` as `RelatedTo`.
Element `AllergyIntolerance.status` is mapped to FHIR R4 element `AllergyIntolerance.verificationStatus` as `RelatedTo`.
Decision support would typically raise alerts for 'Unconfirmed', 'Confirmed', and 'Resolved' and ignore a 'Refuted' reaction. In particular, 'Refuted' may be useful for reconciliation of the Adverse Reaction List. Some implementations may choose to make this field mandatory."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/AllergyIntolerance"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-AllergyIntolerance.category"/>
<targetVersion value="0.1.0"/>
<element>
<code value="AllergyIntolerance.category"/>
<display value="category"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.category` is mapped to FHIR R4 element `AllergyIntolerance.category` as `RelatedTo`.
This data element has been included because it is currently being captured in some clinical systems. This data can be derived from the Substance where coding systems are used, and is effectively redundant in that situation."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/AllergyIntolerance"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-AllergyIntolerance.note"/>
<targetVersion value="0.1.0"/>
<element>
<code value="AllergyIntolerance.note"/>
<display value="note"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.note` is mapped to FHIR R4 element `AllergyIntolerance.note` as `RelatedTo`.
The mappings for `AllergyIntolerance.note` do not cover the following types: Annotation.
The mappings for `AllergyIntolerance.note` do not cover the following types based on type expansion: author[x], text, time.
For example: including reason for flagging a seriousness of 'High Risk'; and instructions related to future exposure or administration of the Substance, such as administration within an Intensive Care Unit or under corticosteroid cover. The notes should be related to an allergy or intolerance as a condition in general and not related to any particular episode of it. For episode notes and descriptions, use AllergyIntolerance.event.description and AllergyIntolerance.event.notes."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/AllergyIntolerance"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-AllergyIntolerance.reaction.certainty"/>
<targetVersion value="0.1.0"/>
<element>
<code value="AllergyIntolerance.reaction.certainty"/>
<display value="certainty"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.reaction.certainty` has a context of AllergyIntolerance.reaction based on following the parent source element upwards and mapping to `AllergyIntolerance`.
Element `AllergyIntolerance.reaction.certainty` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/AllergyIntolerance"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-AllergyIntolerance.reaction.note"/>
<targetVersion value="0.1.0"/>
<element>
<code value="AllergyIntolerance.reaction.note"/>
<display value="note"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="Element `AllergyIntolerance.reaction.note` is mapped to FHIR R4 element `AllergyIntolerance.reaction.note` as `RelatedTo`.
The mappings for `AllergyIntolerance.reaction.note` do not cover the following types: Annotation.
The mappings for `AllergyIntolerance.reaction.note` do not cover the following types based on type expansion: author[x], text, time.
Use this field to record information indirectly related to a particular event and not captured in the description. For example: Clinical records are no longer available, recorded based on information provided to the patient by her mother and her mother is deceased."/>
</target>
</element>
</group>
</ConceptMap>
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r2.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