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


Applies to

Applied to
Not applied to


Covered by
Not covered by
Id scheme
Assertion id
#Applies to
Last changed
ITI20ITI20-1reviewedTestable 0 0 The Audit Record Repository shall accept the Audit Record message.138Section 3.20.24/30/19 4:55:36 PM by NicolasBailliet
ITI20ITI20-10reviewedTestable 0 0 The syslog message shall be created and transmitted as described in RFC 5424.139Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-11reviewedTestable 0 0 Audit repositories must accept audit messages encoded with UTF-8 and store them without damage.144Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-12reviewedTestable 0 0 To perform the calculation of the PRI field in the syslog message, the Facility value of 10 (security/authorization messages) shall be use. (see RFC 5424)144Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-13reviewedTestable 0 0 To perform the calculation of the PRI field in the syslog message, the severity values of 5 (normal but significant) or 4 (warning condition) should be used. (see RFC 5424)144Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-14reviewedTestable 0 0 Audit repositories shall be prepared to deal appropriately with any incoming PRI value.144Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-15reviewedTestable 0 0 The MSGID field in the HEADER of the SYSLOG-MSG shall be set to “IHE+RFC-3881” (minus the quotes).144Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-16reviewedTestable 0 0 The MSG field of the SYSLOG-MSG shall be present and shall be an XML structure following the RFC 3881 format.144Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-17reviewedTestable 0 0 Applications using Reliable Syslog should switch to transmission of syslog messages over TLS.145Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-18reviewedTestable 0 0 When transmission of Syslog Messages over UDP (RFC 5426) with the Syslog Protocol (RFC 5424) occurs, long messages may be truncated. If so, the Audit Repository must correct the message by closing the trucated XML elements.145Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-19reviewedTestable 0 0 Because of the potential for truncated messages and other security concerns with Syslog Messages over UDP, the transmission of syslog messages over TLS may be preferred.145Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-20reviewedTestable 0 0 About Transmission of Syslog Messages over TLS (RFC5425) with The Syslog Protocol (RFC5424), it is recommended to use TLS version 1.2.145Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-22reviewedTestable 0 0 For the ParticipantObjectIDTypeCode element, and when using the values specified in RFC-3881, IHE actors SHALL specify the corresponding description from RFC-3881 in the originalText attribute and "RFC-3881" in the codeSystemName attribute.148Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-23reviewedTestable 0 0 A Secure Node Actor shall be able to detect events that are defined by the DICOM standard in PS 3.16 - 2011, CID 400, and generate Record Audit Event transactions that conform to the DICOM standard when these events take place.147Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-24reviewedTestable 0 0 The additional IHE defined events Health Services Provision Event, Medication Event, Patient Care Resource Assignment, Patient Care Episode and Patient Care Protocol (enumerated in ITI TF-2a: shall be used for their defined purpose.140Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-26reviewedTestable 0 0 In cases where there is an event that applies to more than one patient, there shall be a separate audit message for each patient.147Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-27reviewedTestable 0 0 Events that do not correspond to DICOM events or IHE Extension events can be reported.144Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-28reviewedTestable 0 0 Reported events that do not correspond to DICOM events or IHE Extension events shall comply with the DICOM schema.147Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-29reviewedTestable 0 0 Neither ATNA Profile, DICOM, nor RFC-3881 restrict private extensions to the schema however any private extensions shall comply with the W3C XML encoding rules for the use of schemas, namespaces, etc.147Section 4:55:36 PM by NicolasBailliet
ITI20ITI20-3reviewedTestable 0 0 Except for the scope of an upgrade to DICOM Audit Message Standard with IHE Extensions, it is not recommended that Radiology devices use the deprecated IHE Provisional Audit Message Format.140Section 4:55:36 PM by NicolasBailliet