AssertionManagerGui

Id scheme	Assertion id	Status	Testable?	#Coverage	#Applies to	Predicate	Page	Tags	Last changed
1 2
ITI20_RESTful	ITI20_RESTful-007		Not testable	0	0	For the Resource received, the Audit Record Repository MAY discard the Resource as irrelevant	31	Section 3.20.4.2.3	5/12/22 3:29:02 PM by vhofman
ITI20_RESTful	ITI20_RESTful-008		Not testable	0	0	For the Resource received, the Audit Record Repository MAY retain the Resource in an internal data store.	31	Section 3.20.4.2.3	5/12/22 3:29:07 PM by vhofman
ITI20_RESTful	ITI20_RESTful-009		Not testable	0	0	For the Resource received, the Audit Record Repository MAY perform other processing on the Resource.	31	Section 3.20.4.2.3	5/12/22 3:29:12 PM by vhofman
ITI20_RESTful	ITI20_RESTful-011		Testable	0	0	An Audit Record Repository that needs to store a received AuditEvent Resource as a DICOM Audit Message CAN do the transformation from the FHIR Resource to a DICOM message according to the requirements defined in Table 3.20.4.2.2.1-1.	32	Section 3.20.4.2.3	6/27/22 3:54:39 PM by vhofman
ITI20_RESTful	ITI20_RESTful-013		Testable	0	0	Events SHALL not be available for further search via Retrieve Syslog Events [ITI-82] transaction.	32	Section 3.20.4.2.3	5/2/22 8:46:15 AM by vhofman
ITI20_RESTful	ITI20_RESTful-016		Testable	0	0	An Audit Record Forwarder that will forward a received AuditEvent Resource using the Audit Event message (DICOM audit event via syslog protocol) CAN do the transformation from the FHIR Resource to a DICOM message according to the requirements defined in Table 3.20.4.2.2.1-1.	32	Section 3.20.4.2.3	5/2/22 8:46:15 AM by vhofman
ITI20_RESTful	ITI20_RESTful-018		Testable	0	0	An Audit Record Forwarder or an actor that is grouped with Secure Node or Secure Application SHALL issue an HTTP request according to requirements defined in the FHIR specification for batch interaction (see https://www.hl7.org/fhir/R4/http.html#transaction).	33	Section 3.20.4.2.3	6/27/22 3:54:39 PM by vhofman
ITI20_RESTful	ITI20_RESTful-026	to be reviewed	Not testable	0	0	For each Resource received in the Bundle, the Audit Record Repository MAY discard the Resource as irrelevant.	34	Section 3.20.4.4.3	5/12/22 3:29:27 PM by vhofman
ITI20_RESTful	ITI20_RESTful-027	to be reviewed	Not testable	0	0	For each Resource received in the Bundle, the Audit Record Repository MAY retain the Resource in an internal data store.	34	Section 3.20.4.4.3	5/12/22 3:29:35 PM by vhofman
ITI20_RESTful	ITI20_RESTful-028	to be reviewed	Not testable	0	0	For each Resource received in the Bundle, the Audit Record Repository MAY perform other processing on the Resource.	34	Section 3.20.4.4.3	5/12/22 3:29:40 PM by vhofman
ITI20_RESTful	ITI20_RESTful-030	to be reviewed	Testable	0	0	An Audit Record Repository that needs to store a received AuditEvent Resource as a DICOM Audit Message CAN do the transformation from the FHIR Resource to a DICOM message according to the requirements defined in Table 3.20.4.2.2.1-1.	34	Section 3.20.4.4.3	6/27/22 3:54:39 PM by vhofman
ITI20_RESTful	ITI20_RESTful-033	to be reviewed	Testable	0	0	When the Audit Record Repository is grouped with an Audit Record Forwarder, the Audit Record Forwarder SHALL apply filtering rules to all AuditEvent Resources received by the Audit Record Repository.	34	Section 3.20.4.4.3	5/12/22 8:32:40 AM by vhofman
ITI20_RESTful	ITI20_RESTful-034	to be reviewed	Testable	0	0	When the Audit Record Repository is grouped with an Audit Record Forwarder, the Audit Record Forwarder SHALL forward all AuditEvent Resources that match filters to their configured destinations.	34	Section 3.20.4.4.3	5/12/22 8:32:46 AM by vhofman
ITI20_RESTful	ITI20_RESTful-035	to be reviewed	Testable	0	0	An Audit Record Forwarder that needs to forward a received AuditEvent Resource using the Audit Event message CAN do the transformation from the FHIR Resource to a DICOM message according to the requirements defined in Table 3.20.4.2.2.1-1.	35	Section 3.20.4.4.3	6/27/22 3:54:39 PM by vhofman
ITI20_RESTful	ITI20_RESTful-039	to be reviewed	Testable	0	0	Each entry element SHALL contain a response element with an HTTP Status Code which details the outcome of processing of the request entry.	35	Section 3.20.4.5.2	6/27/22 3:54:39 PM by vhofman
ITI20_RESTful	ITI20_RESTful-041	to delete	Testable	0	0	If no Prefer header is specified in the request the server SHOULD respond as if it is set to 840 return=minimal; see https://www.hl7.org/fhir/R4/http.html#ops.	35	Section 3.20.4.5.2	6/27/22 3:54:39 PM by vhofman
ITI20_RESTful	ITI20_RESTful-045	to be reviewed	Testable	0	0	The use of the TLS or HTTPS transport mechanism is recommended because the audit event 855 messages often contain PHI or other sensitive information. See Section 3.20.4.1.2.1.	35	Section 3.20.5	6/27/22 3:54:39 PM by vhofman
ITI20_RESTful	ITI20_RESTful-046	to be reviewed	Testable	0	0	The use of the TLS transport mechanism is not always required because there are other means of protection that MAY be more appropriate in some situations.	35	Section 3.20.5	6/27/22 3:54:39 PM by vhofman
ITI20_RESTful	ITI20_RESTful-047	to be reviewed	Not testable	0	0	The decision to use the UDP transport mechanism SHOULD be based upon a security and privacy risk analysis.	35	Section 3.20.5	6/27/22 3:54:39 PM by vhofman
ITI20_RESTful	ITI20_RESTful-048	to be reviewed	Not testable	0	0	The data store within the Audit Record Repository MAY contain sensitive information, and the Audit Record Repository analysis facilities MAY allow sensitive queries.	35	Section 3.20.5	6/27/22 3:54:39 PM by vhofman

ITI20_RESTful

ITI20_RESTful-007

Not testable

0

For the Resource received, the Audit Record Repository MAY discard the Resource as irrelevant

31

Section 3.20.4.2.3

5/12/22 3:29:02 PM by vhofman

ITI20_RESTful

ITI20_RESTful-008

Not testable

0

For the Resource received, the Audit Record Repository MAY retain the Resource in an internal data store.

31

Section 3.20.4.2.3

5/12/22 3:29:07 PM by vhofman

ITI20_RESTful

ITI20_RESTful-009

Not testable

0

For the Resource received, the Audit Record Repository MAY perform other processing on the Resource.

31

Section 3.20.4.2.3

5/12/22 3:29:12 PM by vhofman

ITI20_RESTful

ITI20_RESTful-011

Testable

0

An Audit Record Repository that needs to store a received AuditEvent Resource as a DICOM Audit Message CAN do the transformation from the FHIR Resource to a DICOM message according to the requirements defined in Table 3.20.4.2.2.1-1.

32

Section 3.20.4.2.3

6/27/22 3:54:39 PM by vhofman

ITI20_RESTful

ITI20_RESTful-013

Testable

0

Events SHALL not be available for further search via Retrieve Syslog Events [ITI-82] transaction.

32

Section 3.20.4.2.3

5/2/22 8:46:15 AM by vhofman

ITI20_RESTful

ITI20_RESTful-016

Testable

0

An Audit Record Forwarder that will forward a received AuditEvent Resource using the Audit Event message (DICOM audit event via syslog protocol) CAN do the transformation from the FHIR Resource to a DICOM message according to the requirements defined in Table 3.20.4.2.2.1-1.

32

Section 3.20.4.2.3

5/2/22 8:46:15 AM by vhofman

ITI20_RESTful

ITI20_RESTful-018

Testable

0

An Audit Record Forwarder or an actor that is grouped with Secure Node or Secure Application SHALL issue an HTTP request according to requirements defined in the FHIR specification for batch interaction (see https://www.hl7.org/fhir/R4/http.html#transaction).

33

Section 3.20.4.2.3

6/27/22 3:54:39 PM by vhofman

ITI20_RESTful

ITI20_RESTful-026

to be reviewed

Not testable

0

For each Resource received in the Bundle, the Audit Record Repository MAY discard the Resource as irrelevant.

34

Section 3.20.4.4.3

5/12/22 3:29:27 PM by vhofman

ITI20_RESTful

ITI20_RESTful-027

to be reviewed

Not testable

0

For each Resource received in the Bundle, the Audit Record Repository MAY retain the Resource in an internal data store.

34

Section 3.20.4.4.3

5/12/22 3:29:35 PM by vhofman

ITI20_RESTful

ITI20_RESTful-028

to be reviewed

Not testable

0

For each Resource received in the Bundle, the Audit Record Repository MAY perform other processing on the Resource.

34

Section 3.20.4.4.3

5/12/22 3:29:40 PM by vhofman

ITI20_RESTful

ITI20_RESTful-030

to be reviewed

Testable

0

An Audit Record Repository that needs to store a received AuditEvent Resource as a DICOM Audit Message CAN do the transformation from the FHIR Resource to a DICOM message according to the requirements defined in Table 3.20.4.2.2.1-1.

34

Section 3.20.4.4.3

6/27/22 3:54:39 PM by vhofman

ITI20_RESTful

ITI20_RESTful-033

to be reviewed

Testable

0

When the Audit Record Repository is grouped with an Audit Record Forwarder, the Audit Record Forwarder SHALL apply filtering rules to all AuditEvent Resources received by the Audit Record Repository.

34

Section 3.20.4.4.3

5/12/22 8:32:40 AM by vhofman

ITI20_RESTful

ITI20_RESTful-034

to be reviewed

Testable

0

When the Audit Record Repository is grouped with an Audit Record Forwarder, the Audit Record Forwarder SHALL forward all AuditEvent Resources that match filters to their configured destinations.

34

Section 3.20.4.4.3

5/12/22 8:32:46 AM by vhofman

ITI20_RESTful

ITI20_RESTful-035

to be reviewed

Testable

0

An Audit Record Forwarder that needs to forward a received AuditEvent Resource using the Audit Event message CAN do the transformation from the FHIR Resource to a DICOM message according to the requirements defined in Table 3.20.4.2.2.1-1.

35

Section 3.20.4.4.3

6/27/22 3:54:39 PM by vhofman

ITI20_RESTful

ITI20_RESTful-039

to be reviewed

Testable

0

Each entry element SHALL contain a response element with an HTTP Status Code which details the outcome of processing of the request entry.

35

Section 3.20.4.5.2

6/27/22 3:54:39 PM by vhofman

ITI20_RESTful

ITI20_RESTful-041

to delete

Testable

0

If no Prefer header is specified in the request the server SHOULD respond as if it is set to 840 return=minimal; see https://www.hl7.org/fhir/R4/http.html#ops.

35

Section 3.20.4.5.2

6/27/22 3:54:39 PM by vhofman

ITI20_RESTful

ITI20_RESTful-045

to be reviewed

Testable

0

The use of the TLS or HTTPS transport mechanism is recommended because the audit event 855 messages often contain PHI or other sensitive information. See Section 3.20.4.1.2.1.

35

Section 3.20.5

6/27/22 3:54:39 PM by vhofman

ITI20_RESTful

ITI20_RESTful-046

to be reviewed

Testable

0

The use of the TLS transport mechanism is not always required because there are other means of protection that MAY be more appropriate in some situations.

35

Section 3.20.5

6/27/22 3:54:39 PM by vhofman

ITI20_RESTful

ITI20_RESTful-047

to be reviewed

Not testable

0

The decision to use the UDP transport mechanism SHOULD be based upon a security and privacy risk analysis.

35

Section 3.20.5

6/27/22 3:54:39 PM by vhofman

ITI20_RESTful

ITI20_RESTful-048

to be reviewed

Not testable

0

The data store within the Audit Record Repository MAY contain sensitive information, and the Audit Record Repository analysis facilities MAY allow sensitive queries.

35

Section 3.20.5

6/27/22 3:54:39 PM by vhofman

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

Assertion

Applies to

Coverage