HL7 Version 2 to FHIR
1.0.0-ballot - ballot International flag

HL7 Version 2 to FHIR, published by HL7 International / Orders and Observations. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/v2-to-fhir/ and changes regularly. See the Directory of published versions

ConceptMap: Segment AL1 to AllergyIntolerance Map (Experimental)

Official URL: http://hl7.org/fhir/uv/v2mappings/segment-al1-to-allergyintolerance Version: 1.0.0-ballot
Active as of 2024-03-22 Computable Name: SegmentAL1ToAllergyIntolerance

Copyright/Legal: Copyright (c) 2020, HL7 International, Inc., All Rights Reserved.

This ConceptMap represents a mapping from the HL7 V2 Segment AL1 to the FHIR AllergyIntolerance Resource.

This ConceptMap represents the mapping from the HL7 V2 AL1 Segment to the FHIR AllergyIntolerance Resource. See also the FHIR Shorthand or the CSV Source.

HL7 v2Condition (IF True, args)HL7 FHIRComments
Sort OrderIdentifierNameData TypeCardinality - MinCardinality - MaxComputable ANTLRComputable FHIRPathNarrativeFHIR AttributeExtensionData TypeCardinality - MinCardinality - MaxData Type MappingVocabulary Mapping
(IS, ID, CE, CEN, CWE)
Assignment
0AL1AllergyIntolerance.clinicalStatus.coding.codeAllergyIntolerance.code01"active"While .clinicalStatus is not required, constraint ait-1 (AllergyIntolerance.clinicalStatus SHALL be present if verificationStatus is not entered-in-error.) does necessitate populating this element in the map as it's not possible to infer a verificationStatus of "entered-in-error" based on the data in AL1.
0AL1AllergyIntolerance.clinicalStatus.coding.systemAllergyIntolerance.uri01"http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical"
1AL1-1Set ID - AL1SI11This field doesn't warrant mapping
2AL1-2Allergen Type CodeCWE01AllergyIntolerance.categoryAllergyIntolerance.code0-1CWE[code]AllergenType[AllergyIntoleranceCategory]The FHIR table has a "required" binding. Do we need to expand the values in the FHIR table? Could other be used for: Miscellaneous allergy Miscellaneous contraindication Animal Allergy HL70127 is a user defined table
2AL1-2Allergen Type CodeCWE01AllergyIntolerance.category.extension.urlAllergyIntolerance.uri11"http://hl7.org/fhir/StructureDefinition/alternate-codes"
2AL1-2Allergen Type CodeCWE01AllergyIntolerance.category.extension.valueCodeableConceptAllergyIntolerance.CodeableConcept11CWE[CodeableConcept]AllergenType[AllergyIntoleranceOriginalCategory]
2AL1-2Allergen Type CodeCWE01AllergyIntolerance.typeAllergyIntolerance.code01CWE[code]AllergyType
3AL1-3Allergen Code/Mnemonic/DescriptionCWE11AllergyIntolerance.codeAllergyIntolerance.CodeableConcept01CWE[CodeableConcept]
4AL1-4Allergy Severity CodeCWE01If severity was used equivalent to criticalityAllergyIntolerance.criticalityAllergyIntolerance.code01CWE[code]AllergySeverity[AllergyIntolerance.criticality]Note that AllergyIntolerance.reaction.severity is available in FHIR but from a base standard perspective that is actually not the most appropriate and would require that AL1-6 is valued as well. However, a local implementation may have used vocabulary that better fits AllergyIntolerance.reaction.severity and should then consider that instead as a local variation. Note that the .reaction though is at a particular time, while .criticality is an overall assement that matches HL7 v2 generally better.
4AL1-4Allergy Severity CodeCWE01If severity was used equivalent to criticalityAllergyIntolerance.criticality.extension.urlAllergyIntolerance.uri11"http://hl7.org/fhir/StructureDefinition/alternate-codes"
4AL1-4Allergy Severity CodeCWE01If severity was used equivalent to criticalityAllergyIntolerance.criticality.extension.valueCodeableConceptAllergyIntolerance.CodeableConcept11CWE[CodeableConcept]AllergyTyp[AllergyIntolerance.criticality-original]
4AL1-4Allergy Severity CodeCWE01If severity was not used equivalent to criticalityNeed a local implementation extension.While AllergyIntolerance.reaction.severity would provide a potential mapping target, that is not clearly and unambiguously known at the standard level as the mapping to .criticality should be the "normal" mapping per the standard. Please enter a JIRA against the guide to help determine whether an HL7 extension would be appropriate to create.
5AL1-5Allergy Reaction CodeST0-1AllergyIntolerance.reaction.manifestation.textAllergyIntolerance.CodeableConcept01ST[CodeableConcept]AllergyIntolerance.reaction can repeat, presumably to capture both multiple manifestations of the reaction (rash and nausea) as well as reactions to independent exposures (last week and last month) - we may want to confirm this understanding.
6AL1-6Identification DateDT11AllergyIntolerance.onsetDateTimeAllergyIntolerance.dateTime01Withdrawn as of 2.7, Refer to IAM-11 Onset or IAM-13 Reported Date

