Cross Border Data Exchange IG
1.0.0 - CI Build International flag

Cross Border Data Exchange IG, published by IEHR-Workgroup. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/InteropEHRate-project/cross-border-data-exchange/ and changes regularly. See the Directory of published versions

ValueSet: CombinedAllergy - IEHR

Official URL: http://interopehrate.eu/fhir/ValueSet/CombinedAllergy-IEHR Version: 1.0.0
Draft as of 2024-04-08 Computable Name: CombinedAllergyIEHR

ValueSet with all relevant codes for the Allergy-IEHR

References

Content explanation

This ValueSet contains a list of codes from which at least one must be part of the concept in the code attribute of the AllergyIntolerance-IEHR profile. Each of the ValueSets that are a part of this set contains codes for a specific use case:

  • if the cause is a drug a code from the WHO ATC - IPS ValueSet should be used
  • if only a general allergen is given a code from the ATCAllergens - IEHR ValueSet should be used
  • if the cause can not be represented as one of the other use cases a code from the AllergySnomed - IEHR ValueSet can be used. This should be the last resort, as not all countries have a snomed license and as such this codes might not be usable by all organizations
  • if there is no allergy or no allergy is known a code from the Absent or Unknown Allergies - IPS ValueSet should be used
  • if the local code provided is not in one of the ValueSets above and the semantic translator could not translate it into one such code, it should instead add the nullflavor 'OTH' from the system http://terminology.hl7.org/CodeSystem/v3-NullFlavor

While the validator will accept resources where the concept has codes from different use cases, this behaviour is not intended and can cause issues. The use cases and ValueSet are designed to be unambiguous and as such it should not be possible to use codes from different use cases with the same meaning.

A valid concept should contain the original/local codes provided by the original author and must contain an additional code, with either the same or the closest possible meaning to the local code, from one of the use cases, if the original code is not from this ValueSet.

Logical Definition (CLD)

This value set includes codes based on the following rules:

  • Import all the codes that are contained in AllergySnomed - IEHR
  • Import all the codes that are contained in WHO ATC - IPS
  • Import all the codes that are contained in ATCAllergens - IEHR
  • Import all the codes that are contained in Absent or Unknown Allergies - IPS
  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-NullFlavor
    CodeDisplayDefinition
    OTH other **Description:**The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system).

    **Usage Notes**: This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to \*any\* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc.

    With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE.

 

Expansion

No Expansion for this valueset (Unsupported Code System Version)


Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code