Difference between PIX and PDQ

[Jim]

Hi,

Our product already supports PDQ profile.But as part of HIMSS, We are
planning to Implement PIX.
Is it worth to implement PIX?. Could you please help me in
understanding PIX vs PDQ?

Thanks

Jim.J

[Dmytro Rud]

Hi Jim,

Here some interesting links for you:

http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Rev8-0_Vol1_FT_2011-08-19.pdf
http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Rev8-0_Vol2a_FT_2011-08-19.pdf

Regards,
Dmytro

2011/9/20 Jim <jaihin...@gmail.com>:

[Marek0]

Jim.J,

here a quick list of technical differences. I am sure there are more
comparisons like this "out there".

Both PIX and PDQ define how to query for patient data.
Both PIX and PDQ are based on HL7 and MLLP.
Both PIX and PDQ have a newer "edition" of the profile, based on HL7v3
and "IHE Appendix V" WebServices (PIXv3/PDQv3).

PDQ (Patient Demographics Query) only defines one interaction: a query
(ITI-21). The system responding to queries and maintaining the patient
data (Patient Demographics Supplier) may support multiple patient IDs
(multiple Patient Identifier Domains) or not. Query responses may turn
out large, therefore system have be able to split it (continuation).
Demographic data such as name, date of birth, address may be used as
query parameters.

PIX (Patient Identifier Cross-Referencing) is about a system (PIX
Manager) that links patient records from multiple sources together .
The profile describes how to feed the PIX Manager with new/updated/
merged patient data (ITI-8), how to query for associated patient
identifiers (ITI-9) and how to let PIX Manger notify other systems,
when an association changes (ITI-10). PIX queries deal with patient
identifiers only (therefore no big responses => no continuation
required).

The above is also true for PIXv3/PDQv3, when HL7v2/MLLP terms are
transposed into HL7v3/WS.

I hope this helps.
Marek