For those that struggle with the way that IHE documents the specific requirements of audit logging per type of security event or per ITI transaction; there is an easier tool. The IHE Gazelle "Security Suite" Tool has each audit log message broken down and explained.
My hope is that soon this tool is the way that IHE documents the transaction patterns, so that the supplements and technical-framework documents no longer have the ugly tables.
Here is what shows for the IHE ITI-2 User Authenticate Login message:
The Gazelle tool is also used for Testing...
Here is the generic Security relevant events. These are expected of any application/service that participates in these security relevant events. DICOM -- PS3.15 - A.5.3
There are also a specification page for EACH of the other ITI transactions. For example (They are ALL in the Gazelle tool, so go there and see them all):
My hope is that soon this tool is the way that IHE documents the transaction patterns, so that the supplements and technical-framework documents no longer have the ugly tables.
Here is what shows for the IHE ITI-2 User Authenticate Login message:
The Gazelle tool is also used for Testing...
Here is the generic Security relevant events. These are expected of any application/service that participates in these security relevant events. DICOM -- PS3.15 - A.5.3
- IHE - DICOM - Application Entity Start
- IHE - DICOM - Application Entity Stop
- IHE - DICOM - Audit Log Used
- IHE - DICOM - Begin Transferring DICOM Instances
- IHE - DICOM - Data Export
- IHE - DICOM - Data Import
- IHE - DICOM - General Message Format Conventions
- IHE - DICOM - Instances Accessed
- IHE - DICOM - Instances Transferred
- IHE - DICOM - Query
- IHE - DICOM - Security Alert
- IHE - DICOM - Study Deleted
There are also a specification page for EACH of the other ITI transactions. For example (They are ALL in the Gazelle tool, so go there and see them all):
This comment has been removed by a blog administrator.
ReplyDelete