CH ELM (R4)
1.8.0-cibuild - ci-build Switzerland flag

CH ELM (R4), published by Federal Office of Public Health FOPH. This guide is not an authorized publication; it is the continuous build for version 1.8.0-cibuild built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/ahdis/ch-elm/ and changes regularly. See the Directory of published versions

Home

Official URL: http://fhir.ch/ig/ch-elm/ImplementationGuide/ch.fhir.ig.ch-elm Version: 1.8.0-cibuild
Active as of 2024-12-03 Computable Name: CH_ELM

Copyright/Legal: CC0-1.0

Introduction

CH ELM is a project of the Swiss Federal Office of Public Health (FOPH), Communicable Diseases Division, to enable laboratories to send their observations of notifiable communicable infectious diseases to the FOPH electronically. A report is created as a specialized Clinical Document based on the HL7® FHIR® standard. This FHIR document is sent to the FOPH by a FHIR RESTful web API endpoint. CH ELM derives from the Swiss implementation guides and the European laboratory project (see graphical overview).

​The expected content of the FHIR document, based on the ordinance of the Federal Office of Public Health (DE, FR, IT), is defined in the logical model. A mapping shows how to access the data from the FHIR document. In addition, further documentation for specific topics can be found on the guidance page and the use cases describe the different scenarios with respective examples for specific organisms.

The specification herewith documented is work in progress. No liability can be inferred from the use or misuse of this specification, or its consequences.

Changelog with significant changes, open and closed issues.

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

Implementation Support for Laboratories

This guide supports you as a laboratory in the following way:

  • Use cases describe the different scenarios with respective example reports for specific organisms, e.g. for Neisseria gonorrhoeae in xml or json, you choose if you want to provide the FHIR laboratory report in xml or json format.
  • What needs to be defined in the laboratory report is defined in FHIR document, profiles define the constraints on FHIR resources which need to be included in the report, see the overview here.
  • ​The data elements defined by the ordinance of the Federal Office of Public Health (FOPH) for the report are defined in the logical model and are then mapped to the FHIR document structure.
  • Value sets for the terminology are provided as FHIR resources which you can directly import from the npm package.
  • The laboratory report is sent to the FOPH by a FHIR RESTful web API endpoint.
  • Further documentation for specific topics can be found on guidance and/or by contacting the FOPH directly.

FHIR R4 has a huge implementation community and offers various libraries to support the implementation of FHIR based solutions, for creating the FHIR document or providing a client for doing the FHIR API calls. For java we recommend hapi-fhir, for .NET firely-net-sdk, but there are also multiple other options. If you have questions about general FHIR questions do not hesitate to ask in chat.fhir.org.

To check if your report is valid to the requirements of this implementation guide you can check it with the FHIR Validator providing this package as a parameter and specifying the profile http://fhir.ch/ig/ch-elm/StructureDefinition/ch-elm-document-strict.

Since the FHIR API is standardized you can test your client also against a public FHIR test server like hapi.

If you have general feedback this implementation guide you find at the bottom a "Propose a change" link where you can raise an issue.

Must Support

For the CH ELM exchange format, the mustSupport flag set to true has the following meaning:
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.

IP Statements

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 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 (ch.fhir.ig.ch-elm.r4) and R4B (ch.fhir.ig.ch-elm.r4b) are available.

Dependencies

Dependency Overview

This overview illustrates the relevant dependencies of CH ELM to the Swiss implementation guides and the European laboratory project.

Fig. 1: Dependency Overview

Fig. 1: Dependency Overview

Dependency Table

Package hl7.fhir.uv.extensions.r5#5.1.0

This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Apr 27, 2024 18:39+1000+10:00)

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 hl7.fhir.uv.ips#1.1.0

International Patient Summary (IPS) FHIR Implementation Guide (built Tue, Nov 22, 2022 03:24+0000+00:00)

Package hl7.fhir.eu.extensions#0.1.0

This guide lists the extensions speciifed for the European REALM. (built Tue, Feb 20, 2024 08:56+0100+01:00)

Package hl7.fhir.eu.laboratory#0.1.0

This guide describes how the Laboratory Report can be represented in the European REALM. (built Mon, Feb 26, 2024 08:09+0100+01:00)

Package ch.fhir.ig.ch-core#5.0.0

FHIR implementation guide CH Core (built Tue, Dec 17, 2024 19:54+0000+00:00)

Package ch.fhir.ig.ch-lab-report#1.0.0

FHIR® Implementation Guide for Laboratory Reports in Switzerland (built Wed, Dec 18, 2024 08:52+0000+00:00)

Globals Table

There are no Global profiles defined