This page is part of the CH-AllergyIntolerance (R4) (v3.0.0: STU 3) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Changelog
All significant changes to this FHIR implementation guide will be documented on this page.
STU 3 Sequence - v3.0.0 (2024-12-17)
Open Issues
During the ballot, the following comments came in, which will be taken into account in the further development of CH AllergyIntolerance:
- #106: Examples with deprecated SNOMED CT codes
See also open issues on GitHub.
Added
- #104: Add guidance for adverse reaction & manifestation
Changed / Updated
- #109: Add open issues section to changelog (STU 3 Ballot - v3.0.0-ballot)
- #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)
Fixed
- #103: Typo corrected in use case (english)
- #105: Typo fixed in use case 2
- #117: Replace deprecated discriminator (
pattern
-> value
) resp. removal of the redundant slice definition (inherited from parent profile)
Issues resolved without amendment (in IG)
- #108: Versioned links for VS/CS to CH Term
STU 3 Sequence - v3.0.0-ballot (2024-05-17)
Open Issues
During the ballot, the following comments came in, which will be taken into account in the further development of CH AllergyIntolerance:
- #86: Split value set CHAllergyIntoleranceValueSet into different categories
- #87: Link between the condition and the allergyintolerance
- #89: Compensate for redundancy-related differences
See also open issues on GitHub.
Changed / Updated
- #91: Move terminology (CS/VS) to CH Term
- #92: Update title numbering (incl. fixing some typos)
- #93: Update to current version of IPS IG (v1.0.0 -> v1.1.0)
- #95: Use CH Core base profiles as parent (Condition, AllergyIntolerance)
- #99: In the profile CHAllergyIntoleranceCompositionEPR Typo at the title
STU 2 Sequence - v2.0.1 (2023-12-28)
- #270: Technical correction for invalid package
Open Issues
During the ballot, the following comments came in, which will be taken into account in the further development of CH AllergyIntolerance:
- #86: Split value set CHAllergyIntoleranceValueSet into different categories
- #87: Link between the condition and the allergyintolerance
- #89: Compensate for redundancy-related differences
See also open issues on GitHub.
Fixed
- Issue 78 - Typo in codes adjusted in CHAllergyIntoleranceReactionManifestationValueSet
- Issue 79 - Typo in codes adjusted in CHAllergyIntoleranceReactionSubstanceValueSet
- Issue 80 - Typo in codes adjusted in CHAllergyIntoleranceConditionValueSet
- Issue 81 - Typo in codes adjusted in CHAllergyIntoleranceValueSet
- Issue 82 - Typo in codes adjusted in CHAllergyIntoleranceReactionSubstanceValueSet
- Issue 83 - Typo in codes adjusted in CHAllergyIntoleranceConditionValueSet
- Issue 88 - Typo in codes adjusted in Use Case 8
- Issue 85 - For Best practice for patternCodeableConcept, fixed value were removed from the display value.
Changed / Updated
- Issue 84 - Added IG Fragments to the home page below
STU 1 Sequence - v1.0.0 (2022-02-11)
Added
Navigation within the Implementation Guide for a better usability:
- Issue 22 - Besseren Zugang zu den einzelnen Seiten des IG ermöglichen
- Issue 20 - Home
- Issue 19 - Home: Download link for npm package
- Issue 12 - Home - Add Links to referred specifications, copyright
- Issue 11 - Extend Menu and Description for Implementation Guide
Clarification about the use of and implementation of AllergyIntolerance IG:
- Issue 26 - Artifacts Summary: Beschreibung der beiden Profile "CH AllergyIntolerance" und "CH AllergyIntolerance Condition" ist weitgehend identisch
- Issue 31 - Provide Use Cases – CH AllergyIntolerance
- Issue 23 - CH AllergyIntolerance Condition: Beispiel fehlt
- Issue 17 - CH AllergyIntolerance Condition
- Issue 14 - Examples are missing
- Issue 13 - Home - Goal of Implementation Guide?
Changed / Updated
Removed own extensions, replaced through existing ones:
References to CH Core profiles:
Content and integration of value sets:
- Issue 37 - Allergy or non-allergic hypersensivity to vancomycin
- Issue 35 - CH AllergyIntolerance Value Set
- Issue 32 - Put Allergy value set to extensible
- Issue 28 - make value set extensible? CH AllergyIntolerance Value Set
- Issue 27 - CH AllergyIntolerance: Binding code zu SNOMED CT
- CHAllergyIntoleranceValueSet
- CHAllergyIntoleranceReactionSubstanceValueSet
- Issue 29 - manifestation value set: define extensional and extensible value set
- CHAllergyIntoleranceReactionManifestationValueSet
Use of must support:
- Issue 30 - AllergyIntolerance.category must be supported
- Issue 24 - CH AllergyIntolerance: zu viele Elemente als "Must Support" gekennzeichnet
- Issue 25 - CH AllergyIntolerance Condition: zu viele Elemente als "Must Support" gekennzeichnet
Fixed
Refuted
- Issue 38 - short name for IG?
- Issue 36 - Need for arborescence in the valueset?
- Issue 34 - CH AllergyIntolerance Composition Profile
- Issue 33 - type indication not useful – allergyintolerance-type-supplement