Patient Demographics Query

A patient demographics query event is triggered when a consumer needs to select a patient based on demographic data. The consumer requests information about patients that match the data from the master patient index. The query message provides a set of demographic data, which the master patient index compares and matches against existing records in the database. The master patient index generates a response with the demographic data for matching patients.

Patient Demographics Query Processing Flow

Patient demographics queries are processed as follows. This can be seen in the figure Figure 1.

1. A request is sent by an HL7 messaging domain for patients whose demographic information closely matches the demographic data sent in.

2. The message is received by the HL7 Binding Component if it is HL7 v2, or by the HTTP Binding Component if it is HL7 v3.

3. The message processed through the Normalized Message Router (NMR) to one of the following BPEL processes, depending on which version of HL7 is being processed: IHEPixPdqV2BpelProcess (v2) or bpelPDQManager (v3).

4. The BPEL process maps the data and routes it to the MDM Facade EJB, which then sends it to the Master Index for processing.

5. The Master Index compares the input data against existing records in the database. Any matches are returned to the BPEL process.

6. The BPEL process then sends the patient information back through the NMR and Binding Components to the originating domain, and generates an ACK or NACK response, which is also sent back out to the originating domain.

7. The BPEL process generates the audit record of the transaction, which is stored in the ATNA repository.

Patient Demographics Query HL7 Message Types

In the HL7 v2 IHE framework, this type of event is also called an ITI-21 transaction. It is triggered by the following HL7 v2 event. For audit purposes, it is identified as a “Query” event with an event ID of 110112.

• Q22: Find candidates

The master patient index response to the above request is the following HL7 v2 event:

• K22: Find candidates response

In the HL7 v3 IHE framework, this type of event is also called an ITI-47 transaction. It is triggered by the following HL7 v3 event. For audit purposes, it is identified as a “Query” event with an event ID of 110112.

• PRPA_TE201305UV02: Find candidates query (triggers a PRPA_IN201305UV02 message)

The master patient index response to the above request is the following HL7 v3 event:

• PRPA_IN201306UV02: Find candidates query (triggers a PRPA_IN201306UV02 message)