CH EPR mHealth (R4)
0.2.0 - DSTU 1 Informative Ballot

CH EPR mHealth (R4), published by eHealth Suisse. This is not an authorized publication; it is the continuous build for version 0.2.0). This version is based on the current content of https://github.com/ehealthsuisse/ch-epr-mhealth/ and changes regularly. See the Directory of published versions

CH:PIXm Mobile Patient Identity Feed [ITI-93]

Scope

The Mobile Patient Identity Feed transaction sends a FHIR Bundle of new and updated Patient Resources.

Actor Roles

Actor: Supplier played by Patient Identity Source
Role: Provides notification to the Patient Identifier Cross-reference Manager for any patient identification related events including: creation, updates, merges, etc.
Actor: Consumer played by Patient Identifier Cross-reference Manager
Role: Based on information provided in each Patient Identification Domain by a Patient Identification Source Actor, it manages the cross-referencing of patient identifiers across Patient Identification Domains.

Referenced Standards

Patient Identifier Cross-reference for Mobile (PIXm), Rev. 2.1 – Trial Implementation, December 5, 2019
Patient Master Identity Registry (PMIR) – Revision 1.1 – December 5, 2019

Messages

Interaction Diagram for [ITI-93]SupplierSupplierConsumerConsumerMobile Patient Identity Feed RequestMobile Patient Identity Feed Response

Trigger Events

A Supplier triggers a Mobile Patient Identity Feed request to a Consumer when patients are created, updated, merged or deleted.

Message Semantics

The same message semantic apply as in 3.93.4.1.2 Message Semantics.

The patient data (see Patient example) SHALL be conform to the CH:PIXm Patient profile with the canonical url http://fhir.ch/ig/ch-epr-mhealth/StructureDefinition/ch-pixm-patient. If the patient is already registered in a community, the MPI-PID SHALL be provided as an identifier. The EPR-SPID as an identifier MAY be added. The birthname can be added with the ISO 21090 qualifier extension, the religion SHALL not be added.

Expected Actions Consumer played by Patient Identifier Cross-reference Manager

If the MPI-PID is provided as an identifier the Patient Identifier Cross-reference Manager SHALL use the MPI-PID to correlate the patient in the community.

Message Example

See Bundle example (and the corresponding profile) for the Mobile Patient Identity Feed request.
See Bundle example (and the corresponding profile) for the Mobile Patient Identity Feed response.

Security Consideration

TLS SHALL be used. This national extension enforces authentication and authorization of access to the Patient Identifier Cross-reference Manager using the IUA profile with basic access token. Consequently the CH:PIXm Mobile Patient Identity Feed [ITI-93] request must authorize using the Incorporate Access Token [ITI-72] transaction of the IUA profile.