CH EPREG (R4), published by HL7 Switzerland. This guide is not an authorized publication; it is the continuous build for version 1.0.0-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-epreg/ and changes regularly. See the Directory of published versions
Home
Official URL: http://fhir.ch/ig/ch-epreg/ImplementationGuide/ch.fhir.ig.ch-epreg
The pregnancy passport contains all the important medical information needed during pregnancy, at birth and for six weeks afterwards to ensure comprehensive care. This information is entered in the pregnancy passport by the treating healthcare providers, such as gynecologists, midwives and general practitioners, as well as institutions such as clinics, birthing centres, practices or midwife organizations.
The CH EPREG implementation guide describes the FHIR representation of the electronic pregnancy passport in Switzerland. It is dependent on CH Core and CH Term, which describe the Swiss-specific context, particularly in relation to the Swiss Electronic Patient Record (EPR).
This implementation guide is based on the concept for the exchange format of the electronic pregnancy passport (de, fr).
This implementation guide is under STU ballot by HL7 Switzerland until September 30th, 2025 midnight.
Please add your feedback via the ‘Propose a change’-link in the footer on the page where you have comments.
Changelog with significant changes, open and closed issues.
Please note that not all data elements from the concept have been mapped in this first version of the implementation guide. However, all elements and sections described in the guide (document structure / use cases, etc.) have already been mapped, enabling an initial use of the pregnancy passport. You can find the current status under Mapping Concept Data Elements.
Download: You can download this implementation guide in the npm package format from here.
MustSupport
In the concept for the electronic pregnancy passport, the data elements are described in terms of cardinality and conformity, which are then applied in the CH EPREG profiles (as long as it conforms to FHIR and the CH Core requirements). This table shows how the different levels of conformity are reflected in the FHIR profiles:
Concept (conformity)
FHIR profile (minimum cardinality and flag)
Mandatory: This is a required field. It must contain a valid value.
1..
Required: The field should always contain a valid value if possible.
0.. MS (mustSupport=true)
Optional: The field may contain a valid value.
0..
For CH EPREG the meaning of mustSupport follows also the IHE use of R2 (Required if known) as defined in ITI TF-2: Appendix Z: 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.
IP Statements
This document is licensed under Creative Commons "No Rights Reserved" (CC0).
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 implementation guide contains and references intellectual property owned by third parties ("Third Party IP"). Acceptance of these License Terms does not grant any rights with respect to Third Party IP. The licensee alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize Third Party IP in connection with the specification or otherwise.
This publication includes IP covered under the following statements.
The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
This artefact includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyright of the International Health Terminology Standards Development Organisation (IHTSDO). Implementers of these artefacts must have the appropriate SNOMED CT Affiliate license - for more information contact http://www.snomed.org/snomed-ct/getsnomed-ct or info@snomed.org.
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.
This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Mon, Feb 10, 2025 21:45+1100+11:00)
Package hl7.fhir.uv.extensions.r4#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 ihe.formatcode.fhir#1.3.0
Implementation Guide for IHE defined FormatCode vocabulary. (built Fri, May 17, 2024 12:02-0500-05:00)
Package ch.fhir.ig.ch-term#current
Implementation Guide for Swiss Terminology (built Thu, May 22, 2025 05:51+0000+00:00)
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:36+0000+00:00)
Package ch.fhir.ig.ch-orf#current
Order & Referral by Form - Implementation Guide (CH ORF) (built Thu, May 22, 2025 09:52+0000+00: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 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.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.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.1
This guide describes how the Laboratory Report can be represented in the European REALM. (built Tue, Mar 25, 2025 12:00+0100+01:00)
Package ch.fhir.ig.ch-lab-report#2.0.0-ci-build
FHIR® Implementation Guide for Laboratory Reports in Switzerland (built Thu, May 22, 2025 14:31+0000+00:00)
® are trademarks owned by Health Level Seven International, registered with the United States Patent and Trademark Office.
