Unattributed Code Systems

Copyright Fragment

This fragment is available on index.html

Copyright and Registered Trademark Uses

• IG © 2021+ HL7 Switzerland. Package ch.fhir.ig.ch-allergyintolerance#3.0.2-ci-build based on FHIR 4.0.1. Generated 2025-12-16 Links: Table of Contents | QA Report | Propose a change ( src )
• CH AllergyIntolerance (R4), published by HL7 Switzerland. This guide is not an authorized publication; it is the continuous build for version 3.0.2-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7ch/ch-allergyintolerance/ and changes regularly. See the Directory of published versions ( src )
• HL7®, HEALTH LEVEL SEVEN®, FHIR® and the FHIR [image]® are trademarks owned by Health Level Seven International, registered with the United States Patent and Trademark Office. ( src )
• This material contains content from LOINC. LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc. Show Usage * LOINC: Bundle/ch-allergyintolerance-document-example, CHAllergyIntoleranceCompositionEPR, Composition/AllergyIntoleranceComposition and Composition/ch-allergyintolerance-composition-example ( src )
• This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html Show Usage * AllergyIntolerance Clinical Status Codes: AllergyIntolerance/AllergyToCatDander, AllergyIntolerance/CH-AllergyIntolerance-IPAG-Recommendation-Table-1... Show 10 more , AllergyIntolerance/CH-AllergyIntolerance-MultipleManifestationEntries, AllergyIntolerance/CH-AllergyIntolerance-MultipleReactionEntries, AllergyIntolerance/CH-AllergyIntolerance-Usecase-2, AllergyIntolerance/CH-AllergyIntolerance-Usecase-3, AllergyIntolerance/CH-AllergyIntolerance-Usecase-5, AllergyIntolerance/CH-AllergyIntolerance-Usecase-6, AllergyIntolerance/CH-AllergyIntolerance-Usecase-7, AllergyIntolerance/CH-AllergyIntolerance-Usecase-8, AllergyIntolerance/ExAllergy and Bundle/ch-allergyintolerance-document-example * AllergyIntolerance Verification Status: AllergyIntolerance/AllergyToCatDander, AllergyIntolerance/CH-AllergyIntolerance-IPAG-Recommendation-Table-1... Show 9 more , AllergyIntolerance/CH-AllergyIntolerance-MultipleManifestationEntries, AllergyIntolerance/CH-AllergyIntolerance-MultipleReactionEntries, AllergyIntolerance/CH-AllergyIntolerance-Usecase-2, AllergyIntolerance/CH-AllergyIntolerance-Usecase-3, AllergyIntolerance/CH-AllergyIntolerance-Usecase-5, AllergyIntolerance/CH-AllergyIntolerance-Usecase-6, AllergyIntolerance/CH-AllergyIntolerance-Usecase-7, AllergyIntolerance/CH-AllergyIntolerance-Usecase-8 and Bundle/ch-allergyintolerance-document-example * Condition Category Codes: Condition/CH-AllergyIntolerance-Condition-Usecase-3, Condition/CH-AllergyIntolerance-Condition-Usecase-7, Condition/CH-AllergyIntolerance-Condition-Visit1-Usecase-1 and Condition/CH-AllergyIntolerance-Condition-Visit2-Usecase-1 * Condition Clinical Status Codes: Condition/CH-AllergyIntolerance-Condition-Usecase-3, Condition/CH-AllergyIntolerance-Condition-Usecase-7, Condition/CH-AllergyIntolerance-Condition-Visit1-Usecase-1 and Condition/CH-AllergyIntolerance-Condition-Visit2-Usecase-1 * ConditionVerificationStatus: Condition/CH-AllergyIntolerance-Condition-Usecase-3, Condition/CH-AllergyIntolerance-Condition-Usecase-7, Condition/CH-AllergyIntolerance-Condition-Visit1-Usecase-1 and Condition/CH-AllergyIntolerance-Condition-Visit2-Usecase-1 * AllergyIntoleranceCertainty: AllergyIntolerance/AllergyToCatDander, AllergyIntolerance/CH-AllergyIntolerance-IPAG-Recommendation-Table-1... Show 4 more , AllergyIntolerance/CH-AllergyIntolerance-Usecase-3, AllergyIntolerance/CH-AllergyIntolerance-Usecase-5, AllergyIntolerance/CH-AllergyIntolerance-Usecase-7 and Bundle/ch-allergyintolerance-document-example * identifierType: Bundle/ch-allergyintolerance-document-example and Patient/MonikaWegmueller * MaritalStatus: Patient/ElisabethBroennimannByBFH ( src )

