AssertionManagerGui

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

ITI44	ITI44-10	to be reviewed	Testable	0	2	The Patient Registry Record Added/Revised messages will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V.	202	Section 3.44.4.1.2.4	9/3/18 6:10:53 PM by Jean-François Labbe
ITI44	ITI44-11	to be reviewed	Testable	0	2	The following WSDL naming conventions SHALL apply for transmission of the Patient Registry Record Added/Revised messages : add message -> "PRPA_IN201301UV02_Message" revise message -> "PRPA_IN201302UV02_Message" acknowledgement -> "MCCI_IN000002UV01_Message"	202	Section 3.44.4.1.2.4	9/3/18 6:10:53 PM by Jean-François Labbe
ITI44	ITI44-22	to be reviewed	Testable	0	2	The message shall be generated by the system (Patient Identity Source) that performs the update whenever two patient records are found to reference the same person.	207	Section 3.44.4.2.2	9/3/18 6:10:55 PM by Jean-François Labbe
ITI44	ITI44-23	to be reviewed	Testable	0	2	The Patient Registry Duplicates Resolved interaction is carried out by the HL7 v3 Patient Demographics message (PRPA_MT201303UV02) .	207	Section 3.44.4.2.2	9/3/18 6:10:55 PM by Jean-François Labbe
ITI44	ITI44-25	to be reviewed	Testable	0	3	The Patient Registry Resolve Duplicates message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V.	210	Section 3.44.4.2.2.4	9/3/18 6:10:56 PM by Jean-François Labbe
ITI44	ITI44-26	to be reviewed	Testable	0	2	The following WSDL naming conventions SHALL apply for transmitting the Patient Registry Resolve Duplicates message: "resolve duplicates" message -> "PRPA_IN201304UV02_Message" Acknowledgement -> "MCCI_IN000002UV01_Message"	210	Section 3.44.4.2.2.4	9/3/18 6:10:56 PM by Jean-François Labbe
ITI44	ITI44-3	to be reviewed	Testable	0	2	Patient Registry Record Revised (PRPA_TE201302UV02) event from a Patient Identity Source shall trigger the Revise Patient Record message.	195	Section 3.44.4.1.1	9/3/18 6:10:57 PM by Jean-François Labbe
ITI44	ITI44-46	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. Audit messages produced by the Patient Identity Source actor shall comply with the definitin given in table 3.44.5.1.1	216	Section 3.44.5.1.1	9/3/18 6:10:59 PM by Jean-François Labbe
ITI44	ITI44-6	to be reviewed	Testable	0	2	A given Patient Identity Source Actor may serve more than one Patient Identifier Domain.	195	Section 3.44.4.1.1	9/3/18 6:11:00 PM by Jean-François Labbe
ITI44	ITI44-7	to be reviewed	Testable	0	2	The components of the PRPA_MT201301UV02 and PRPA_MT201302UV02 messages listed in section 3.44.4.1.2 are required.	196	Section 3.44.4.1.2	9/3/18 6:11:00 PM by Jean-François Labbe
ITI44	ITI44-8	to be reviewed	Testable	0	2	The Patient Identity Feed transaction is carried out by the HL7 v3 Patient Activate (PRPA_MT201301UV02) and Patient Revise (PRPA_MT201302UV02) messages, as defined in the subsequent sections. The Patient Identity Source shall generate the message whenever a patient is registered or when some piece of patient demographic data changes.	196	Section 3.44.4.1.2	9/3/18 6:11:00 PM by Jean-François Labbe
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-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-2	to be reviewed	Testable	0	2	Patient Identity Source actor which claims support of the Patient Identity Cross-Referencing HL7 V3 (PIXV3) integration profile shall perform the Patient Identity Feed HL7V3 [ITI-44] transaction	235	Table 23.1-1	9/3/18 6:28:53 PM by Meenal T
PIXV3	PIXV3-8	to be reviewed	Testable	0	2	Patient Identity Source actors may implement the Pediatric Demographics option	236	Table 23.2-1	9/3/18 6:28:53 PM by Meenal T

