Please use a compatible browser :Google Chrome or Mozilla Firefox
Page expired. Any change will be lost. Try to refresh the page.
Gazelle update scheduled, unsaved changes will be lost :
Your session will timeout :
Redeployed...
Logged out...
The server is restarting. Any change will be lost.
 

Actor : Secure Node

Actor Details Last changed 6/19/18 9:51:58 AM by mtoudic

10
SN
Secure Node
A system unit that validates the identity of any user and of any other node, and determines whether or not access to the system for this user and information exchange with the other node is allowed. Maintains the correct time.
Id
Keyword
Name
Description
Status
Action
48 ATNA Audit Trail and Node Authentication The ITI Audit Trail and Node Authentication (ATNA) Profile establishes the characteristics of a Basic Secure Node: It describes the security environment (user identification, authentication, authorization, access control, etc.) assumed for the node so that security reviewers may decide whether this matches their environments. It defines basic security requirements for the communications of the node using TLS or equivalent functionality. It defines basic auditing requirements for the node. The profile also establishes the characteristics of the communication of audit messages between the Basic Secure Nodes and Audit Repository nodes that collect audit information. Final Text
377 CH:ATNA Audit Trail and Node Authentication Swiss Extension Trial Implementation
354 CH:ATNA Deprecated Audit Trail and Node Authentication Swiss Extension Deprecated Deprecated
51 DEPRECATED:SEC DEPRECATED: Basic Security The Basic Security Integration Profile establishes basic security measures that can, as part of an institution s overall security policies and procedures in the enterprise, help protect the confidentiality of patient information. It also provides institutions with a mechanism to consolidate audit trail events on user activity across several systems interconnected in a secure manner. Deprecated
243 epSOS Security epSOS Security This profile is for handling the security aspects of epSOS Trial Implementation
123 T15 HITSP Collect and Communicate Audit Trail US HITSP: T15: Collect and Communicate Audit Trail. The Collect and Communicate Security Audit Trail Transaction is a means to provide assurance that security policies are being followed or enforced and that risks are being mitigated. This document describes the mechanisms to define and identify security relevant events and the data to be collected and communicated as determined by policy, regulation or risk analysis. It also provides the mechanism to determine the record format to support analytical reports that are needed. HITSP Construct
124 T17 HITSP Secured Communication Channel Transaction US HITSP: T17: Secured Communication Channel Transaction. The Secured Communication Channel Transaction provides the mechanisms to ensure the authenticity, integrity, and confidentiality of transmissions, and the mutual trust between communicating parties. Its objectives include providing: mutual node authentication to assure each node of the others’ identity; transmission integrity to guard against improper information modification or destruction while in transit; and transmission confidentiality to ensure that information in transit is not disclosed to unauthorized individuals, entities, or processes. HITSP Construct
Id
Keyword
Name
Description
TF Reference
Status
Specifications
Action
43 ITI-1 Maintain Time NTP transactions used to maintain time synchronization. Final Text
151 ITI-19 Authenticate Node This transaction is embedded within all network communications activity. All DICOM, HL7, and HTML connections shall comply with the IHE specification for bi-directional authentication and authorization of communications of Protected Healthcare Information (PHI). IHE does not specify how other protocols that transfer PHI shall perform bi-directional authentication and authorization, but requires that other protocols perform such authentication and authorization.</p> Final Text
77 ITI-20 Record Audit Event The delivery of an audit event description from any secure node to the Audit Repository. Final Text
1 NULL NULL Dummy transaction Final Text
30 RAD-34 Record Audit Event-Deprecated Create and transmit an Audit Record. Deprecated
Assertion Id
Description
CH-ATC-014 The Patient Audit Record Repository MUST be grouped with actor : CH:ATNA - Secure Node (see Table 3 Actor Grouping)
CH-RESTfulATNA-002 [ITI-20] TLS Shall be used.
ITI20_RESTful-001 A Secure Node, Secure Application or Audit Record Forwarder SHALL issue an HTTP request according to requirements defined in the FHIR specification for create interaction (http://hl7.org/fhir/R4/http.html#create ).
ITI20_RESTful-002 The Secure Node, Secure Application or Audit Record Forwarder SHALL submit the FHIR AuditEvent Resource in either XML format or JSON format.
ITI20_RESTful-003 An AuditEvent Resource that reflect Audit Message definition defined in IHE Technical Framework SHALL conform to the requirements defined in Section 3.20.4.2.2.1.
ITI20_RESTful-004 The mappings between IHE defined Audit Message content and FHIR AuditEvent Resource is based on FHIR Table 6.4.7.4 (http://hl7.org/fhir/R4/auditevent-mappings.html) that is further constrained in Table 3.20.4.2.2.1-1.
ITI20_RESTful-020 The message uses an HTTP POST method to submit a FHIR Bundle Resource. The client SHALL post FHIR resources in either XML format or JSON format.
ITI20_RESTful-021 The FHIR Bundle Resource SHALL contain at least one FHIR AuditEvent Resource (https://www.hl7.org/fhir/R4/auditevent.html).
ITI20_RESTful-022 The element Bundle.entry.request.method SHALL be POST.
ITI20_RESTful-023 AuditEvent Resources included in the Bundle that reflect Audit Message definitions defined in IHE Technical Framework SHALL conform to the requirements defined in Section 3.20.4.2.2.1.
RESTfulATNA-007 Audit Record Repository, Audit Record Forwarder, Secure Node and Secure Application SHALL support at least one of the ATX Options
RESTfulATNA-013 A Secure Node, Secure Application or Audit Record Forwarder that supports ATX: FHIR Feed Option SHALL at least support one of the two RESTful interactions defined in the Record Audit Event [ITI-20] transaction. See ITI TF-2: 3.20.4.2 (Send Audit Resource) and 3.20.4.4 (Send Audit Bundle).
RESTfulATNA-016 The Internet User Authorization (IUA) Profile SHOULD be considered for the authorization controls.

Tool index

  • Simulators

    Copyright IHE 2024
  • Gazelle 7.1.7
Back to top