This page is part of the CH EPR mHealth (R4) (v3.0.0-ballot: Draft Ballot 1) based on FHIR 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

Patient Identifier Cross-referencing for mobile (PIXm)

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.

Scope

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.

Use Cases

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.

Actors and Transactions, Content Specifications

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.

Actor Options

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.

Required Actor 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
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

Process Flow

For the process flow of this profile and its interplay with the other mHealth profiles see sequence diagrams.

Security Consideration

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.