Patient Demographics Query for mobile (PDQm)
2.4.0 - Trial-Implementation International flag

This page is part of the IHE Patient Demographics Query for Mobile (v2.4.0: Trial Implementation) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Capability Statements

The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.

PDQm Client requirements CapabilityStatement

The PDQm Patient Demographics Consumer Actor requirements CapabililtyStatement expresses the requirements that can be utilized while being compliant.

  • Query against the FHIR endpoint to the Patient Resource endpoint
  • Using FHIR R4
  • may request json or xml encoding
  • should use a security framework. Recommend IHE-IUA or SMART-on-FHIR
  • Search Parameters that may be used
    • _id
    • active
    • family
    • given
    • identifier
    • telecom
    • birthdate
    • address
    • gender
    • mothersMaidenName
IHE.PDQm.server

The PDQm Patient Demographics Supplier Actor requirements CapabililtyStatement expresses the requirements that shall be provided.

  • Query against the FHIR endpoint to the Patient Resource endpoint
  • Using FHIR R4
  • shall support both json or xml encoding
  • should use a security framework. Recommend IHE-IUA or SMART-on-FHIR
  • Search Parameters that shall be supported
    • _id
    • active
    • family
    • given
    • identifier
    • telecom
    • birthdate
    • address
    • gender
    • mothersMaidenName

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide

Audit Event for PDQm Query at Consumer

Defines constraints on the AuditEvent (AuditMessage) Resource for a Patient Demographics Consumer to record when it performs a Patient Demographics Query ITI-78.

  • type (EventTypeCode) = EV(110112, DCM, Query)
  • action (EventActionCode) = E
  • subtype (EventTypeCode) = EV(ITI-78, urn:ihe:event-type-code, Mobile Patient Demographics Query)
  • agent (ActiveParticipant)
    • supplier as the Destination
    • consumer as the Source
      • this agent is the source of the auditEvent
    • other agents are allowed including identity of the application or infrastructure
  • entity (ParticipantObjectIdentification)
    • query parameters
    • no patient, because the consumer does not know the patient they are looking for or they wouldn’t be using this transaction.
Audit Event for PDQm Query at Supplier

Defines constraints on the AuditEvent (AuditMessage) Resource when a Patient Demographics Supplier responds to a Patient Demographics Query ITI-78.

  • type (EventTypeCode) = EV(110112, DCM, Query)
  • action (EventActionCode) = E
  • subtype (EventTypeCode) = EV(ITI-78, urn:ihe:event-type-code, Mobile Patient Demographics Query)
  • agent (ActiveParticipant)
    • supplier as the Destination
      • this agent is the source of the auditEvent
    • consumer as the Source
    • other agents are allowed including identity of the application or infrastructure
  • entity (ParticipantObjectIdentification)
    • query parameters
    • other entity are allowed including one to identify a patient when explicitly identified in the query parameters
PDQm Patient Profile

The PDQm Patient Profile

  • when any element in FHIR Core Patient are known, and when authorized to return the element, then all elements that are core to FHIR Patient should be returned
  • forbids modifier extensions - so that all uses do not need to be concerned with changes to the meaning of the core elements of the Patient resource
  • adds the patient-mothersMaidenName extension as an extension available to hold the mothers maiden name

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like

Audit Example of ITI-78 at Consumer

Audit Event for PDQm Query Transaction by the Patient Identifier Cross-reference Consumer

where the Query was executed with a GET as follows:

GET https://server.example.com/fhir/Patient?family=MOHR&given=ALICE&active=true&gender=female
Accept: application/fhir+json; fhirVersion=4.0
Audit Example of ITI-78 at Supplier

Audit Event for PDQm Query Transaction by the Patient Identifier Cross-reference Supplier

where the Query was executed with a GET as follows:

GET https://server.example.com/fhir/Patient?family=MOHR&given=ALICE&active=true&gender=female
Accept: application/fhir+json; fhirVersion=4.0

Note the Supplier may choose to record patient identities found, but is not required to.

Given the Supplier chooses to record a patient in the AuditEvent When the search finds multiple Patients, Then the Supplier would create an AuditEvent for each of those Patients.

This example shows where ex-patient is returned. This single result does not affect the response returned on the ITI-78 that would include all results.

Dummy Device example

Dummy Device example for completeness sake. No actual use of this resource other than an example target

Dummy Patient example

Dummy patient example for completeness sake. No actual use of this resource other than an example target