Audit Log

An audit log records actions taken in a system — which user, which record, what changed, at what time — and is written by the system rather than by the person acting. A thorough one records reads as well as writes, because looking at a record somebody has no reason to look at is itself an event worth capturing. Entries are appended, never edited, and a correction is a new entry rather than an alteration of an old one.

Why it matters in a hospital

Without an audit log, a disputed bill, an altered clinical note or a question about who accessed a record has no factual answer, only recollections. It is also what makes correction safe: a record that can be amended and shows that it was amended is more trustworthy than one that cannot be touched at all, because the alternative to amendment is usually a second, conflicting record. It is also the evidence any data-protection question is answered with: a log shows what happened to a record, which is a different thing from being compliant, and no substitute for reading the obligations themselves.

How Trisvio handles it

Trisvio audits data changes, and the opening of key records such as the patient profile, a visit, a report or a print, storing the before and after values for money-path actions so a disputed figure can be traced rather than argued about. Audit entries are system-written and exempt from the tenant-scoping rules that apply elsewhere, which is what stops a log being editable by the people it records.