CH EPR FHIR (R4), published by eHealth Suisse. This guide is not an authorized publication; it is the continuous build for version 4.0.1-ballot-2 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

Patient Demographics Match [ITI-119]

This section describes the national extension for the Swiss EPR to the Patient Demographics Match [ITI-119] 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) 3.0.0
2. This PDQm Profile is based on Release 4 of the emerging HL7® FHIR® standard.

Messages

Match Patient Resource Message

Message Semantics

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

• When specifying the count parameter, no more than 5 matches SHALL be requested.

The HTTP body SHALL conform to the PDQm Match Input Parameters profile.

Expected Actions

The Patient Demographics Supplier shall follow the expected actions as defined in 2:3.119.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.
• If the client requests more than 5 matches, the result should return zero matches with an OperationOutcome explaining the server can't fulfill the request.
• Patient identifiers other than the MPI-PID and EPR-SPID SHALL NOT be returned.

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 family name Muster and birthdate 1995-01-27.

POST [base]/Patient/$match
Content-Type: application/fhir+json
Accept: application/fhir+json
traceparent: 00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-00

{
  "resourceType" : "Parameters",
  "parameter" : [
    {
      "name" : "resource",
      "resource" : {
        "resourceType" : "Patient",
        "name" : [
          {
            "family" : "Muster",
          }
        ],
        "birthDate" : "1995-01-27"
      }
    }
  ]
}

Example response to above query

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

POST [base]/Patient/$match
Content-Type: application/fhir+json
Accept: application/fhir+json
traceparent: 00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-00

{
  "resourceType" : "Parameters",
  "parameter" : [
    {
      "name" : "resource",
      "resource" : {
        "resourceType" : "Patient",
        "name" : [
          {
            "family" : "M",
          }
        ]
      }
    }
  ]
}

Example response to above query

Query Patient Resource Response message

The response Bundle SHALL conform to the PDQm Match Output Bundle profile.

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

The transaction SHALL be secured by Transport Layer Security (TLS) encryption and server authentication with server certificates.

The transaction SHALL use client authentication and authorization using basic authorization token as defined in the IUA profile. The authorization token SHALL be conveyed as defined in the Incorporate Access Token [ITI-72] transaction.

The actors SHALL support the traceparent header handling, as defined in Appendix: Trace Context.

Security Audit Considerations

Patient Demographics Consumer Audit

The Patient Demographics Consumer shall record a CH Audit Event for [ITI-119] Patient Demographics Consumer (example).

Patient Demographics Supplier Audit

The Patient Demographics Supplier shall record a CH Audit Event for [ITI-119] Patient Demographics Supplier (example).