Overview
The Patient Demographics Query for Mobile (PDQm) Profile provides a transaction for mobile and lightweight browser-based applications to query a patient demographics supplier for a list of patients based on user-defined search criteria and retrieve a patient’s demographic information.
Using these patterns, the PDQm Profile exposes the functionality of a patient demographics supplier to mobile applications and lightweight browser applications. The following list provides a few examples of how PDQm might be leveraged by implementers:
- A health portal securely exposing demographics data to browser based plugins
- Medical devices which need to access patient demographic information
- Mobile devices used by physicians (example bedside eCharts) which need to establish patient context by scanning a bracelet
- Web based EHR/EMR applications which wish to provide dynamic updates of patient demographic information such as a non-postback search, additional demographic detail, etc.
- Any low resource application which exposes patient demographic search functionality
- Any application using the MHD Profile to access documents may use PDQm to find an appropriate patient identifier
Actors and Transactions
The following diagram provides an overview of the PDQm profile Actors, Transactions and their interactions.
The table below lists the transactions for each actor directly involved in the PDQm profile. To claim compliance with PDQm, an actor shall support all required transactions (labeled “R”).
Actor | Transaction | Optionality |
---|---|---|
Patient Identity Manager | Mobile Patient Demographic Query [ITI-78] | R |
Patient Demographics Consumer | Mobile Patient Demographic Query [ITI-78] | R |
Transactions
- Mobile Patient Demographic Query [ITI-78] - 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. Uses a FHIR Patient Query: GET [base]/Patient?<query>