CH ELM (R4)
1.2.0 - release Switzerland flag

This page is part of the Observations of notifiable communicable infectious diseases (v1.2.0: Release) 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

Changelog

All significant changes to this FHIR implementation guide will be documented on this page.

1.2.0 - 2024/03/28

  • #32: adding ValueSets/ConceptMaps for Interpretation Code
  • #68: Add slice for DocumentReference.contained for improving validation output
  • #71: Fix SARS-CoV-2 Strict validation
  • #72: Einbau ValueSet Specimen.type
  • #73: Change status of IG from Draft to Release for version 1.2.0
  • #75: PractitionerRole: Orderer -> update constraints
  • #78: Removed Observation code for example Bundle-6Doc-Influenza (http://loinc.org#100343-3)

1.1.0 2024/01/31

Added

  • #56: add a search box to the ig #56

Changed / Updated

  • #49: Update description of CS/VS CH ELM FOPH Patient Name Representation
  • #52: CH ELM Organization: BUR and UID as identifiers 0..1, no ZSR anymore
  • #6: Fix ig dependencies to published versions
  • #60: Removal of rule that prevents a specimen code to be sent
  • #61: postalCode / city required for Orderer (Practitioner and/or Organisation)

Fixed

  • #45: Fix minimum cardinality for Practitioner in Bundle
  • #54: API fixed to Release FHIR R4
  • #55: Fixed link to specimen in broker example 1bDoc - Neisseria Gonorrhoeae
  • #58: Don’t indicated meta.profiles in examples
  • #57: Patient address.line also specified, not only extension

1.0.0-release

Added

  • New examples: Carbapenemase-producing Enterobacteriaceae (CPE), Campylobacter spp., Treponema pallidum, Influenza, SARS-CoV-2
  • In order to have the possibility to react quickly to any changes in the reporting needs, a two-stage validation strength has been introduced:
    • Profile CH ELM Document: Laboratory Report (strict): The leading code element has a required binding to the ValueSet CH ELM Results Laboratory Observation and initials are checked depending on the leading code
      • Usage: For all examples in this published version of the implementation guide, use for validation of an implementation according to the current implementation guide
    • Profile CH ELM Document: Laboratory Report: The leading code element has an extensible binding to the ValueSet CH ELM Results Laboratory Observation
      • Potential usage: A new leading code to be reported is introduced, which could not yet get updated in the implementation guide
  • Include a check (warning) if Observation.code and ServiceRequest.code are equal (so far no other requirements)
  • #7: Add ConceptMap with the requirements to the patient name representation
  • #29: Validation of Bundle for DocumentReference
  • #39: Integration of FOPH business rules as CodeSystem
  • #43: Add limits to string lengths

Changed / Updated

  • #15: API update for search capabilities
  • #14: Remove turtle definitions
  • #11: Change level of flag MustSupport for Patient.country (Patient.country MS, Patient.country.extension:countrycode 1..)
  • Adjustment to the changed names of the parent profiles of CH LAB-Order
  • #19: Require DiagnosticReport.identifier (equal to Composition.identifier)
  • #13: Update Fig. 6: Resource Overview with cardinalities
  • #21: Usage of the IDN instead of the OASI for Patient.identifier Liechtenstein.
  • Add a computable way for the concept of leading code and in some cases necessary addition of additional codes to the leading code, see Guidance - Laboratory Result
    • #23: Include rules to check if the described mechanism is applied correctly
    • #25: Renaming of the specimen-specific ValueSet ‘CH ELM Lab Specimen Types: Chlamydia Trachomatis’ to ValueSet ‘CH ELM Results Geni Spec’
    • #26/#8: Remove ValueSet ‘CH ELM Lab Specimen Types’; now handled via the newly introduced mechanism
    • #8: Change the fixed value for Specimen.type.text to a more general version: ‘Material declared by LOINC system axis’ -> ‘Material declared by Observation.code or non-mandatory’
  • #35: Address.line now requires the explicit specification of streetName, houseNumber and postOfficeBoxNumber (via extensions)
  • #34: Restriction of maximum cardinalities

Fixed

  • #9: Set minimum cardinality of Patient.gender to 1 (according to the logical model)