| ITI46 | ITI46-1 | to be reviewed | Testable |
0
|
1
| | PIXV3 Update Notification [ITI-46] transaction references the following standard HL7 Version 3 Edition 2008 Patient Administration DSTU, Patient Topic (found at http://www.hl7.org/memonly/downloads/v3edition.cfm#V32008) | 237 | Section 3.46.3 | 9/3/18 6:28:49 PM by Meenal T |
|
| ITI46 | ITI46-10 | to be reviewed | Testable |
0
|
2
| | Consumer CON_A is configured to receive update notifications for domains DOM_A and DOM_AD. A PIXV3 Patient Registry Record Add message is processed for DOM_AD. The Patient Identifier Cross-reference Manager cross references this patient with DOM_A. The update notification shall contain the patient identifiers for both DOM_A and DOM_AD.
| 238 | Section 3.46.4.1.2 | 2/24/15 5:36:05 PM by Jean-François Labbe |
|
| ITI46 | ITI46-11 | to be reviewed | Testable |
0
|
2
| | Consumer CON_A is configured to receive update notifications for domains DOM_A and DOM_AD. A PIXV3 Patient Registry Record Revise message is processed for DOM_AD changing the patient address. The Patient Identifier Cross-reference Manager cross references determines this patient is no longer the same patient as DOM_A. Two update notifications shall be sent. One containing the patient identifier for DOM_A. The other one containing the patient identifier for DOM_AD. | 238 | Section 3.46.4.1.2 | 2/24/15 5:36:05 PM by Jean-François Labbe |
|
| ITI46 | ITI46-12 | to be reviewed | Testable |
0
|
2
| | The Patient Identifier Cross-reference Manager shall have configuration indicating which Identity Consumers are interested in receiving the PIXV3 Update Notification Transactions. | 238 | Section 3.46.4.1.2 | 2/24/15 5:36:05 PM by Jean-François Labbe |
|
| ITI46 | ITI46-13 | to be reviewed | Testable |
0
|
2
| | This configuration information shall include identification of the identity consumer systems interested in receiving notifications and, for each of those systems, a list of the patient identifier domains of interest. | 238 | Section 3.46.4.1.2 | 2/24/15 5:36:05 PM by Jean-François Labbe |
|
| ITI46 | ITI46-14 | to be reviewed | Testable |
0
|
2
| | The Patient Registry Record Revised message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V | 242 | Section 3.46.4.1.2.4 | 9/3/18 6:28:50 PM by Meenal T |
|
| ITI46 | ITI46-15 | to be reviewed | Testable |
0
|
2
| | The following WSDL naming conventions SHALL apply:
âÃÂÃÂreviseâÃÂàmessage -> "PRPA_IN201302UV02_Message"
acknowledgement -> "MCCI_IN000002UV01_Message" | 242 | Section 3.46.4.1.2.4 | 9/3/18 6:28:50 PM by Meenal T |
|
| ITI46 | ITI46-16 | to be reviewed | Testable |
0
|
2
| | The identifiers found in both Patient.id and OtherIDs.id attributes shall be considered together to form a complete list of patient identifiers from the different Patient Identity domains in which this actor is interested. | 243 | Section 3.46.4.1.3 | 9/3/18 6:28:50 PM by Meenal T |
|
| ITI46 | ITI46-17 | to be reviewed | Testable |
0
|
2
| | In the case where the returned list of identifiers contains multiple identifiers for a single domain, the Patient Identifier Cross-reference Consumer shall either use ALL of the multiple identifiers from the given domain or it shall ignore ALL of the multiple identifiers from the given domain | 243 | Section 3.46.4.1.3 | 9/3/18 6:28:50 PM by Meenal T |
|
| ITI46 | ITI46-18 | to be reviewed | Testable |
0
|
2
| | The following WSDL naming conventions SHALL apply:
wsdl:definitions/@name="PIXConsumer":
PIX update message -> "PRPA_IN201302UV02_Message"
acknowledgement ->"MCCI_IN000002UV01_Message"
portType -> "PIXConsumer_PortType"
get identifiers operation -> "PIXConsumer_PRPA_IN201302UV02"
SOAP 1.2 binding -> "PIXConsumer_Binding_Soap12"
SOAP 1.2 port -> "PIXConsumer_Port_Soap12" | 243 | Section 3.46.4.1.3.1 | 2/24/15 5:36:05 PM by Jean-François Labbe |
|
| ITI46 | ITI46-19 | to be reviewed | Testable |
0
|
2
| | When grouped with ATNA Secure Node or Secure Application actors, this transaction is to be audited as Patient Record event, as defined in ITI TF-2a: Table 3.20.6-1. Tables 3.46.5.1.1 show items that are required to be part of the audit record produced by the Patient Identifier Cross-reference manager actor for this transaction | 245 | Section 3.46.5.1 | 9/3/18 6:28:50 PM by Meenal T |
|
| ITI46 | ITI46-2 | to be reviewed | Testable |
0
|
3
| | Implementers of this transaction shall comply with all requirements described in ITI TF-2x: Appendix V Web Services for IHE Transactions. | 237 | Section 3.46.3 | 9/3/18 6:28:51 PM by Meenal T |
|
| ITI46 | ITI46-20 | to be reviewed | Testable |
0
|
2
| | When grouped with ATNA Secure Node or Secure Application actors, this transaction is to be audited as Patient Record event, as defined in ITI TF-2a: Table 3.20.6-1. Tables 3.46.5.1.2 show items that are required to be part of the audit record produced by the Patient Identifier Cross-reference consumer actor for this transaction | 245 | Section 3.46.5.1 | 2/24/15 5:36:05 PM by Jean-François Labbe |
|
| ITI46 | ITI46-21 | to be reviewed | Testable |
0
|
2
| | Whenever the Patient Identifier Cross-reference Consumer receives updated identifier information in a Patient Revise message that results in a change to the cross-referencing of a patient, the actor shall update its internal identifier information for the affected patient(s) in all domains in which it is interested | 243 | Section 3.46.4.1.3 | 9/3/18 6:28:51 PM by Meenal T |
|
| ITI46 | ITI46-3 | to be reviewed | Testable |
0
|
2
| | The Patient Identifier Cross-reference Manager shall notify a Patient Identifier Cross-reference Consumer when there is a change in a set of cross-referenced patient identifiers for any of the patient identifiers belonging to Patient Identifier Domains of interest to the consumer | 238 | Section 3.46.4.1.1 | 9/3/18 6:28:51 PM by Meenal T |
|
| ITI46 | ITI46-4 | to be reviewed | Testable |
0
|
2
| | Several notifications may have to be issued to communicate a single update to a set of cross-reference patient identifiers as required to reflect all the changes on the resulting sets of cross-reference patient Identifiers belonging to Patient Identifier Domains of interest to the Patient Identifier Cross-referencing Consumer | 238 | Section 3.46.4.1.1 | 9/3/18 6:28:51 PM by Meenal T |
|
| ITI46 | ITI46-5 | to be reviewed | Testable |
0
|
2
| | The following HL7 trigger event will be used to update to the list of patient identifiers: Patient Registry Record Revised (PRPA_TE201302UV02). This trigger event signals that patient information was revised in a patient registry.
| 238 | Section 3.46.4.1.1 | 9/3/18 6:28:51 PM by Meenal T |
|
| ITI46 | ITI46-6 | to be reviewed | Testable |
0
|
2
| | The PIX Update Notification transaction is conducted by the Patient Revise (PRPA_MT201302UV02) message | 238 | Section 3.46.4.1.2 | 9/3/18 6:28:51 PM by Meenal T |
|
| ITI46 | ITI46-7 | to be reviewed | Testable |
0
|
2
| | Each message shall be acknowledged by the HL7 V3 Accept Acknowledgement (MCCI_MT000200UV01), which is described in ITI TF-2x: Appendix O | 238 | Section 3.46.4.1.2 | 9/3/18 6:28:51 PM by Meenal T |
|
| ITI46 | ITI46-8 | to be reviewed | Testable |
0
|
2
| | The information provided by the Patient Identifier Cross-reference Manager to Patient Identifier Cross-reference Consumer Actors shall only contain a list of cross-referenced identifiers for the domains of interest as configured with the Patient Identifier Cross-reference Manager in two or more of the domains managed by the Patient Identifier Cross-reference Manager | 238 | Section 3.46.4.1.2 | 9/3/18 6:28:51 PM by Meenal T |
|