CH EPR mHealth (R4)
0.1.1 - Draft Standard for Trial Use

This page is part of the CH EPR mHealth (R4) (v0.1.1: DSTU 1) based on FHIR R4. . For a full list of available versions, see the Directory of published versions



The national extensions documented in this implementation guide shall be used in conjunction with the definitions of integration profiles, actors and transactions provided in Volumes 1 through 3 of the IHE IT Infrastructure Technical Framework.

This implementation guide with national extensions of IHE integration profiles was authored in order to fulfil the Swiss regulations of the Ordinance on the Electronic Patient Record (EPRO, SR 816.11). The EPRO and the EPRO-DFI are published in Official Compilation of Federal Legislation (AS) (available in German, French and Italian).


The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in [RFC2119].

Scope of precisions

The extensions, restrictions and translations specified apply to the following IHE IT Infrastructure (ITI) Integration profiles:



This national extension is motivated by the intention to ease integration of mobile applications to the Swiss EPR by extending the IHE FHIR based mobile profiles. This national extension to IHE profiles is intended for mobile applications running on mobile devices, but not limited to. The IHE FHIR based mobile profiles use technologies (REST, OAuth, etc.) which are widely spread in the developer community and may be used for native applications and Web Applications as well, for example in primary systems.

The scope of this extension covers the following use cases:

  1. User Authentication and authorization;
  2. Read documents from the EPR;
  3. Write documents to the EPR;
  4. Write logs to the EPR ATNA Audit Repository.

This extension covers two options:

  1. Generic mHealth option – This option adresses primary systems or mobile applications using the basic EPR flows but replace the XDS.b related and PIX V3 profiles with the FHIR based profiles;
  2. SMART on FHIR – This option adresses mobile apps or modular primary systems that want to connect to the Swiss EPR using SMART on FHIR.

The options differ by the architecture for the user authentication and request authorization. While in the generic mHealth option all profiles and extensions defined in this extension must be applied, in the SMART on FHIR option only a subset of the mHealth profiles and transactions must be applied.

Profiles, actors and transactions

The following figure shows the profiles, actors and transactions specified or referenced in this national extension:

Figure 1: Profiles, actors and transactions covered in this national extension

Figure 1: Profiles, actors and transactions covered in this national extension