Patient Demographics Query for mobile (PDQm)
2.4.0 - Trial-Implementation
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
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
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.
|
IHE.PDQm.server |
The PDQm Patient Demographics Supplier Actor requirements CapabililtyStatement expresses the requirements that shall be provided.
|
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.
|
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.
|
PDQm Patient Profile |
The PDQm Patient Profile
|
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:
|
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:
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 |