| CH-PIX | CH-PIX-001 | reviewed | Testable |
1
|
1
| | In the "Person" parameter at least "Person.name" or "Patient.id" must be non-null (see Table Table 9: Patient Active and Revise Model Attributes) | 32 | Section 1.7.1.1 | 3/15/24 2:33:35 PM by vhofman |
|
| CH-PIX | CH-PIX-002 | reviewed | Testable |
1
|
1
| | In the "Person" parameter, in the "name" field the birth name is passed with the qualifier BR (see Table 9: Patient Active and Revise Model Attributes) | 32 | Section 1.7.1.1 | 3/15/24 2:33:35 PM by vhofman |
|
| CH-PIX | CH-PIX-003 | reviewed | Testable |
1
|
1
| | In the "Person" parameter, the "religiousAffiliationCode" MUST NOT be used (see Table 9: Patient Active and Revise Model Attributes) | 32 | Section 1.7.1.1 | 3/15/24 2:33:35 PM by vhofman |
|
| CH-PIX | CH-PIX-004 | reviewed | Testable |
1
|
1
| | In the "Person" parameter the "raceCode" field MUST NOT be used (see Table 9: Patient Active and Revise Model Attributes) | 32 | Section 1.7.1.1 | 3/15/24 2:33:35 PM by vhofman |
|
| CH-PIX | CH-PIX-005 | reviewed | Testable |
1
|
1
| | In the "Person" parameter, the "ethnicGroupCode" MUST NOT be used (see Table 9: Patient Active and Revise Model Attributes) | 32 | Section 1.7.1.1 | 3/15/24 2:33:35 PM by vhofman |
|
| CH-PIX | CH-PIX-007 | reviewed | Testable |
1
|
1
| | In the "PersonalRelationship" parameter, the code MUST NOT be used (see Table 9: Patient Active and Revise Model Attributes) | 32 | Section 1.7.1.1 | 3/15/24 2:33:35 PM by vhofman |
|
| CH-PIX | CH-PIX-008 | reviewed | Testable |
2
|
1
| | The DataSource Parameter SHALL be specified to the assigning authorities of the EPR-SPID and the MPI-PID in the affinity domain. Other assigning authorities SHALL not be used. | 36 | Section 1.8.1.1 | 3/15/24 2:33:35 PM by vhofman |
|
| CH-PIX | CH-PIX-010 | reviewed | Testable |
2
|
1
| | id[2..2](M)Patient(SET<II>) SHALL convey the patients local ID and the EPR-SPID. Field : Patient.id | 32 | Table 11 | 3/15/24 2:33:35 PM by vhofman |
|
| ITI44 | ITI44-1 | reviewed | Testable |
2
|
1
| | Patient Identity Feed HL7 V3 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). | 193 | Section 3.44.3 | 5/29/19 1:42:05 PM by aberge |
|
| ITI44 | ITI44-12 | reviewed | Testable |
1
|
2
| | The Patient Identifier Cross-reference Manager shall be capable of accepting attributes specified in Table 3.44.4.1.2-1 | 201 | Section 3.44.4.1.3 | 5/29/19 1:42:28 PM by aberge |
|
| ITI44 | ITI44-13 | validated | Testable |
1
|
2
| | Once the Patient Identifier Cross-reference Manager has completed its cross-referencing function, it shall make the newly cross-referenced identifiers available to PIX queries and send out notification to any Patient Identifier Cross-reference Consumers that have been configured as being interested in receiving such notifications using the PIX Update Notification HL7 V3 transaction (see ITI TF-2b: 3.46 for the details of that transaction). | 201 | Section 3.44.4.1.3 | 5/29/19 1:42:41 PM by aberge |
|
| ITI44 | ITI44-14 | reviewed | Testable |
1
|
2
| | The following WSDL naming conventions SHALL apply:
wsdl:definitions/@name="PIXManager":
add message -> "PRPA_IN201301UV02_Message"
revise message -> "PRPA_IN201302UV02_Message"
acknowledgement ->"MCCI_IN000002UV01_Message"
portType -> "PIXManager_PortType"
add operation -> "PIXManager_PRPA_IN201301UV02"
revise operation -> "PIXManager_PRPA_IN201302UV02"
SOAP 1.2 binding -> "PIXManager_Binding_Soap12"
SOAP 1.2 port -> "PIXManager_Port_Soap12"
| 202 | Section 3.44.4.1.3.1 | 5/29/19 1:42:49 PM by aberge |
|
| ITI44 | ITI44-19 | reviewed | Testable |
1
|
2
| | The Patient Registry Resolve Duplicates message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V. | 208 | Section 3.44.4.2.2.4 | 5/29/19 1:43:02 PM by aberge |
|
| ITI44 | ITI44-24 | reviewed | Testable |
1
|
3
| | Each HL7 Merge Patient message shall be acknowledged by the HL7 v3 Accept Acknowledgement (MCCI_MT000200UV01), which is described in ITI TF-2x: Appendix O | 205 | Section 3.44.4.2.2 | 5/29/19 1:43:14 PM by aberge |
|
| ITI44 | ITI44-25 | reviewed | Testable |
1
|
3
| | The Patient Registry Resolve Duplicates message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V. | 208 | Section 3.44.4.2.2.4 | 5/29/19 1:43:24 PM by aberge |
|
| ITI44 | ITI44-27 | reviewed | Testable |
1
|
2
| | The Patient Identifier Cross-reference Manager shall be capable of accepting attributes in the Resolve Duplicates message as specified in Table 3.44.4.2.2-1. | 209 | Section 3.44.4.2.3 | 5/29/19 1:43:49 PM by aberge |
|
| ITI44 | ITI44-28 | reviewed | Testable |
1
|
2
| | After the identifier references are replaced, the Patient Identifier Cross-reference Manager shall reapply its internal cross-referencing logic/ policies before providing the updated information via either the PIX Query or PIX Notification Transactions | 209 | Section 3.44.4.2.3 | 5/29/19 1:43:54 PM by aberge |
|
| ITI44 | ITI44-29 | reviewed | Testable |
1
|
2
| | When the Patient Identifier Cross-reference Manager receives the Resolve Duplicates message type of the Patient Identity Feed transaction, it shall cross-reference the patient identifiers provided in the wrapper and the payload of the message by replacing any references it is maintaining internally to the patient ID provided in the wrapper by the patient ID included in the payload. | 210 | Section 3.44.4.2. | 5/29/19 1:44:00 PM by aberge |
|
| ITI44 | ITI44-31 | reviewed | Testable |
1
|
2
| | The following WSDL naming conventions SHALL apply:
wsdl:definitions/@name="PIXManager":
merge message -> "PRPA_IN201304UV02_Message"
acknowledgement ->"MCCI_IN000002UV01_Message"
portType -> "PIXManager_PortType"
merge operation -> "PIXManager_PRPA_IN201304UV02"
SOAP 1.2 binding -> "PIXManager_Binding_Soap12"
SOAP 1.2 port -> "PIXManager_Port_Soap12" | 209 | Section 3.44.4.2.3.1 | 5/29/19 1:44:34 PM by aberge |
|
| ITI44 | ITI44-47 | reviewed | Testable |
1
|
3
| | 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. Audit messages produced by the Patient Identifier Cross-reference Manageractor shall comply with the definitin given in table 3.44.5.1.2 | 215 | Section 3.44.5.1.2 | 8/26/19 5:25:26 PM by aberge |
|