AssertionManagerGui

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

ITI45	ITI45-10	to be reviewed	Testable	0	2	The Patient Registry Query by Identifier message and response will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V.	224	Section 3.45.4.1.2.4	9/3/18 6:28:47 PM by Meenal T
ITI45	ITI45-11	to be reviewed	Testable	0	2	The following WSDL naming conventions SHALL apply: Query by Identifier -> "PRPA_IN201309UV02_Message" Query Response -> "PRPA_IN201310UV02_Message"	224	Section 3.45.4.1.2.4	9/3/18 6:28:47 PM by Meenal T
ITI45	ITI45-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	219	Section 3.45.3	9/3/18 6:28:48 PM by Meenal T
ITI45	ITI45-24	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 (either requested or available).	233	Section 3.45.4.2.4	9/3/18 6:28:49 PM by Meenal T
ITI45	ITI45-25	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.	233	Section 3.45.4.2.4	9/3/18 6:28:49 PM by Meenal T
ITI45	ITI45-26	to be reviewed	Testable	0	2	When grouped with ATNA Secure Node or Secure Application actors, this transaction is to be audited as Query Information event. Audit message produced by the Patient Identifier Cross-reference Consumer actor shall follow the rules defined in section 3.45.5.1.1	233	Section 3.45.5.1	9/3/18 6:28:49 PM by Meenal T
ITI45	ITI45-3	to be reviewed	Testable	0	2	A Patient Identifier Cross-reference Consumers need to get the patient identifier associated with a domain for which it needs patient related information shall trigger the request for corresponding patient identifiers message based on the following HL7 trigger event: Patient Registry Get Identifiers Query (PRPA_TE201309UV02)	220	Section 3.45.4.1.1	9/3/18 6:28:49 PM by Meenal T
ITI45	ITI45-4	to be reviewed	Testable	0	2	The Get Corresponding Identifiers transaction is initiated by the HL7 Patient Registry Query by Identifier (PRPA_MT201307UV02) message. The Patient Identifier Cross-reference Consumer shall generate the query message whenever it needs to obtain corresponding patient identifier(s) from other Patient Identification Domain(s).	220	Section 3.45.4.1.2	9/3/18 6:28:49 PM by Meenal T
ITI45	ITI45-5	to be reviewed	Testable	0	2	The components of the PRPA_MT201307UV02 message listed in section 3.45.4.1.2 are required.	220	Section 3.45.4.1.2	9/3/18 6:28:49 PM by Meenal T
PIXV3	PIXV3-1	to be reviewed	Testable	0	4	All the actors involved in the Patient Identity Cross-Referencing HL7 V3 (PIXV3) integration profile shall be grouped with the Time Client Actor.	234	Table 2-1	9/3/18 6:28:52 PM by Meenal T
PIXV3	PIXV3-10	to be reviewed	Testable	0	2	Patient Identifier Cross-reference Consumer may implement the PIXV3 Update Notification option	236	Table 23.2-1	9/3/18 6:28:52 PM by Meenal T
PIXV3	PIXV3-15	to be reviewed	Testable	0	4	The patient identifier SHALL be represented as a root and an extension, where the root is an appropriately assigned OID.	237	Section 23.5	9/3/18 6:28:52 PM by Meenal T
PIXV3	PIXV3-16	to be reviewed	Testable	0	4	All actors in PIXV3 should be grouped with an Audit Trail and Node Authentication (ATNA) Profile - Secure Node Actor or ATNA Secure Application Actor	238	Section 23.6	9/3/18 6:28:52 PM by Meenal T
PIXV3	PIXV3-17	to be reviewed	Testable	0	4	All actors in PIXV3 should be grouped with an XUA X-Service User or X-Service Provider Actor as appropriate	238	Section 23.6	9/3/18 6:28:52 PM by Meenal T
PIXV3	PIXV3-18	to be reviewed	Testable	0	4	All actors in PIXV3 should be grouped with the appropriate actor from the Enterprise User Authentication (EUA) Profile	238	Section 23.6	9/3/18 6:28:52 PM by Meenal T
PIXV3	PIXV3-4	to be reviewed	Testable	0	2	Patient Identifier Cross-reference Consumer actor which claims support of the Patient Identity Cross-Referencing HL7 V3 (PIXV3) integration profile may perform the PIXV3 Update Notification [ITI-46] transaction	235	Table 23.1-1	9/3/18 6:28:53 PM by Meenal T

