Can Cloverleaf make a PIX query?

[Peter Heggie]

From TCL?

Peter Heggie

Topic

[Jim Kosloskey]

Do you mean can the HL/7 Query message be built in Cloverleaf or is there some special connection you are referring to?

 

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Charlie Bursell]

Simple answer is yes, of course.  The PIX Query is a simple XML message.

But, without specifics I can say nothing more

[Peter Heggie]

Thank you both. What I’ve been told is that an HL7 message of the right message type and content can convey a PIX query to some query service. Now I’m thinking that something like a msgtype QBP^Q23 can be used to send a query. But the actual query string is dependent on the target system?

I got this sample PIX query HL7, which is supposed to request an “enterprise” MRN given a “local” MRN. I’m not sure what field holds the local MRN.

MSH|^~\&|NIST_Hydra_PIX_Consumer^^|NIST^^|MESSAGESERVICE^^|NEXTGATE^^|20171218135518||QBP^Q23^QBP_Q21|NIST-20171218135518|P|2.5
QPD|IHE PIX Query|QRY1243359573282|PIX10501^^^NIST2010&2.16.840.1.113883.3.72.5.9.1&ISO
RCP|I

Maybe the local MRN is in QPD#2. ?

Peter Heggie

[Jim Kosloskey]

According to the HL/7 2.5 doc Chapter 5. QPD-2 is used in the case of asynchronous exchanges and acts as a Query Identifier (like a Control ID). If used it is supposed to be repeated in the response to the query.

Again according to the standard, QPD-3 is supposed to contain parameters to the server. Those parameters can specify the segment and field where the query data can be found in the message.

You should receive a specification (conformance statement) from the receiving system documenting in detail how the exchange should transpire. Whether it is synchronous or asynchronous and how the needed data elements are identified and placed in both the query and the response.

 

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Charlie Bursell]

PIX Query HL7 Message Types

In the HL7 v2 IHE framework, this type of event is known as an ITI-9 transaction. It is triggered by the following HL7 v2 event, and is identified as a “Query” event with an event ID of 110112:

• Q23: Get corresponding identifiers

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

• K23: Corresponding patient identifiers

In the HL7 v3 IHE framework, this type of event is known as an ITI-45 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_TE201309UV02: Patient registry get identifiers query (triggers a PRPA_IN201309UV02 message)

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

• PRPA_IN201310UV02: Patient registry get identifiers query response
• Take a look here for definition of Q23 and its segments
  https://hl7-definition.caristix.com/v2/HL7v2.6/TriggerEvents/QBP_Q23

[Author]

Replies