CH Core (R4)
6.0.0-ci-build - ci-build Switzerland flag

CH Core (R4), published by HL7 Switzerland. This guide is not an authorized publication; it is the continuous build for version 6.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-core/ and changes regularly. See the Directory of published versions

Usage of Swiss Core Artifacts

The CH Core implementation guide provides the basis for a layered approach to FHIR interoperability in the Swiss context and aims to support a coherent and reusable set of FHIR artifacts across Switzerland.

Fig. 1 shows the dependencies between Swiss implementation guides. The CH Core IG is derived from CH Term, the implementation guide where Swiss-specific terminology (e.g., value sets, code systems) is defined. These terminologies can be used in CH Core as well as in exchange format IGs or organization-specific implementations. The CH Core IG defines core profiles as well as EPR (Electronic Patient Record) concepts.

CH TermSwiss TerminologyCH CoreSwiss Core Profiles,EPR ConceptsCH EMEDMedicationCH IPSPatient SummaryCH ...Other Exchange Formatsderivedderivedderivedderived

Fig. 1: Schematic overview of the dependencies between the Swiss IGs at the core (in red) and exchange format (in blue) level

The core artifacts serve as guidance and recommendations for how FHIR can and should be used in Switzerland. Fig. 2 illustrates this approach. This is implemented, for example, by defining elements such as Medication.code (see Fig. 2) for GTIN, a commonly used code in Switzerland. Specific value sets are also bound to the corresponding elements, but with low binding strength. Data types are specified according to Swiss-specific requirements as well. At the core level, the principle is to have no or as few mandatory constraints as possible, to ensure reusability.

CH Term Value Set:EDQM - Pharmaceutical Dose FormCH Core Medication Profile- code:GTIN(Slice defined in CH Core)- form ->EDQM - Pharmaceutical Dose Form (preferred) (VS defined in CH Term)- amount ->CH EMED Ratio with EMED Units (Data Type defined in CH Core)- etc.CH EMED Medication Profile- code:GTINMS (Slice defined in CH Core)- formMS->EDQM - Pharmaceutical Dose Form (required) (VS defined in CH Term)- amount ->CH EMED Ratio with EMED Units (Data Type defined in CH Core)- etc.CH IPS Medication Profile-imposeProfile Extension -> Medication IPS (to check conformity to UV IPS)- code:GTIN(Slice defined in CH Core)- form ->EDQM - Pharmaceutical Dose Form (preferred) (VS defined in CH Term)- amount ->CH EMED Ratio with EMED Units (Data Type defined in CH Core)- etc.derivedderivedderived

Fig. 2: Schematic overview of the dependencies shown at the profile level with focus on reusing the core artifacts

Also visible in Fig. 2, at the level of different exchange formats, is that these are derived from the core artifacts. The yellow highlighted text visualizes that requirements can become more strict at this level according to the specific use case.

This principle ensures both the reusability of common core artifacts as well as the ability to base further specifications (such as exchange formats) on them without complex dependencies.