Extended PDQ - Discussion
Introduction
Takeaways from March Face-to-Face
1. In Patient Identity Feed, if you have any of the 15 fields (6 base traits plus 9 extended traits) then send them. Manager is required to deal with them if they receivet them. Draw on “best fit” language from the CP.
2. Karen will write a CP to change ITI-30 to “Patient Identity Feed – 2.5”. Right now there are two separate transactions in Vol 2 called “Patient Identity Feed” – ITI-8 and ITI-30. ITI-30 is HL7 V2.5-based where ITI-8 is V2.3-based.
3. In this supplement, we will add ITI-30 and the Patient Demographic Supplier actor to PIX.
4. In V3, we can draw on the Control Act for the last update date/time fields.
5. Also realize in PIX that you have to support all 15 fields in matching. This will require adding the “best fit” language to Patient Identity Feed (ITI-30) as “best fit” is currently part of Patient Demographics Query.
6. Karen is interested in being added as an author on this profile.
Open Issues
We propose that four of the original ten search fields that were part of the original profile proposal be dropped and one field added to replace them to accomplish the same effect. This is because addition of the four fields in question would require new segments to be added to various transactions while the substitute field, while accomplishing essentially the same work, would not.
Closed Issues
Karen Witting has been added as an author and Sandy Thames dropped.
A change proposal has been written to change the name of ITI-30 from "Patient Identity Feed" to "Patient Identity Feed - 2.5" to distinguish it from ITI-8 "Patient Identity Feed".
ITI-30 will be added as an optional transaction to PIX as part of this supplement. Essentially, this adds an HL7 V2.5-based Patient Identity Feed option to PIX. Previously, PIX was limited to a 2.3.1-based Patient Identity Feed.
Links
Original profile proposal from 2007 planning period - Extended PDQ
Patient Demographics Option (PDO) working documents