Reference Guide

HPMA Audit Message Reference
8
HP Medical Archive
Event-Specific Data
Following the opening “[AUDT” container that identifies the message
itself, is a series of items specific to each event or action. Chapter 3,
“Message Reference” on page 11 lists attributes commonly used for
tracing grid activity.
Common Elements
After the event-specific information is a set of elements common to all
audit messages:
IP32 IP Address; a 32-bit IP address representation.
CSTR C String; a variable length array of characters.
Table 1: Data Types (cont.)
Type Description
Table 2: Common Elements of Audit Messages
Code Type Description
AVER UI32 Version—The version of the audit message. As the HP Medical
Archive software evolves, new versions of services may incorporate
new features in audit reporting. This field enables backward com-
patibility in the AMS to process messages from older versions of
services.
ATYP FC32 Event Type—A four-character identifier of the event being logged.
This governs the “payload” content of the message—the attributes
included.
ATIM UI64 Timestamp—The time the event was generated that triggered the
audit message, measured in microseconds since the operating sys-
tem epoch (00:00:00 UTC on 1 January, 1970). Note that most avail-
able tools for converting the timestamp to local date and time are
based on milliseconds. Rounding or truncation of the database
timestamp may be required.
ATID UI64 Trace ID—An identifier that is shared by the set of messages that
were triggered by a single event.