External References

Type	Reference	Content
web	www.gs1.org	identifier : GLN /7601000234438
web	www.gs1.org	identifier : GLN /7601000121219
web	www.gs1.org	identifier : GLN /7601000050717
web	www.hl7.ch
web	github.com	CH AllergyIntolerance (R4), published by HL7 Switzerland. This guide is not an authorized publication; it is the continuous build for version 3.0.2-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7ch/ch-allergyintolerance/ and changes regularly. See the Directory of published versions
web	www.hl7.ch	IG © 2021+ HL7 Switzerland . Package ch.fhir.ig.ch-allergyintolerance#3.0.2-ci-build based on FHIR 4.0.1 . Generated 2025-12-16 Links: Table of Contents | QA Report | Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	wiki.ihe.net	This is a metadata field from XDS/MHD .
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	en.wikipedia.org	Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. HATEOAS ).
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	github.com	Remove extension 'Information Recipient' (see CH Core #400 )
web	github.com	Remove slice name 'legalAuthenticator' (see CH Core #379 )
web	github.com	Use introduced profile 'CH Core RelatedPerson' (see CH Core #344 )
web	github.com	#120 : Removed unused dependency (inserted by the other dependencies)
web	github.com	#119 : Add expansion-parameter for the usage of SNOMED CT Swiss Extension
web	github.com	#106 : Examples with deprecated SNOMED CT codes
web	github.com	See also open issues on GitHub .
web	github.com	#104 : Add guidance for adverse reaction & manifestation
web	github.com	#109 : Add open issues section to changelog (STU 3 Ballot - v3.0.0-ballot)
web	github.com	#100 & #170 : Use CH IPS as base instead of directly HL7 IPS-UV -> changes due to this update: Update Home (Introduction, Must Support) Usage of CH IPS AllergyIntolerance & CH IPS Condition as parent profiles Remove MS flags in Condition profile Remove Allergy Abatement Extension and use base extension (see HL7 IPS-UV changelog )
web	github.com	#100 & #170 : Use CH IPS as base instead of directly HL7 IPS-UV -> changes due to this update: Update Home (Introduction, Must Support) Usage of CH IPS AllergyIntolerance & CH IPS Condition as parent profiles Remove MS flags in Condition profile Remove Allergy Abatement Extension and use base extension (see HL7 IPS-UV changelog )
web	github.com	#103 : Typo corrected in use case (english)
web	github.com	#105 : Typo fixed in use case 2
web	github.com	#117 : Replace deprecated discriminator ( pattern -> value ) resp. removal of the redundant slice definition (inherited from parent profile)
web	github.com	#108 : Versioned links for VS/CS to CH Term
web	github.com	#86 : Split value set CHAllergyIntoleranceValueSet into different categories
web	github.com	#87 : Link between the condition and the allergyintolerance
web	github.com	#89 : Compensate for redundancy-related differences
web	github.com	#91 : Move terminology (CS/VS) to CH Term
web	github.com	#92 : Update title numbering (incl. fixing some typos)
web	github.com	#93 : Update to current version of IPS IG (v1.0.0 -> v1.1.0)
web	github.com	#95 : Use CH Core base profiles as parent (Condition, AllergyIntolerance)
web	github.com	#99 : In the profile CHAllergyIntoleranceCompositionEPR Typo at the title
web	github.com	#270 : Technical correction for invalid package
web	github.com	Issue 78 - Typo in codes adjusted in CHAllergyIntoleranceReactionManifestationValueSet
web	github.com	Issue 79 - Typo in codes adjusted in CHAllergyIntoleranceReactionSubstanceValueSet
web	github.com	Issue 80 - Typo in codes adjusted in CHAllergyIntoleranceConditionValueSet
web	github.com	Issue 81 - Typo in codes adjusted in CHAllergyIntoleranceValueSet
web	github.com	Issue 82 - Typo in codes adjusted in CHAllergyIntoleranceReactionSubstanceValueSet
web	github.com	Issue 83 - Typo in codes adjusted in CHAllergyIntoleranceConditionValueSet
web	github.com	Issue 88 - Typo in codes adjusted in Use Case 8
web	github.com	Issue 85 - For Best practice for patternCodeableConcept, fixed value were removed from the display value.
web	github.com	Issue 84 - Added IG Fragments to the home page below
web	github.com	Issue 22 - Besseren Zugang zu den einzelnen Seiten des IG ermöglichen
web	github.com	Issue 20 - Home
web	github.com	Issue 19 - Home: Download link for npm package
web	github.com	Issue 12 - Home - Add Links to referred specifications, copyright
web	github.com	Issue 11 - Extend Menu and Description for Implementation Guide Home
web	github.com	Issue 26 - Artifacts Summary: Beschreibung der beiden Profile "CH AllergyIntolerance" und "CH AllergyIntolerance Condition" ist weitgehend identisch Artifacts
web	github.com	Issue 31 - Provide Use Cases – CH AllergyIntolerance
web	github.com	Issue 23 - CH AllergyIntolerance Condition: Beispiel fehlt
web	github.com	Issue 17 - CH AllergyIntolerance Condition
web	github.com	Issue 14 - Examples are missing Use Cases Example AllergyIntolerance Example composition Example condition Example document
web	github.com	Issue 13 - Home - Goal of Implementation Guide? Home
web	github.com	Issue 16 - Extensions CH AllergyIntolerance
web	github.com	Issue 15 - Condition abatement date CH AllergyIntolerance Condition
web	github.com	Issue 21 - CH AllergyIntolerance CH AllergyIntolerance
web	github.com	Issue 37 - Allergy or non-allergic hypersensivity to vancomycin
web	github.com	Issue 35 - CH AllergyIntolerance Value Set
web	github.com	Issue 32 - Put Allergy value set to extensible
web	github.com	Issue 28 - make value set extensible? CH AllergyIntolerance Value Set
web	github.com	Issue 27 - CH AllergyIntolerance: Binding code zu SNOMED CT CHAllergyIntoleranceValueSet CHAllergyIntoleranceReactionSubstanceValueSet
web	github.com	Issue 29 - manifestation value set: define extensional and extensible value set CHAllergyIntoleranceReactionManifestationValueSet
web	github.com	Issue 30 - AllergyIntolerance.category must be supported
web	github.com	Issue 24 - CH AllergyIntolerance: zu viele Elemente als "Must Support" gekennzeichnet CH AllergyIntolerance
web	github.com	Issue 25 - CH AllergyIntolerance Condition: zu viele Elemente als "Must Support" gekennzeichnet CH AllergyIntolerance Condition
web	github.com	Issue 18 - Just typos
web	github.com	Issue 38 - short name for IG?
web	github.com	Issue 36 - Need for arborescence in the valueset?
web	github.com	Issue 34 - CH AllergyIntolerance Composition Profile
web	github.com	Issue 33 - type indication not useful – allergyintolerance-type-supplement
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	www.e-health-suisse.ch	Swiss implementation guide (IG) for allergies and intolerances based on the recommendations of the interprofessional working group EPR (IPAG) and the implementation guide CH IPS , which is closely aligned with the HL7 IPS-UV specification . The "Implementation Guide for Use of SNOMED CT in Documentation of Allergy, Non-allergic Hypersensitivity and Intolerance", which was still in development at the time of the initial publication of this IG, has also been taken into account.
web	fhir.ch	Swiss implementation guide (IG) for allergies and intolerances based on the recommendations of the interprofessional working group EPR (IPAG) and the implementation guide CH IPS , which is closely aligned with the HL7 IPS-UV specification . The "Implementation Guide for Use of SNOMED CT in Documentation of Allergy, Non-allergic Hypersensitivity and Intolerance", which was still in development at the time of the initial publication of this IG, has also been taken into account.
web	confluence.ihtsdotools.org	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.
web	github.com	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."
web	fhir.ch	CH AllergyIntolerance and CH AllergyIntolerance Condition are based on the corresponding profiles of CH IPS . CH IPS itself explicitly does not set any Must Support flags, but rather indicates that the same rules/elements apply as in HL7 IPS-UV (see here ). This therefore also applies to this IG CH AllergyIntolerance. This mechanism also prevents discrepancies/contradictions between the individual specifications. However, for the AllergyIntolerance resource, Must Support flags have been explicitly set here for all those fields that are Must Support in HL7 IPS-UV and are also part of the IPAG recommendations (see also here ). In addition, the fields AllergyIntolerance.reaction.substance and AllergyIntolerance.category were also flagged as Must Support because these fields play an important role in the above mentioned recommendations.
web	fhir.ch	CH AllergyIntolerance and CH AllergyIntolerance Condition are based on the corresponding profiles of CH IPS . CH IPS itself explicitly does not set any Must Support flags, but rather indicates that the same rules/elements apply as in HL7 IPS-UV (see here ). This therefore also applies to this IG CH AllergyIntolerance. This mechanism also prevents discrepancies/contradictions between the individual specifications. However, for the AllergyIntolerance resource, Must Support flags have been explicitly set here for all those fields that are Must Support in HL7 IPS-UV and are also part of the IPAG recommendations (see also here ). In addition, the fields AllergyIntolerance.reaction.substance and AllergyIntolerance.category were also flagged as Must Support because these fields play an important role in the above mentioned recommendations.
web	creativecommons.org	This document is licensed under Creative Commons "No Rights Reserved" ( CC0 ).
web	www.iso.org	ISO maintains the copyright on the country codes, and controls its use carefully. For further details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html Show Usage ISO 3166-1 Codes for the representation of names of countries and their subdivisions — Part 1: Country code : CHAllergyIntolerance , CHAllergyIntoleranceCompositionEPR , CHAllergyIntoleranceCondition and CHAllergyIntoleranceDocumentEPR
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
img	icons.duckduckgo.com
img	icons.duckduckgo.com
img	icons.duckduckgo.com
img	icons.duckduckgo.com
img	icons.duckduckgo.com
web	confluence.ihtsdotools.org	Based on the recommendations of the international expert group "Allergies/Hypersensitivity and Intolerance Clinical Reference Group" , the value sets for this exchange format were compiled according to their "Implementation Guide for Use of SNOMED CT in Documentation of Allergy, Non-allergic Hypersensitivity and Intolerance". For this purpose, 4 value sets were compiled using the following procedure: Based on the substance list of drugs available on the Swiss market with known allergy warnings using the CDS of the Swiss drug catalog "HospIndex" from HCI Solutions AG and the allergy documentation list from the HIS KISIM of Cistec AG, Snomed-CT codes were compiled for as many findings (allergy to substance X), disorders (adverse reaction due to substance X) in the case of non-allergic hypersensitivity and substances as possible. This value set was subsequently reviewed by a working group of the SGAI, the Swiss Society of Allergology and Immunology and is provided herewith.
web	fhir.ch	CH AllergyIntolerance Condition Value set for the condition, contains all codes available so far for findings (Allergy to substance X) and/or disorders (Adverse Reaction due to substance X) in case of non-allergic hypersensitivity
web	fhir.ch	CH AllergyIntolerance Reaction Substance Value set for the reaction.substances, includes all previously compiled codes for substances
web	fhir.ch	CH AllergyIntolerance Value Set for the general part in AllergyIntolerance.code, preferably includes codes for Findings (Allergy to substance X) and/or Disorders (Adverse Reaction due to substance X) in case of non-allergic hypersensitivity, and in case these are not available substitute the substances
web	fhir.ch	CH AllergyIntolerance Reaction Manifestation ValueSet for reaction.manifestation, includes an adapted shortlist of the value set Allergy Reaction (GPS) from the IPS (International Patient Summary)
web	fhir.ch	CH AllergyIntolerance Category
web	fhir.ch	CH AllergyIntolerance Clinical Status
web	fhir.ch	CH AllergyIntolerance Criticality Status
web	fhir.ch	CH AllergyIntolerance Severity Status
web	fhir.ch	CH AllergyIntolerance Type
web	fhir.ch	CH AllergyIntolerance Verification Status
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	confluence.ihtsdotools.org	The use cases are adapted from the "Implementation Guide for Use of SNOMED CT in Documentation of Allergy, Non-allergic Hypersensitivity and Intolerance" of Allergies/Hypersensitivity and Intolerance Clinical Reference Group of SNOMED CT.
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	confluence.ihtsdotools.org	Les cas d’utilisation ont été adaptés à partir de l’« Implementation Guide for Use of SNOMED CT in Documentation of Allergy, Non-allergic Hypersensitivity and Intolerance » de l’ Allergies/Hypersensitivity and Intolerance Clinical Reference Group de SNOMED CT.
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change
web	confluence.ihtsdotools.org	Die Use cases sind adaptiert vom "Implementation Guide for Use of SNOMED CT in Documentation of Allergy, Non-allergic Hypersensitivity and Intolerance" der Allergies/Hypersensitivity and Intolerance Clinical Reference Group of SNOMED CT.
web	docs.google.com	Links: Table of Contents | QA Report |  Propose a change

Internal Images

Bundle-Overview.png

Table_IPAG.png

fhir-logo-www.png

hl7-logo.png

tree-filter.png