AssertionManagerGui

Id scheme	Assertion id	Status	Testable?	#Coverage	#Applies to	Predicate	Page	Tags	Last changed

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.	241	Section 3.46.4.1.3	5/2/19 5:11:38 PM by wbars
ITI46	ITI46-17	to be reviewed	Testable	1	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	241	Section 3.46.4.1.3	6/6/19 9:05:20 AM by aberge
ITI46	ITI46-18	to be reviewed	Testable	1	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"	241	Section 3.46.4.1.3.1	6/6/19 9:05:23 AM by aberge
ITI46	ITI46-2	to be reviewed	Testable	1	3	Implementers of this transaction shall comply with all requirements described in ITI TF-2x: Appendix V Web Services for IHE Transactions.	235	Section 3.46.3	6/6/19 9:05:36 AM by aberge
ITI46	ITI46-20	to be reviewed	Testable	1	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	243	Section 3.46.5.1	8/26/19 3:29:41 PM by aberge
ITI46	ITI46-21	to be reviewed	Testable	1	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	241	Section 3.46.4.1.3	6/6/19 9:05:45 AM by aberge
ITI46	ITI46-7	to be reviewed	Testable	1	2	Each message shall be acknowledged by the HL7 V3 Accept Acknowledgement (MCCI_MT000200UV01), which is described in ITI TF-2x: Appendix O	236	Section 3.46.4.1.2	6/6/19 9:05:54 AM by aberge

to be reviewed

Testable

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.

241

Section 3.46.4.1.3

5/2/19 5:11:38 PM by wbars

ITI46

ITI46-17

to be reviewed

Testable

1

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

241

Section 3.46.4.1.3

6/6/19 9:05:20 AM by aberge

ITI46

ITI46-18

to be reviewed

Testable

1

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"

241

Section 3.46.4.1.3.1

6/6/19 9:05:23 AM by aberge

ITI46

ITI46-2

to be reviewed

Testable

1

3

Implementers of this transaction shall comply with all requirements described in ITI TF-2x: Appendix V Web Services for IHE Transactions.

235

Section 3.46.3

6/6/19 9:05:36 AM by aberge

ITI46

ITI46-20

to be reviewed

Testable

1

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

243

Section 3.46.5.1

8/26/19 3:29:41 PM by aberge

ITI46

ITI46-21

to be reviewed

Testable

1

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

241

Section 3.46.4.1.3

6/6/19 9:05:45 AM by aberge

ITI46

ITI46-7

to be reviewed

Testable

1

2

Each message shall be acknowledged by the HL7 V3 Accept Acknowledgement (MCCI_MT000200UV01), which is described in ITI TF-2x: Appendix O

236

Section 3.46.4.1.2

6/6/19 9:05:54 AM by aberge

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

Assertion

Applies to

Coverage