Search Criteria : 16 assertions found for this search Review filtered assertions

Assertion

Applies to

Applied to
Not applied to

Coverage

Covered by
Not covered by
Id scheme
Assertion id
Status
Testable?
#Coverage
#Applies to
Comment
Predicate
Page
Tags
Last changed
Actions
ITI44ITI44-12reviewedTestable 1 2 The Patient Identifier Cross-reference Manager shall be capable of accepting attributes specified in Table 3.44.4.1.2-1 201Section 3.44.4.1.35/29/19 1:42:28 PM by aberge
ITI44ITI44-13validatedTestable 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). 201Section 3.44.4.1.35/29/19 1:42:41 PM by aberge
ITI44ITI44-14reviewedTestable 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" 202Section 3.44.4.1.3.15/29/19 1:42:49 PM by aberge
ITI44ITI44-24reviewedTestable 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 O205Section 3.44.4.2.25/29/19 1:43:14 PM by aberge
ITI44ITI44-27reviewedTestable 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. 209Section 3.44.4.2.35/29/19 1:43:49 PM by aberge
ITI44ITI44-28reviewedTestable 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 Transactions209Section 3.44.4.2.35/29/19 1:43:54 PM by aberge
ITI44ITI44-29reviewedTestable 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. 210Section 3.44.4.2.5/29/19 1:44:00 PM by aberge
ITI44ITI44-31reviewedTestable 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"209Section 3.44.4.2.3.15/29/19 1:44:34 PM by aberge
ITI44ITI44-4to be reviewedTestable 0 2 The Patient Identifier Cross-reference Manager shall only perform cross-referencing logic on messages received from Patient Identity Source Actors 193Section 3.44.4.1.15/2/19 4:40:23 PM by wbars
ITI44ITI44-47reviewedTestable 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.2215Section 3.44.5.1.28/26/19 5:25:26 PM by aberge
ITI44ITI44-9reviewedTestable 1 3 Each message (PRPA_MT201301UV02 and PRPA_MT201302UV02) shall be acknowledged by the HL7 v3 Accept Acknowledgement (MCCI_MT000200UV01), which is described in ITI TF-2x: Appendix O. 194Section 3.44.4.1.25/29/19 1:46:55 PM by aberge
PIXV3PIXV3-1reviewedTestable 1 4 All the actors involved in the Patient Identity Cross-Referencing HL7 V3 (PIXV3) integration profile shall be grouped with the Time Client Actor.235Table 23.68/26/19 5:25:26 PM by wbars
PIXV3PIXV3-15to be reviewedTestable 0 4 The patient identifier SHALL be represented as a root and an extension, where the root is an appropriately assigned OID. 234Section 23.55/2/19 11:31:35 AM by wbars
PIXV3PIXV3-5reviewedTestable 0 2 Patient Identifier Cross-reference Manager actor which claims support of the Patient Identity Cross-Referencing HL7 V3 (PIXV3) integration profile shall perform the Patient Identity Feed HL7V3 [ITI-44] transaction232Table 23.1-15/2/19 11:25:56 AM by wbars
PIXV3PIXV3-6reviewedTestable 0 2 Patient Identifier Cross-reference Manager actor which claims support of the Patient Identity Cross-Referencing HL7 V3 (PIXV3) integration profile shall perform the PIXV3 Query [ITI-45] transaction232Table 23.1-15/2/19 11:28:16 AM by wbars
PIXV3PIXV3-7reviewedTestable 1 2 Patient Identifier Cross-reference Manager actor which claims support of the Patient Identity Cross-Referencing HL7 V3 (PIXV3) integration profile shall perform the PIXV3 Update Notification [ITI-46] transaction232Table 23.1-15/29/19 1:52:33 PM by aberge