CH-AllergyIntolerance (R4)
2.0.1 - trial-use Switzerland flag

This page is part of the CH-AllergyIntolerance (R4) (v2.0.1: STU 2) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions


Official URL: Version: 2.0.1
Active as of 2023-12-28 Computable Name: CHAllergyIntolerance

Copyright/Legal: CC0-1.0


Swiss Implementation Guide for Allergy & Intolerance based on the recommendations of the interprofessional working group EPR (IPAG), as well on Allergy Intolerance IPS as near as reasonable and influenced further on the “Implementation Guide for Use of SNOMED CT in Documentation of Allergy, Non-allergic Hypersensitivity and Intolerance” which is or was still under construction by the time of creating this IG.

Download: You can download this implementation guide in npm format from here.


The goal of this IG is

  • the exchange of allergies and intolerances in a structured document (profile developed), e.g. in the context of the Swiss EPR
  • as a requirement on how allergy and intolerances are to be used, referenced or derived in order to obtain interoperability in swiss projects (and therefore other IGs), e.g. in the context of vaccination or transition of care
  • clarify the usage of adverse sensitivity data (which encompasses allergy, non-allergic hypersensitivity and intolerance) by providing use cases and thus accelerating consistent implementation as intended by IPAG and the Allergies/Hypersensitivity and Intolerance Clinical Reference Group of Snomed CT.

Must Support

The use of Must Support is in the sense of the Guidelines for Swiss IG developments:

“Required if known. If the sending application has data for the element, it is required to populate the element with a non-empty value. If the value is not known, the element may be omitted. A receiving application may ignore the information conveyed by the element. A receiving application shall not raise an error solely due to the presence or absence of the element.”

The Must Support flags for the AllergyIntolerance resource have been set as in AllergyIntolerance IPS if also part of the IPAG recommendations. Besides that reaction.substance and category have been flagged because these fields play a importante role in the mentioned recommendations.

The extensions defined by the interprofessional working group EPR (IPAG) have no must support flags in the present version but are easily identified in the differential view of the artifact. The expectation is that allergy specialists tend to provide more detailed information applying these extended reaction details, whereas the common MD will document rather the must support attributes.

For the Condition resource the must support flags have been set as in Condition IPS.

Value Sets

The value sets for coding of allergies, intolerances and hypersensities and related conditions are based on the historically most common values documented in the swiss realm and stated as a defined list of findings, as well as the correspondent substances in the value set for reaction.substance, reviewed by the Swiss Society for Allergology and Immunology SGAI-SSAI.

Whereas this is explicitly desired by the professional representatives it is different than stated in IPS for example, where the binding is based on expanded value sets, but which has had very little real world feedback until to date. Experience and feedback is welcome therefore in this respect.

The actual value set AllergyIntolerance.code doesn’t yet include codes which exist only as post coordinated SNOMED CT expressions. They will be suggested to SNOMED CT by eHealth Suisse and added to the ci-build as soon as available as precoodinated SNOMEC CT codes and added to a future publication of this IG.

This artefact includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyright of the International Health Terminology Standards Development Organisation (IHTSDO). Implementers of these artefacts must have the appropriate SNOMED CT Affiliate license - for more information contact Swiss NRC, and

Safety Considerations

This implementation guide defines data elements, resources, formats, and methods for exchanging healthcare data between different participants in the healthcare process. As such, clinical safety is a key concern. Additional guidance regarding safety for the specification’s many and various implementations is available at:

Although the present specification does gives users the opportunity to observe data protection and data security regulations, its use does not guarantee compliance with these regulations. Effective compliance must be ensured by appropriate measures during implementation projects and in daily operations. The corresponding implementation measures are explained in the standard. In addition, the present specification can only influence compliance with the security regulations in the technical area of standardisation. It cannot influence organisational and contractual matters.

IP Statements

This document is licensed under Creative Commons “No Rights Reserved” (CC0).

HL7®, HEALTH LEVEL SEVEN®, FHIR® and the FHIR ® are trademarks owned by Health Level Seven International, registered with the United States Patent and Trademark Office.

This implementation guide contains and references intellectual property owned by third parties (“Third Party IP”). Acceptance of these License Terms does not grant any rights with respect to Third Party IP. The licensee alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize Third Party IP in connection with the specification or otherwise.

This publication includes IP covered under the following statements.

Cross Version Analysis

This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 ( and R4B ( are available.

Dependency Table

Package hl7.fhir.uv.extensions.r4#1.0.0

This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)

Package ihe.formatcode.fhir#1.1.0

Implementation Guide for IHE defined FormatCode vocabulary. (built Thu, Feb 24, 2022 16:55-0600-06:00)


Implementation guide for the meta data specified in the framework of Annex 3 and 9 of the FDHA Ordinance on the electronic patient record in Switzerland (built Tue, Dec 19, 2023 12:36+0100+01:00)


FHIR implementation guide CH Core (built Thu, Dec 28, 2023 08:42+0100+01:00)

Package hl7.fhir.uv.ips#1.0.0

International Patient Summary (IPS) FHIR Implementation Guide (built Tue, May 19, 2020 18:36+0000+00:00)

Globals Table

There are no Global profiles defined