Audit Dispatch Service
Last updated
Was this helpful?
Last updated
Was this helpful?
IAuditDispatchService in assembly SanteDB.Core.Api version 3.0.1980.0
Represents a service that dispatches audits to a central repository
The auditing of access to clinical data is of the utmost importance. SanteDB generates and stores audits locally using an for . However, many implementations will have centralized audit repositories for collecting audits from various health systems in a central place. Such collection is useful to establishing overall patterns of access across systems in an HIE (for example)
The audit dispatching service is responsible for sending instances to remote audit repositories. The service's responsibilities are:
Ensure that the instance is complete and contains relevant information for this node
Transform the class into the appropriate format (IETF RFC3881, FHIR, etc.)
Ensure the delivery of the audit to the central repository
SendAudit
void
AuditEventData audit
Sends the audit to the central authority
Represents an audit dispatcher which uses the administrative queue for the dispatching of audits.
Represents an audit service that communicates Audits via an IHE ATNA transport
The specific formats of audits supported are:
The audits can be sent via a variety of transports including:
UDP Syslog
TCP Syslog
Secure (TLS) TCP Syslog
HTTP POST
File System Settings
Audit dispatch service which sends audits using HL7 FHIR
In order to reduce the number of audits which are sent to the central environment, a dispatcher is used. This allows only audits relevant audits to be sent to the central server via
This implementation of the is responsible for creating and dispatching audits in one of the appropriate formats for audits.
messages
messages
The configuration of this service is described in
This implementation of the is responsible for dispatching audits to a central FHIR repository which supports the FHIR auditing specification.
This dispatcher is configured using the class where the dispatcher name is audit. The dispatcher configuration may include authentication/authorization parameters for the solution, as well as authenticators or proxy information.