Keep a Tamper-Evident Audit Trail of Patient-Data Actions

Some things in Veona happen automatically, quietly, on every screen, for every role — and the audit trail is the clearest example. You do not “turn on” auditing or remember to log anything. Whenever anyone in the facility looks at, creates, changes or releases a patient’s clinical record, Veona writes a line to a permanent, tamper-evident trail. This page explains what is recorded, why it cannot be quietly edited, and how the Compliance officer reads it back.

Who / when: the trail is written for everyone, all the time — but it is read by the Compliance officer (and Administrators), whenever there is a question to answer: a complaint, a regulator’s request, or a routine “who saw this patient?” check.

First, the words you’ll meet:

• Patient data — any detail that identifies a patient or describes their care — name, date of birth, a diagnosis, a result value, a note. This is the thing the law most protects, so every touch of it is recorded.
• Audit trail — the running log of who did what, to whose record, and when. It is append-only.
• Append-only / tamper-evident — entries can be added but never silently changed or deleted. If anyone tried to alter the history, it would show. This is what makes the trail trustworthy in front of a regulator.

1. Compliance — to read the trail, open Admin → Audit Log. This is the facility-wide record of clinical actions: each row names the actor (the staff member), the action (viewed, created, updated, signed, released, deleted), the record it touched, and the exact timestamp.
2. Compliance — narrow the view with the filters at the top: by staff member, by patient, by date range, or by the kind of action. To answer “who opened this patient’s chart last week?”, filter by the patient and the dates and read the rows back.
3. Compliance — for the security side of the house (sign-ins, failed logins, password and PIN changes, multi-factor events), open Admin → Security Log. This is the companion trail for account activity rather than clinical activity.
4. Compliance — to answer the specific question “who has accessed this one patient’s record?”, open Admin → Patient Access. It lists, per patient, every staff member who reached their record and when — the report you hand a patient who exercises their right to know who saw their data.

Note

You do not start, stop or configure auditing — it is part of the foundation, not a feature you switch on. Every module writes to the same trail through one shared audit writer, so a lab release, a ward medication, a chart note and a billing change all land in the same place, in the same format.

Caution

The audit trail is append-only by design: there is no “edit” or “delete” button on a logged event, and there is no setting that turns logging off for a screen or a role. That is deliberate — an audit trail you could quietly trim would be worthless. If a record itself was entered in error, you do not erase the history; you amend the record (see Sign and Amend Any Record With Your eSign PIN), which leaves both the original and the correction visible, with the reason and the signer recorded.

What happens next: because every action on patient data is captured the instant it happens, you are always able to reconstruct exactly what occurred — for an investigation, a regulator, or a patient who asks. The trail is scoped to your facility (you never see another tenant’s activity), it is written under the same per-tenant encryption as the rest of the record (see Encrypt Patient Data Per Tenant With Envelope Keys), and it pairs naturally with the e-signature on every clinical document: the signature says who stands behind this, and the audit trail says who did everything around it.

Follow the trail

• Related: Encrypt Patient Data Per Tenant With Envelope Keys · Store Encrypted Files Used Everywhere · Sign and Amend Any Record With Your eSign PIN