Audit Trail

An audit trail is the memory a system keeps of itself. Who did what, and when. Every time somebody changes a price, cancels an invoice, corrects a phone number or opens a patient file, a line is written in a place the everyday screens never show. That line holds the name, the date, the time, and usually the value before and after the change.

Most people meet the idea during an argument. A customer says the invoice was cancelled by mistake. An accountant is certain the discount was never approved. With no record, the loudest voice wins. With one, the question takes two minutes and nobody has to guess.

This is why a careful system never truly deletes anything. The row is marked as removed and vanishes from the list, but it stays in the database along with the name of the person who removed it. Staff often ask us to make delete mean delete. We say no and explain why. The week money goes missing is the week you need the rows somebody deleted.

Reading is part of the trail too, and that is the part people forget. In a clinic, who opened a file matters as much as who edited it. When Linkysoft builds a records system, viewing a patient history is recorded the same way an edit is, because staff curiosity is a genuine risk and honest people are glad to prove they were nowhere near a file. The habit comes from our cybersecurity work, and it is built into DocMz, our hospital and clinic system.

Two questions are worth asking a supplier before you sign. How many years is the history kept? And can anyone holding an administrator password erase it? A trail a manager can quietly wipe is not a trail. It should sit apart from the daily data, out of reach of the people it describes.

There is a cost. The tables grow, and a busy shop can write more history lines than sale lines. Storage is cheap next to one disputed refund, so Linkysoft switches it on by default in every web application we build, then agrees with the owner how long each kind of record is kept.