The monitoring view is a standard list‑view that functions as an audit log, containing an entry for every event in the system that resulted in a change to data stored in the database, all the way back to implementation. For details of the shared properties and capabilities of all list‑view types, see <link>List Views</link>.
For each event, the following information is stored and displayed in list-view columns:
- Event: This is the name of the event resulting in a change to stored data.
- Accession Number: If the event is associated with a specimen, this is the Accession Number of the specimen. If not, it is left blank.
- Patient Ref: If the event is associated with a patient (via a specimen or directly), this is the main reference identifier for the patient.
- Topic: This is the category of the event. All events in the system are associated with specific categories, such as patient, specimen, culture, direct test or export, for example.
- Status: This indicates whether the event related activity is still in progress and, if not, whether it was successful in achieving its purpose. Values include Started, Completed or Failed.
- User: This is the user responsible for the event, as referenced by a user name. Note, even in the case where an external system generates an event, there will still be a user and hence a username associated with it.
- Added: This is a timestamp (date and time) for the event.
Events can be filtered by Topic, Event type, Status or by using the Filter By Keyword field.
Actions are limited to View Details and View Details (Raw), both of which are only available in the context of a specific event.
View Details provides a cleanly formatted list of the key fields and values associated with the event, while View Details (Raw) gives the JSON formatted representation of the complete message received by the back-end system for processing.