to be reviewed

Testable

The Patient Registry Query by Identifier message and response will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V.

224

Section 3.45.4.1.2.4

9/3/18 6:28:47 PM by Meenal T

ITI45

ITI45-11

to be reviewed

Testable

0

2

The following WSDL naming conventions SHALL apply: Query by Identifier -> "PRPA_IN201309UV02_Message" Query Response -> "PRPA_IN201310UV02_Message"

224

Section 3.45.4.1.2.4

9/3/18 6:28:47 PM by Meenal T

ITI45

ITI45-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

219

Section 3.45.3

9/3/18 6:28:48 PM by Meenal T

ITI45

ITI45-24

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 (either requested or available).

233

Section 3.45.4.2.4

9/3/18 6:28:49 PM by Meenal T

ITI45

ITI45-25

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.

233

Section 3.45.4.2.4

9/3/18 6:28:49 PM by Meenal T

ITI45

ITI45-26

to be reviewed

Testable

0

2

When grouped with ATNA Secure Node or Secure Application actors, this transaction is to be audited as Query Information event. Audit message produced by the Patient Identifier Cross-reference Consumer actor shall follow the rules defined in section 3.45.5.1.1

233

Section 3.45.5.1

9/3/18 6:28:49 PM by Meenal T

ITI45

ITI45-3

to be reviewed

Testable

0

2

A Patient Identifier Cross-reference Consumers need to get the patient identifier associated with a domain for which it needs patient related information shall trigger the request for corresponding patient identifiers message based on the following HL7 trigger event: Patient Registry Get Identifiers Query (PRPA_TE201309UV02)

220

Section 3.45.4.1.1

9/3/18 6:28:49 PM by Meenal T

ITI45

ITI45-4

to be reviewed

Testable

0

2

The Get Corresponding Identifiers transaction is initiated by the HL7 Patient Registry Query by Identifier (PRPA_MT201307UV02) message. The Patient Identifier Cross-reference Consumer shall generate the query message whenever it needs to obtain corresponding patient identifier(s) from other Patient Identification Domain(s).

220

Section 3.45.4.1.2

9/3/18 6:28:49 PM by Meenal T

ITI45

ITI45-5

to be reviewed

Testable

0

2

The components of the PRPA_MT201307UV02 message listed in section 3.45.4.1.2 are required.

220

Section 3.45.4.1.2

9/3/18 6:28:49 PM by Meenal T

PIXV3

PIXV3-1

to be reviewed

Testable

0

4

All the actors involved in the Patient Identity Cross-Referencing HL7 V3 (PIXV3) integration profile shall be grouped with the Time Client Actor.

234

Table 2-1

9/3/18 6:28:52 PM by Meenal T

PIXV3

PIXV3-10

to be reviewed

Testable

0

2

Patient Identifier Cross-reference Consumer may implement the PIXV3 Update Notification option

236

Table 23.2-1

9/3/18 6:28:52 PM by Meenal T

PIXV3

PIXV3-15

to be reviewed

Testable

0

4

The patient identifier SHALL be represented as a root and an extension, where the root is an appropriately assigned OID.

237

Section 23.5

9/3/18 6:28:52 PM by Meenal T

PIXV3

PIXV3-16

to be reviewed

Testable

0

4

All actors in PIXV3 should be grouped with an Audit Trail and Node Authentication (ATNA) Profile - Secure Node Actor or ATNA Secure Application Actor

238

Section 23.6

9/3/18 6:28:52 PM by Meenal T

PIXV3

PIXV3-17

to be reviewed

Testable

0

4

All actors in PIXV3 should be grouped with an XUA X-Service User or X-Service Provider Actor as appropriate

238

Section 23.6

9/3/18 6:28:52 PM by Meenal T

PIXV3

PIXV3-18

to be reviewed

Testable

0

4

All actors in PIXV3 should be grouped with the appropriate actor from the Enterprise User Authentication (EUA) Profile

238

Section 23.6

9/3/18 6:28:52 PM by Meenal T

PIXV3

PIXV3-4

to be reviewed

Testable

0

2

Patient Identifier Cross-reference Consumer actor which claims support of the Patient Identity Cross-Referencing HL7 V3 (PIXV3) integration profile may perform the PIXV3 Update Notification [ITI-46] transaction

235

Table 23.1-1

9/3/18 6:28:53 PM by Meenal T

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

Assertion

Applies to

Coverage