Audit Trail and Node Authentication

Audit Trail and Node Authentication [ATNA] describes certificate-based node authentication and transmitting PHI-related audit events to a repository. This helps sites implement confidentiality policies.

Summary

The Audit Trail and Node Authentication (ATNA) Integration Profile establishes security measures which, together with the Security Policy and Procedures of the enterprise, provide patient information confidentiality, data integrity and user accountability. The Audit Trail and Node Authentication Integration Profile requires the use of bi-directional certificate-based node authentication for connections to and from each node, and requires that events concerning PHI use are recorded and transmitted to a repository where they can be monitored to detect indications of inappropriate activity.

Details

(From an email by Rob Horn)

ATNA is already integrated into the full ITI Technical Framework. The ATNA core is section 9 of volume 1, and sections 3.16 and 3.17 of Volume II. The underlying DICOM standard can be found at: ftp://medical.nema.org/medical/dicom/supps/sup95_fz.pdf The underlying RFC can be found at a variety of RFC repositories. ATNA specializes these for some purposes, but also invokes their general support so that we don't have to redefine ATNA every time a new profile specializes an audit message for some new purpose. There are individual profile specializations scattered through all the different frameworks. This makes it hard for an implementer. It's easy to pull out the core sections as a starting point, but not the individual profile specializations.

You find sections of specializations in some of the other technical frameworks. Radiology is probably the most complete for this. This scattering of requirements reflects a fundamental conflict of documentation uses. From one perspective you would like it all in one place, and from another perspective you want it documented in the sections that will actually be read by implementers. We have done this only for profiles that were most critical (e.g. XDS, RFD, EUA, XUA). There is some interested in RID and PIX, we need help to create prioritized CP requests for clarity on profiles that the IHE community needs assistance with.

There is also some historical funny business. Originally HL7 was going to issue an HL7 side equivalent to DICOM's Supplement 95, but that lost sponsorship and got abandoned. So DICOM threw together some partial stuff to cover the immediate needs of the imaging community. It deals with only those HL7ish things that happen to DICOM equipment (like receiving orders). DICOM didn't attempt to handle the rest of the HL7 world. So the various IHE domains get creative in a variety of ways.

Systems Affected

<List (in user terms) systems that would be likely candidates for implementing this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. >

Actors & Transactions:

<Insert an actor-transaction diagram, and or list of Content Definitions>

Specification

Profile Status: Final Text <Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>

Documents:

<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>

IHE IT Infrastructure Technical Framework:

• Vol. 1 - Section 5 (SWF Profile)
• Vol. 2 - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
• Vol. 3 - Appendix E

Underlying Standards:

<list all the standards on which the profile is based; if possible with links to sources>

• HL7?
• Syslog?
• XML?
• ...

See Also

<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>

Related Profiles

<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>

• Audit Train and Node Authentication - Radiology Option defines radiology specific audit events for ATNA.
• Cross-enterprise Document Sharing [XDS] depends on ATNA for ...
• ...

Consumer Information

The ATNA Profile FAQ Template answers typical questions about what the Profile does.

The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile.

Implementer Information

Audit Trail and Node Authentication Implementation provides additional information about implementing this Profile in software. Specific questions about how to implement this profile can be found in the ATNA FAQ.

White Paper IHE Security and Privacy for HIE puts ATNA in context.

Reference Articles

Creating an IHE ATNA-Based Audit Repository, Gregg, B. et al, Journal of Digital Imaging, Vol. 19, Number 4, 2006, pp. 307-315

This page is based on the Profile Template