Mapping from AL1 to AllergyIntolerance

ACTIVE (not intended for production usage). Published on 2024-03-22 by HL7 International / Orders and Observations (HL7 Orders and Observations Workgroup: http://www.hl7.org/Special/com..., Keith W. Boone: kboone@ainq.com, Rob Hausam: rrhausam@gmail.com). Copyright (c) 2020, HL7 International, Inc., All Rights Reserved.

This ConceptMap represents a mapping from the HL7 V2 Segment AL1 to the FHIR AllergyIntolerance Resource.


Group 1 Mapping from unspecified code system to unspecified code system

Source Concept DetailsRelationshipTarget Concept DetailsCommentProperties
Codes from vocabularymapvaluedatatypemapCodes from narrative
AL1"active"is equivalent toclinicalStatus.coding.codeclinicalStatus.coding.codeWhile .clinicalStatus is not required, constraint ait-1 (AllergyIntolerance.clinicalStatus SHALL be present if verificationStatus is not entered-in-error.) does necessitate populating this element in the map as it's not possible to infer a verificationStatus of "entered-in-error" based on the data in AL1.
AL1"http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical"is equivalent toclinicalStatus.coding.systemclinicalStatus.coding.system
AL1-2Allergen Type CodeAllergenType[AllergyIntoleranceCategory]CWE[code]is equivalent tocategorycategoryThe FHIR table has a "required" binding. Do we need to expand the values in the FHIR table? Could other be used for: Miscellaneous allergy Miscellaneous contraindication Animal Allergy HL70127 is a user defined table\
AL1-2Allergen Type Code"http://hl7.org/fhir/StructureDefinition/alternate-codes"is equivalent tocategory.extension[1].urlcategory.extension[1].url
AL1-2Allergen Type CodeAllergenType[AllergyIntoleranceOriginalCategory]CWE[CodeableConcept]is equivalent tocategory.extension[1].valueCodeableConceptcategory.extension[1].valueCodeableConcept
AL1-2Allergen Type CodeAllergyTypeCWE[code]is equivalent totypetype
AL1-3Allergen Code/Mnemonic/DescriptionCWE[CodeableConcept]is equivalent tocodecode
AL1-4Allergy Severity CodeAllergySeverity[AllergyIntolerance.criticality]CWE[code]is equivalent tocriticalitycriticalityIf severity was used equivalent to criticalityNote that AllergyIntolerance.reaction.severity is available in FHIR but from a base standard perspective that is actually not the most appropriate and would require that AL1-6 is valued as well. However, a local implementation may have used vocabulary that better fits AllergyIntolerance.reaction.severity and should then consider that instead as a local variation. Note that the .reaction though is at a particular time, while .criticality is an overall assement that matches HL7 v2 generally better.
AL1-4Allergy Severity Code"http://hl7.org/fhir/StructureDefinition/alternate-codes"is equivalent tocriticality.extension[1].urlcriticality.extension[1].urlIf severity was used equivalent to criticality
AL1-4Allergy Severity CodeAllergyTyp[AllergyIntolerance.criticality-original]CWE[CodeableConcept]is equivalent tocriticality.extension[1].valueCodeableConceptcriticality.extension[1].valueCodeableConceptIf severity was used equivalent to criticality
AL1-5Allergy Reaction CodeST[CodeableConcept]is equivalent toreaction.manifestation.textreaction.manifestation.textAllergyIntolerance.reaction can repeat, presumably to capture both multiple manifestations of the reaction (rash and nausea) as well as reactions to independent exposures (last week and last month) - we may want to confirm this understanding.\
AL1-6Identification Dateis equivalent toonsetDateTimeonsetDateTimeWithdrawn as of 2.7, Refer to IAM-11 Onset or IAM-13 Reported Date

Notes: