Contents
Open Issues ..................................................................................................................................... 3
1 Foreword................................................................................................................................. 3
Profile Abstract ........................................................................................................................... 5
25 Organization of the Documentation............................................................................................ 5
History of Annual Changes......................................................................................................... 6
5.1 Actors/Transactions .............................................................................................................. 6
5.2 Patient Identifier Cross-referencing Integration Profile Options.......................................... 6
8 Patient Demographics Query (PDQ) ...................................................................................... 7
30 8.1 Actors/Transactions ........................................................................................................ 7
8.2 Patient Demographics Query Integration Profile Options .............................................. 7
3.8B.2 Use Case Roles................................................................................................................ 8
3.8B.3 Referenced Standards...................................................................................................... 8
3.8B.4 Interaction Diagrams ....................................................................................................... 9
35 3.8B.4.1 Patient Identity Management – Register or Update Patient ......................................... 9
3.8B.4.1.1 Trigger Events ........................................................................................................... 9
3.8B.4.1.2 Message Semantics ................................................................................................... 9
3.8B.4.1.3 Expected Actions – PIX Manager........................................................................... 11
3.8B.4.1.4 Expected Actions – Document Registry ................................................................. 15
40 3.8B.4.2 Patient Identity Management – Patient Identity Merge ............................................. 15
3.8B.4.2.1 Trigger Events ......................................................................................................... 15
3.8B.4.2.2 Message Semantics ................................................................................................. 15
3.8B.4.2.3 Expected Actions – PIX Manager........................................................................... 16
3.8B.4.2.4 Expected Actions – Document Registry ................................................................. 17
45 3.9B.2 Use Case Roles.............................................................................................................. 18
3.9B.3 Referenced Standards.................................................................................................... 18
3.9B.4 Interaction Diagrams ..................................................................................................... 19
3.9B.4.1 Get Corresponding Identifiers.................................................................................... 19
3.9B.4.1.1 Trigger Events ......................................................................................................... 19
50 3.9B.4.1.2 Message Semantics ................................................................................................. 19
3.9B.4.1.3 Expected Actions..................................................................................................... 20
3.9B.4.2 Return Corresponding Identifiers............................................................................... 21
3.9B.4.2.1 Trigger Events ......................................................................................................... 21
3.9B.4.2.2 Message Semantics ................................................................................................. 21
55 3.9B.4.2.2.6 Patient Identifier Cross-Reference Manager Query Response Behaviour ........... 23
3.9B.4.2.3 Expected Actions..................................................................................................... 24
3.10B.2 Use Case Roles............................................................................................................ 25
3.10B.3 Referenced Standards.................................................................................................. 25
3.10B.4 Interaction Diagrams ................................................................................................... 25
60 3.10B.4.1 Update Person Information ...................................................................................... 26
3.10.B4.1.1 Trigger Events ....................................................................................................... 26
3.10B.4.1.2 Message Semantics ............................................................................................... 26
3.10B.4.1.3 Expected Actions................................................................................................... 28
3.21B.2 Use Case Roles............................................................................................................ 28
IHE IT Infrastructure Technical Framework, Supplement PIX/PDQ HL7 v3
______________________________________________________________________________
__________________________________________________________________________
Trial Implementation Version
2006-11-06 Copyright © 2006: ACC/HIMSS/RSNA
2
65 3.21B.3 Referenced Standards.................................................................................................. 29
3.21B.4 Interaction Diagrams ................................................................................................... 29
3.21B.4.1 Patient Demographics Query ................................................................................... 29
3.21B.4.1.1 Trigger Events ....................................................................................................... 29
3.21B.4.1.2 Message Semantics ............................................................................................... 29
70 3.21B.4.1.3 Expected Actions................................................................................................... 33
Patient Demographics Query Response.................................................................................... 34
3.21B.4.1.1 Trigger Events ....................................................................................................... 34
3.21B.4.1.2 Message Semantics ............................................................................................... 34
3.21B.4.1.3 Expected Actions................................................................................................... 39
75 Appendix E: IHE Requirements for Patient Identifier Data Types in HL7 Messages........... 41
Appendix O: HL7 v3 Transmission and Trigger Event Control Act Wrappers ........................... 46
Appendix P: PIX HL7 v3 New Person Added Sample Message................................................. 48
Appendix Q: PIX HL7 v3 Payload Schemas................................................................................ 53
Appendix R: Mapping of HL7v2.5 to HL7v3 for PIX and PDQ.................................................. 56
80
IHE IT Infrastructure Technical Framework, Supplement PIX/PDQ HL7 v3
______________________________________________________________________________
__________________________________________________________________________
Trial Implementation Version
2006-11-06 Copyright © 2006: ACC/HIMSS/RSNA
3
Open Issues
1. As this is the first time that IHE adds HL7 V3 messages equivalence as options to a
transaction which has been defined with HL7 V2 messages, the Technical Framework section
numbering has to reflect this new structure. After many discussions within the Technical
85 Committee, is was decided to add suffix "A" or "B" after the second level section numbers of
Volume 2 document, to represent (original) HL7 V2 message definitions and HL7 V3 message
definitions (added in this supplement) of the transactions, respectively. For example, 3.8A.4 and
3.8B.4 describe the interaction diagrams of HL7 V2 and V3 messages, both of the Patient
Identity Feed transaction. The Technical Committee recognizes that this |
|
资源大小：632.57 KB 
