| ATNA | ATNA-10 | | Testable |
0
|
2
| | Audit Record Repository actor which claims support of the Audit Trail and Node Authentication (ATNA) integration profile shall support the Record Audit Event [ITI-20] transaction. | 69 | Table 9.1-1 | 5/22/23 2:18:09 PM by testAuto |
|
| ATNA | ATNA-12 | | Testable |
0
|
2
| | Secure Node actor which claims support for the Audit Trail and Node Authentication (ATNA) integration profile shall support the Record Audit Event [ITI-20] transaction | 69 | Table 9.1-1 | 6/27/22 4:37:57 PM by testAuto |
|
| ATNA | ATNA-15 | | Testable |
0
|
2
| | Secure Application actor which claims support for the Audit Trail and Node Authentication (ATNA) integration profile may perform the Maitain Time [ITI-1] transaction | 72 | Table 9.3-1 | 7/9/24 2:31:02 PM by dgraveto |
|
| ATNA | ATNA-16 | | Testable |
0
|
2
| see previous comment on ITI-19 | Secure Application actor which claims support for the Audit Trail and Node Authentication (ATNA) integration profile may perform the Record Audit Event [ITI-20] transaction | 69 | Table 9.1-1 | 6/29/22 11:49:04 AM by testAuto |
|
| ATNA | ATNA-21 | | Testable |
0
|
2
| | The Audit Repository shall support any IHE-specified audit message format, when sent over one of those transport mechanisms. Note that new applications domains may have their own extended vocabularies in addition to the DICOM and IHE vocabularies. This also means that an ATNA Audit Repository is also automatically a Radiology Basic Security Profile Audit Repository because it must support the IHE Provisional Message format and it must support the BSD syslog protocol | 70 | Section 9.1.1.3 | 6/29/22 2:22:50 PM by testAuto |
|
| ATNA | ATNA-3 | | Testable |
0
|
2
| | A Secure Node Actor shall be configurable to support both connection authentication and physically secured networks | 72 | Section 9.4 | 4/30/19 4:13:19 PM by NicolasBailliet |
|
| ATNA | ATNA-4 | | Testable |
0
|
4
| | The mechanism for logging audit record messages to the audit record repository shall be either Transmission of Syslog Messages over UDP (RFC5426) with The Syslog Protocol (RFC5424) which formalizes and obsoletes Syslog (RFC-3164), either 2) Transmission of Syslog Messages over TLS (RFC5425) with The Syslog Protocol (RFC5424) which formalizes sending syslog messages over a streaming protocol protectable by TLS. | 72 | Section 9.3 | 4/30/19 4:13:19 PM by NicolasBailliet |
|
| ATNA | ATNA-6 | | Testable |
0
|
4
| | A means must be provided to upload the required certificates to the implementation, e.g., via floppy disk or file transfer via network. | 72 | Section 9.4 | 4/30/19 4:13:19 PM by NicolasBailliet |
|
| ATNA | ATNA-7 | | Testable |
0
|
2
| I don't know what this assertion means. | When an IHE profile requires a grouping of an actor with either Secure Node or Secure Application, then the ATNA requirements apply to all actors in the implementation. | 72 | Section 9.3.1 | 4/30/19 4:13:19 PM by NicolasBailliet |
|
| ATNA | ATNA-8 | | Testable |
0
|
2
| | When an implementation chooses to support this Integration Profile for an actor, it is required that all IHE actors and any other activities in this implementation support the Audit Trail and Node Authentication Integration Profile. | 72 | Section 9.4 | 4/30/19 4:13:19 PM by NicolasBailliet |
|
| CH-ATNA | CH-ATNA-010 | to be reviewed | Not testable |
0
|
1
| | For audit records generated by IHE and EPR actors, in all elements of the type CodedValueType: whenever the represented code belongs to the Swiss Metadata Value Set, the attribute @codeSystemName shall contain the OID of the corresponding code system instead of its symbolic name. For all other codes, this requirement is optional. | 8 | Section 1.5 | 10/1/21 3:05:11 PM by vhofman |
|
| CH-HPD | CH-HPD-001 | reviewed | Testable |
0
|
4
| | the Actor must implement the CH:PIDD request validating PIDD.xsd (see Section 1.11.3.1 Provider Information Directory) | 50 | Section 1.11.3 | 3/15/24 2:33:35 PM by vhofman |
|
| CH-HPD | CH-HPD-002 | reviewed | Testable |
0
|
3
| | the Actor must implement the CH:PIDD response validating PIDD.xsd (see Section 1.11.3.2 Provider Information Consumer) | 50 | Section 1.11.3 | 3/15/24 2:33:35 PM by vhofman |
|
| CH-PDQ | CH-PDQ-015 | reviewed | Testable |
0
|
1
| | The different return cases should be handled equivalent to the XCPD cases in IHE ITI TF-2b, chapter 3.55.4.2.3 Expected Actions (see Section 1.9.2.1.1 Special handling for more attributes requested) | 37 | Section 1.9.2.1.1 | 11/25/21 2:50:09 PM by vhofman |
|
| CH-XCPD | CH-XCPD-002 | reviewed | Testable |
0
|
1
| | The Health Data Locator and Revoke Option of the Patient Location Query transaction [ITI-56] MUST NOT be used (see Section 1.10.1 Modes and Options) | 38 | Section 1.10.1 | 7/2/21 10:46:37 AM by aeschlimann |
|
| CH-XUA | CH-XUA-013 | | Testable |
0
|
3
| Agreed to do not cover this assertion | The User Authentication Provider authenticates the user and returns a SAML 2 Authentication Assertion (see Section 1.6.4.1.1 Scope) | 14 | Section 1.6.4.1.1 | 1/22/24 2:03:10 PM by vhofman |
|
| CH-XUA | CH-XUA-026 | | Testable |
0
|
1
| Agreed to do not cover this assertion | X-Service User actor MUST be able to send SAML attribute queries to the Identity Provider to query specific attributes according to the Identity Provider (see Section 1.6.4.2.2 Use Case Roles) | 15 | Section 1.6.4.2.2 | 1/22/24 2:03:10 PM by vhofman |
|
| CH-XUA | CH-XUA-031 | | Testable |
0
|
0
| | [SAML Assertion - HCP - ASS - TCU] The <NameID> child element of the <Subject> MUST contain the GLN of the subject with name qualifier attribute set to urn:gs1:gln. | 24 | Section 1.6.4.3.4.2.1 | 1/22/24 2:03:10 PM by vhofman |
|
| CH-XUA | CH-XUA-092 | reviewed | Testable |
0
|
0
| | [SAML Assertion - ASS] The purpose of use attribute ("urn:oasis:names:tc:xspa:1.0:subject:purposeofuse") of the <AttributeStatement> MUST be either code NORM or EMER from code system 2.16.756.5.30.1.127.3.10.5 of the CH:EPR value set. | 25 | Section 1.6.4.3.4.2.2 | 1/22/24 2:03:10 PM by vhofman |
|
| CH-XUA | CH-XUA-093 | reviewed | Testable |
0
|
0
| | [SAML Assertion - TCU] The purpose of use attribute ("urn:oasis:names:tc:xspa:1.0:subject:purposeofuse") MUST be code AUTO from code system 2.16.756.5.30.1.127.3.10.5 of the CH:EPR value set. | 26 | Section 1.6.4.3.4.2.3 | 1/22/24 2:03:10 PM by vhofman |
|