CH eTOC (R4)
2.0.1 - trial-use Switzerland flag

This page is part of the CH eTOC (R4) (v2.0.1: STU 2) 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


Official URL: Version: 2.0.1
Active as of 2023-12-28 Computable Name: CH_eTOC

Copyright/Legal: CC0-1.0


The CH eTransition of Care (CH eTOC) Implementation Guide defines the content of a referral from a GP to the hospital, to a specialist, from one hospital to another etc.

CH eTOC is intended primarly for use in directional information exchange and for the use in the SWISS EPR. It however may be implemented in other settings too.

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


This Implementation Guide uses FHIR defined resources. For details on HL7 FHIR R4 see

Because the Implementation Guide relies heavily on the FHIR Resources Questionnaire and QuestionnaireResponse, forms are addressed here as Questionnaires.

This Implementation Guide is derived from the CH Order & Referral by Form (CH ORF) Implementation Guide (CH ORF) which relies on HL7 Structured Data Capture Implementation Guide, see SDC and uses the Swiss Core Profiles, see CH Core.

April 7, 2022 the HL7 Switzerland Technical Committee discussed #39 and finally voted to set cardinality for the Questionnaire and QuestionnaireResponse to 1.. in the composition resource thus making the use of Questionnaires and QuestionnaireResponses mandatory (see also CH ORF).

Applications claiming for conformance with an CH ORF derived implementation guide shall:

Render (and in case of the Questionnaire Filler allow for data entry) all elements of a questionnaire in the user interface (e.g. on screen, in print). Grouping of items and the order of items within shall be adequately reproduced according to the questionnaire.

Vendors of applications with Questionnaire Filler/Questionnaire Receiver actors are strongly recommended to implement interfaces to other applications (such as HIS and PACS) at least for all data in the generics elements of questionnaires.

In the 3rd report of the Interprofessional Working Group on Electronic Patient Dossiers (IPAG) eDischarge Report, recommendations are formulated that are important for the inter-professional exchange of information during transitions of treatment (transition of care). The information relevant to treatment shall be be described in an exchange format that makes suggestions for structuring the content of interprofessional data content.

At the working group meeting in February 2021, it was decided that a first version of eTOC shall be based on the the FHIR International Patient Summary (IPS).

However, this first version of CH eTOC still allows many free text entries. Reason: According to IPAG, in a first step, the items shall be implemented as text. It can be expected, that users want to copy paste results: it seems sensible, to have multiple entries for lab, but other findings are mostly in freetext and therefore it makes sense to copy all findings in one copy-paste action.

Clinical content uses mostly the same resources as the IPS. The resource definitions are however constrained from FHIR base definitions and CH Core definitions and NOT from UVIPS. This decision was made in order to minimize unexpected impact of future changes in IPS and for compatibility with Swiss Core.

Corresponding section in the IPS Resource / Datatype Derived from
IPS Medication Summary CH EMED MedicationStatement MedicationStatement
CH EMED Medication Medication
CH EMED Dosage Dosage
IPS Allergies and Intolerances ChEtocAllergyIntolerance ChAllergyIntolerance
IPS Problem List ChEtocPrimaryDiagnosisCondition Condition
ChEtocSecondaryDiagnosisCondition Condition
IPS Immunizations ChEtocImmunization ChVacdImmunization
IPS History of Procedures ChEtocProcedure Prozedure
IPS Medical Devices ChEtocDevice Device
IPS Diagnostic Results ChEtocLabObservation Observation
ChEtocPathologyObservation Observation
ChEtocRadiologyObservation Observation
ChEtocCardiologyObservation Observation
ChEtocBodyHeightObservation HL7BodyHeight
ChEtocBodyWeightObservation HL7BodyWeight
IPS Past history of illnesses ChEtocPastHistoryofIllnessesCondition Condition
IPS Pregnancy ChEtocPregnancyStatusObservation Observation
CH eToc Expected Delivery Date Observation Observation
IPS Social History ChEtocSocialHistoryCondition Condition
IPS IFunctional Status ChEtocFunctionalStatusCondition Condition
IPS Advance Directives Not supported yet

[Table 1] Resources and datatypes for clinical content

In addition to the Composition (IPS), the CH eTOC Composition provides a sectionPurpose.

CH eTOC alllows to distinguish between primary and secondary diagnosis; both are referenced in sectionProblems. sectionAttachment allowsnfor attachment (whatever is considered as important).

There is no sectionVitalSigns such as provided by the IPS. This is in order to prevent duplicate content.

SectionPlanOfCare is omitted for the following reason: It can be assumed that careplans will be available at best as pdf files for the foreseeable future. There is therefore a need to provide careplans as an attachment. This is what the Attachment section is for.

All other sections for clinical content use the same wording for section titles as the Composition (IPS):

sectionMedications sectionImmunizations sectionAllergies sectionPastIllnessHx sectionFunctionalStatus sectionProceduresHx sectionSocialHistory sectionMedicalDevices sectionResults sectionPregnancyHx

As a consequence of the above CH eTOC does not claim to be conformant to IPS for now.

Derivations for use cases in different disciplines are to be defined later.

eTOC adds a ServiceRequest resource to the clinical content (according to the IPS) in order to depict the reason for a referral, the requested service and some additional information (e.g. coverage, room preferance etc.).

Header information such as sender, receiver etc. are considered as Generic Elements (to all sorts of referral, orders etc.) and follow the definition in the ORF Implementation Guide.

Copy receiver is meant to receive a copy from the order and all evolving results thereof.

Actors, transactions and security considerations are covered in the corresponding sections of CH-ORF


Value sets and coding are preliminary and not yet approved by eHealth Suisse.

Safety Considerations

This implementation guide defines data elements, resources, formats, and methods for exchanging healthcare data between different participants in the healthcare process. As such, clinical safety is a key concern. Additional guidance regarding safety for the specification’s many and various implementations is available at:

Although the present specification does gives users the opportunity to observe data protection and data security regulations, its use does not guarantee compliance with these regulations. Effective compliance must be ensured by appropriate measures during implementation projects and in daily operations. The corresponding implementation measures are explained in the standard. In addition, the present specification can only influence compliance with the security regulations in the technical area of standardisation. It cannot influence organisational and contractual matters.

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.

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 ( and R4B ( are available.

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)


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, Dec 19, 2023 12:36+0100+01:00)


FHIR implementation guide CH Core (built Thu, Dec 28, 2023 08:42+0100+01: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)


Order & Referral by Form - Implementation Guide (CH ORF) (built Thu, Dec 28, 2023 11:35+0100+01:00)


Implementation Guide for the eMedication in Switzerland. (built Thu, Dec 28, 2023 09:59+0100+01:00)

Package hl7.fhir.uv.ips#1.0.0

International Patient Summary (IPS) FHIR Implementation Guide (built Tue, May 19, 2020 18:36+0000+00:00)


Implementation guide CH-AllergyIntolerance (R4) (built Thu, Dec 28, 2023 10:34+0100+01:00)

Globals Table

There are no Global profiles defined