to be reviewed

Testable

The Patient Registry Record Added/Revised messages will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V.

202

Section 3.44.4.1.2.4

9/3/18 6:10:53 PM by Jean-François Labbe

ITI44

ITI44-11

to be reviewed

Testable

0

2

The following WSDL naming conventions SHALL apply for transmission of the Patient Registry Record Added/Revised messages : add message -> "PRPA_IN201301UV02_Message" revise message -> "PRPA_IN201302UV02_Message" acknowledgement -> "MCCI_IN000002UV01_Message"

202

Section 3.44.4.1.2.4

9/3/18 6:10:53 PM by Jean-François Labbe

ITI44

ITI44-22

to be reviewed

Testable

0

2

The message shall be generated by the system (Patient Identity Source) that performs the update whenever two patient records are found to reference the same person.

207

Section 3.44.4.2.2

9/3/18 6:10:55 PM by Jean-François Labbe

ITI44

ITI44-23

to be reviewed

Testable

0

2

The Patient Registry Duplicates Resolved interaction is carried out by the HL7 v3 Patient Demographics message (PRPA_MT201303UV02) .

207

Section 3.44.4.2.2

9/3/18 6:10:55 PM by Jean-François Labbe

ITI44

ITI44-25

to be reviewed

Testable

0

3

The Patient Registry Resolve Duplicates message will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V.

210

Section 3.44.4.2.2.4

9/3/18 6:10:56 PM by Jean-François Labbe

ITI44

ITI44-26

to be reviewed

Testable

0

2

The following WSDL naming conventions SHALL apply for transmitting the Patient Registry Resolve Duplicates message: "resolve duplicates" message -> "PRPA_IN201304UV02_Message" Acknowledgement -> "MCCI_IN000002UV01_Message"

210

Section 3.44.4.2.2.4

9/3/18 6:10:56 PM by Jean-François Labbe

ITI44

ITI44-3

to be reviewed

Testable

0

2

Patient Registry Record Revised (PRPA_TE201302UV02) event from a Patient Identity Source shall trigger the Revise Patient Record message.

195

Section 3.44.4.1.1

9/3/18 6:10:57 PM by Jean-François Labbe

ITI44

ITI44-46

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. Audit messages produced by the Patient Identity Source actor shall comply with the definitin given in table 3.44.5.1.1

216

Section 3.44.5.1.1

9/3/18 6:10:59 PM by Jean-François Labbe

ITI44

ITI44-6

to be reviewed

Testable

0

2

A given Patient Identity Source Actor may serve more than one Patient Identifier Domain.

195

Section 3.44.4.1.1

9/3/18 6:11:00 PM by Jean-François Labbe

ITI44

ITI44-7

to be reviewed

Testable

0

2

The components of the PRPA_MT201301UV02 and PRPA_MT201302UV02 messages listed in section 3.44.4.1.2 are required.

196

Section 3.44.4.1.2

9/3/18 6:11:00 PM by Jean-François Labbe

ITI44

ITI44-8

to be reviewed

Testable

0

2

The Patient Identity Feed transaction is carried out by the HL7 v3 Patient Activate (PRPA_MT201301UV02) and Patient Revise (PRPA_MT201302UV02) messages, as defined in the subsequent sections. The Patient Identity Source shall generate the message whenever a patient is registered or when some piece of patient demographic data changes.

196

Section 3.44.4.1.2

9/3/18 6:11:00 PM by Jean-François Labbe

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

to be reviewed

Testable

0

2

Patient Identity Source actor which claims support of the Patient Identity Cross-Referencing HL7 V3 (PIXV3) integration profile shall perform the Patient Identity Feed HL7V3 [ITI-44] transaction

235

Table 23.1-1

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

PIXV3

PIXV3-8

to be reviewed

Testable

0

2

Patient Identity Source actors may implement the Pediatric Demographics option

236

Table 23.2-1

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

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

Assertion

Applies to

Coverage