Use the Authenticate Node transaction for all network connections to or from the node that may expose private information as specified in This includes any non-IHE applications that process PHI in that environment, such as database services. This permits cloud-based and other system architectures to claim to be a Secure Node when there are sufficient contractual controls to ensure that security and privacy services cover the entire relevant hardware and software stack.
TRANSPORTER ACTOR FULL
A short list of exceptions may exist if the risk analysis indicates that these are not significant and the full list of exceptions is documented. Contractual control over security is sufficient. A Secure Node vendor does not need to invent its own disk drives or write its own operating system. A Secure Node has control over this entire stack, and ensures that all aspects are covered by the security and privacy services. Security services apply to all aspects of the system from the hardware up to the user interface and external communication. An ultrasound machine is an example of a Secure Node. 9.1.1.1 Secure NodeĪ Secure Node is a system that provides security and privacy services (user authentication, secure communications, security audit recording, and security policy enforcement) for all software and services on that system. When an implementation supports a Secure Node, Secure Application or Audit Record Repository, the ATNA requirements – node authentication, user authentication, access control, event logging, and other security rules – apply to all of the actors in the implementation. Table 9.1-1: Audit Trail and Node Authentication Integration Profile - Actors and Transactions Actorĩ.1.1 Actor Descriptions and Actor Profile Requirements
To claim compliance with this profile, an actor shall support all required transactions (labeled “R”) and may support the optional transactions (labeled “O”). Table 9.1-1 lists the transactions for each actor directly involved in the ATNA Profile. Figure 9.1-1: Audit Trail and Node Authentication Actor Diagram
0 kommentar(er)
