This page is part of the Observations of notifiable communicable infectious diseases (v1.0.0-trialuse: STU 1 Draft) based on FHIR 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

Home

Official URL: http://fhir.ch/ig/ch-elm/ImplementationGuide/ch.fhir.ig.ch-elm				Version: 1.0.0-trialuse
Draft as of 2023-09-13				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 (DE) describe the different scenarios with respective examples for specific organisms.

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 (DE) 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 the guidance.

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.

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.

• CC0-1.0
  Show Usage
  • eCH-011 Types: ChElmPatient
• Copyright HL7. Licensed under creative commons public domain
  Show Usage
  • identifierType: ChElmPatient
• ISO Maintains the copyright on the country codes, and controls it's use carefully. For futher 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: Bundle/1Doc-NeisseriaGonorrhoeae, Bundle/1bDoc-NeisseriaGonorrhoeae... Show 37 more, Bundle/2Doc-ChlamydiaTrachomatis, CH_ELM, CH_ELM_CapabilityStatement_DocumentRecipient, ChElmCodeableConcept, ChElmCoding, ChElmComposition, ChElmDiagnosticReport, ChElmDocument, ChElmExtDepartment, ChElmLabSpecimenTypes, ChElmLabSpecimenTypesChlamydiaTrachomatis, ChElmLabStudyTypes, ChElmLaboratoryReport, ChElmObservationInterpretationCodes, ChElmObservationResultsLaboratory, ChElmOrganizationAuthor, ChElmOrganizationLab, ChElmOrganizationOrderer, ChElmPatient, ChElmPractitionerOrderer, ChElmPractitionerRoleOrderer, ChElmResultsCodedValuesLaboratory, ChElmResultsLaboratoryObservation, ChElmServiceRequestLaboratoryOrder, ChElmSpecimen, ChElmStatus, ChExtElmStatus, DocumentReference/1-DocumentReference, OASINumberLI, OasiLiIdentifier, Patient/1Pat-DM, Patient/Pat-E5, Patient/Pat-ET, Patient/Pat-ErnstKarlTanner, Patient/Pat-LillyLiechtenstein, PublishDocumentReference and PublishDocumentReferenceResponse
• 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/1Doc-NeisseriaGonorrhoeae, Bundle/1bDoc-NeisseriaGonorrhoeae... Show 15 more, Bundle/2Doc-ChlamydiaTrachomatis, ChElmComposition, ChElmDiagnosticReport, ChElmLabStudyTypes, ChElmObservationResultsLaboratory, ChElmResultsLaboratoryObservation, ChElmServiceRequestLaboratoryOrder, Composition/1Comp-NeisseriaGonorrhoeae, Composition/1bComp-NeisseriaGonorrhoeae, DiagnosticReport/1DR-NeisseriaGonorrhoeae, DiagnosticReport/1bDR-NeisseriaGonorrhoeae, DocumentReference/1-DocumentReference, Observation/1Obs-NeisseriaGonorrhoeae, Observation/1bObs-NeisseriaGonorrhoeae and ServiceRequest/1SR-Order
• This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed or info@snomed.org.
  Show Usage
  • SNOMED Clinical Terms® (SNOMED CT®): Bundle/1Doc-NeisseriaGonorrhoeae, Bundle/1bDoc-NeisseriaGonorrhoeae... Show 14 more, Bundle/2Doc-ChlamydiaTrachomatis, ChElmComposition, ChElmDiagnosticReport, ChElmLabSpecimenTypes, ChElmLabSpecimenTypesChlamydiaTrachomatis, ChElmObservationResultsLaboratory, ChElmResultsCodedValuesLaboratory, ChElmServiceRequestLaboratoryOrder, ChElmSpecimen, Composition/1Comp-NeisseriaGonorrhoeae, Composition/1bComp-NeisseriaGonorrhoeae, DocumentReference/1-DocumentReference, Observation/1Obs-NeisseriaGonorrhoeae and Observation/1bObs-NeisseriaGonorrhoeae

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

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)

Package ch.fhir.ig.ch-epr-term#2.0.9 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, Jun 27, 2023 18:05+0200+02:00)

Package ch.fhir.ig.ch-core#4.0.0 FHIR implementation guide CH Core (built Tue, Sep 5, 2023 13:15+0000+00:00)

Package hl7.fhir.uv.ips#current International Patient Summary (IPS) FHIR Implementation Guide (built Wed, Dec 7, 2022 16:30+0000+00:00)

Package hl7.fhir.eu.laboratory#current This guide describes how the Laboratory Report can be represented in the European REALM. (built Mon, Sep 11, 2023 18:04+0000+00:00)

Package ch.fhir.ig.ch-core#4.0.0-ballot FHIR implementation guide CH Core (built Tue, Jun 27, 2023 23:13+0200+02:00)

Package hl7.fhir.r4.examples#4.0.1 Example resources in the R4 version of the FHIR standard

Package hl7.fhir.uv.sdc#3.0.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR. This includes two components: * Support more sophisticated questionnaire/form use-cases such as those needed for research, oncology, pathology and other clinical domains. *Support pre-population and auto-population of EHR data into forms/questionnaires for uses outside direct clinical care (patient safety, adverse event reporting, public health reporting, etc.). (built Tue, Mar 8, 2022 18:32+0000+00:00)

Package ch.fhir.ig.ch-orf#2.0.0-ballot Order & Referral by Form - Implementation Guide (CH ORF) (built Thu, Jun 29, 2023 21:19+0200+02:00)

Package hl7.fhir.uv.order-catalog#0.1.0 An Order Catalog is an administered homogeneous collection of items such as medication products, laboratory tests, procedures, medical devices or knowledge artifacts such as order sets, which support the ordering process, or more generally healthcare processes. (built Sun, Aug 9, 2020 15:18+0000+00:00)

Package ch.fhir.ig.ch-lab-order#2.0.0-ballot Implementation guide CH LAB-Order (R4) (built Thu, Jun 29, 2023 22:56+0200+02:00)

Package ch.fhir.ig.ch-lab-report#0.1.0 FHIR® Implementation Guide for Laboratory Reports in Switzerland (built Tue, Sep 5, 2023 15:25+0000+00:00)

Globals Table

There are no Global profiles defined