CH EPR mHealth (R4)
4.0.0-ci-build - DSTU3
CH EPR mHealth (R4), published by eHealth Suisse. This guide is not an authorized publication; it is the continuous build for version 4.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/qligier/ch-epr-mhealth/ and changes regularly. See the Directory of published versions
This section specifies Swiss national extensions to the Mobile Access to Health Documents (MHD) with XDS on FHIR Profile, which is published as an IHE ITI Trial Implementation profile.
A mHealth App can query, retrieve or publish data to EPR communities using the transaction of the MHD profile.
No extensions or restrictions to the profile use cases are specified in the Swiss in national extension.
No extensions or restrictions to the actors and transactions are specified in the Swiss national extension.
This figure shows the actors directly involved in the Mobile Access to Health Documents Profile and the relevant transactions between them.
For all actors the Comprehensive Metadata Option and the XDS on FHIR Option SHALL be supported. For all actors the Metadata as defined in Annex 3 SHALL be supported.
The Actors Document Recipient and Document Responder MUST be grouped according to the XDS on FHIR grouping condition see Table 33.3-1: MHD - Actors Required Grouping. This national extension enforces authentication and authorization for access control. Therefore actors of this profile must be grouped with actors of other profiles according to the following table:
Actor | Required Grouping | Optionality |
---|---|---|
Document Recipient | IUA Resource Server | R |
Document Responder | IUA Authorization Client | R |
Document Source | IUA Authorization Client | R |
Document Consumer | IUA Authorization Client | R |
For the process flow of this profile and its interplay with the other mHealth profiles see sequence diagrams.
This national extension enforces authentication and authorization of access to the Patient Identity Manager using the IUA profile with extended access token as described in IUA.