CH EPR mHealth (R4)
1.0.0 - DSTU 1

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

Home

Introduction

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).

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

Conformance Expectations

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].

This implementation guide uses Must Support in StructureDefinitions with the definition found in Appendix Z. This is equivalent to the IHE use of R2 as defined in Appendix Z.

Scope of precisions

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

Overview

Introduction

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, for example in web based primary systems.

The scope of this extension covers the following use cases:

  1. Client authentication and authorization;
  2. User Authentication;
  3. Read documents from the EPR;
  4. Write documents to the EPR;
  5. Write logs to the EPR ATNA Audit Record 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.

Profiles, actors and transactions

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

Profiles, actors and transactions covered in this national extensionmHealth: AppmHealth: APIIUA Authorization ClientPIXm Patient Identifier Cross-reference ConsumerPIXm Patient Identity SourceMHD Document SourceMHD Document ConsumerRESTful ATNA Secure NodeIUA Authorization ServerIUA Resource ServerPIXm Patient Identifier Cross-reference ManagerMHD Document RecipientMHD Document ResponderRESTful ATNA Audit Record RepositoryUser Authentication ProviderGet Access Token [ITI-71],Get Authorization Server Metadata [ITI-103]Incorporate Access Token [ITI-72]Mobile Patient Identifier Cross-reference Query [ITI-83]Patient Identity Feed FHIR [ITI-104]Provide Document Bundle [ITI-65]Find Document Lists [ITI-66],Find Document References [ITI-67],Retrieve Document [ITI-68]Record Audit Event [ITI-20]Authenticate User