CH EPR FHIR (R4)
4.0.0-ballot - ballot
This page is part of the CH EPR FHIR (R4) (v4.0.0-ballot: DSTU 4 Ballot 1) 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
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.
The national extensions adds an additional transaction to≈from the Document Source to the Document Recipient.
An EPR App can query, retrieve or publish data to an EPR community using the transaction of the MHD profile. An EPR App can Update Document Metadata for a published document with this national extension.
In addition to the Document Sharing Use Case for MHD the national extension defines the following Use Cases:
A Healthcare professional has published a document in his own community for the patient but needs to update the metadata of the document. The healthcare professional updates the metadata (e.g. title) in the primary systems and submits the updated metadata to the community. The metadata which is allowed to be updated is defined in Annex 5.1 1.12.1.
A patient wants to change the confidentiality code of one of his documents. The patient updates the confidentiality code in the portal and the portal submits the updated metadata to the community.
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 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.