CH EPR mHealth (R4)
0.2.0 - DSTU 1 Informative Ballot
CH EPR mHealth (R4)
0.2.0 - DSTU 1 Informative Ballot
This page is part of the CH EPR mHealth (R4) (v0.2.0: DSTU 1) based on FHIR R4. . For a full list of available versions, see the Directory of published versions 
This section specifies Swiss national extensions to Patient Identifier Cross-reference for Mobile (CH:PIXm) profile. The CH:PIXm is based on the Patient Identifier Cross-reference for Mobile (PIXm) profile and adds the feed for patient identities. PIXm is published as an IHE ITI Trial Implementation profiles.
In the Swiss EPR, the CH: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 feeded 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.
A mHealth App wants to get data from the EPR. The mHealth App needs to know the MPI-PID in the community. With the local identifier the mHealth 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.
The CH:PIXm Patient Identifier Cross-reference Manager adds the Mobile Patient Identity Feed [ITI-93] to the Patient Identity Source actor. 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.
No extensions or restrictions to the profile actor options are specified in the Swiss national extension.
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 Demographics Consumer | 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 mHealth 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.