This page is part of the CH EPR mHealth (R4) (v3.0.0: DSTU3) 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

Mobile Patient Demographics Query [ITI-78]

This section describes the national extension for the Swiss EPR to the Mobile Patient Demographics Query [ITI-78] transaction defined in the IUA profile published in the IHE IT Infrastructure Technical Framework Trial Implementation “Patient Demographics Query for mobile”.

Scope

The Mobile Patient Demographics Query is used by an app in the Swiss EPR to query with demographics parameters for a patient participating in the Swiss EPR.

Actor Roles

Actor: Patient Demographics Consumer
Role: Requests a list of patients matching the supplied set of demographics criteria (example: ID or Name) from the Patient Demographics Supplier. The Patient Demographics Consumer populates its attributes with demographic information received from the Patient Demographics Supplier.
Actor: Patient Demographics Supplier
Role: Returns demographic information for all patients matching the demographics criteria provided by the Patient Demographics Consumer

Referenced Standards

1. Patient Demographics Query for mobile (PDQm) Rev. 2.4.0
2. This PDQm Profile is based on Release 4 of the emerging HL7® FHIR® standard.

Messages

Query Patient Resource message

Message Semantics

The semantics of the Query Patient Resource message is the same as defined in 2:3.78.4.1.2, with the following restrictions:

• The telecom search parameter SHALL NOT be used.

Expected Actions

The Patient Demographics Supplier shall follow the expected actions as defined in 2:3.78.4.1.3, with the following restrictions:

• If there are more than 5 matches, the result should return zero matches with an OperationOutcome requesting more query parameters.

The patient data (see Patient example) SHALL conform to the PDQm Patient profile. The Patient Demographics Supplier SHALL reference the PDQm Patient profile or a derived constrained profile as a supportedProfile in the CapabilityStatement.

Message Example

Query for a patient with name Muster and birthdate 1995-01-27.

GET [base]/Patient?name=Muster&birthdate=1995-01-27
Accept: application/fhir+json
traceparent: 00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-00

Example response to above query

Query for a patient with name M returning too many results:

GET [base]/Patient?name=M
Accept: application/fhir+json
traceparent: 00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-00

Example response to above query

Query Patient Resource Response message

Retrieve Patient Resource message

The Retrieve Patient Resource is conducted by executing an HTTP GET against the Patient Demographics Supplier’s Patient Resource URL, providing the resource id of the patient being retrieved. The target is formatted as:

GET [base]/Patient/[resourceId]

Retrieve Patient Resource Response message

CapabilityStatement Resource

The CapabilityStatement resource for the Patient Demographics Consumer is PDQm Consumer.

The CapabilityStatement resource for the Patient Demographics Supplier is PDQm Supplier.

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 Mobile Patient Identifier Cross-reference Query [ITI-83] request must authorize using the [ITI-72] transaction of the IUA profile.

The traceparent header is required, as described in Trace Context header.

Security Audit Considerations

Patient Demographics Consumer Audit

The Patient Demographics Consumer shall be able to record a Patient Demographics Consumer AuditEvent. Audit Example for a PDQm Query transaction from consumer perspective.

Patient Demographics Supplier Audit

The Patient Demographics Supplier shall be able to record a Patient Demographics Supplier AuditEvent. Audit Example for a PDQm Query transaction from supplier perspective.