CH EPR FHIR (R4)
5.0.0-ballot-ci-build - ci-build
CH EPR FHIR (R4)
5.0.0-ballot-ci-build - ci-build
CH EPR FHIR (R4), published by eHealth Suisse. This guide is not an authorized publication; it is the continuous build for version 5.0.0-ballot-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/ehealthsuisse/ch-epr-fhir/ and changes regularly. See the Directory of published versions
This section specifies Swiss national extensions to Patient Identifier Cross-referencing for mobile (PIXm) profile. PIXm is published as an IHE ITI Trial Implementation profile.
In the Swiss EPR, the PIXm profile ensures that different systems can correlate the local identity with the MPI-PID (and EPR-SPID) for the community and that the initial demographics data can be fed to the MPI. The profile supports creation, update and deprecation of patient master identity information about a subject of care using the HL7 FHIR standard resources and RESTful transactions.
An EPR App wants to get data from the EPR. The EPR App needs to know the MPI-PID in the community. With the local identifier the EPR App can query the MPI-PID (and EPR-SPID) for the community. The local identifier with the initial demographics data needs to be setup initially in the community that the correlation is possible.
This national extension adds restrictions to the correlation to other local identifiers, to the query results and a specific patient content profile is defined. Otherwise there are no extensions or restrictions to the profile actors and the transaction.
This figure shows the actors directly involved in the Patient Identifier Cross-referencing for mobile Profile and the relevant transactions between them.
No extensions or restrictions to the profile actor options are specified in the Swiss national extension. Support for the 'Remove Patient' option for Patient Identity Source and Patient Identifier Cross-reference Manager is not required.
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 |
|---|---|---|
| Patient Identifier Cross-reference Manager | IUA Resource Server | R |
| Patient Identity Source | IUA Authorization Client | R |
| Patient Identifier Cross-reference 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 Identifier Cross-reference Manager using the IUA profile with basic access token as described in IUA.