Audit trail
Miraa keeps an audit trail of sensitive actions so there’s an accurate, reviewable history of what happened in the clinical record.
What the audit trail is for
- Accountability — a record of who did what, and when.
- Safety — the ability to review actions if something looks wrong.
- Trust — patients and clinicians are both protected by an honest history.
What tends to be recorded
Sensitive and record-affecting actions are logged, for example:
- Note approval and finalisation.
- Access to and changes in patient records.
- Administrative actions such as user and access changes.
The exact set of audited events and how they’re presented can vary by version and plan. Needs confirmation — confirm what your clinic’s audit view shows.
How clinics use it
- Reviewing an incident — understanding a sequence of actions after the fact.
- Confirming approvals — checking that clinical content was approved by a clinician.
- Access review — checking who has been accessing particular records.
🔒
Because access is logged, only open records and take actions you have a legitimate reason for. The audit trail is there to protect patients — treat it as a reason to be careful, not a formality.
Privacy of the audit trail itself
The audit trail supports accountability while following the same access controls as the rest of the system — not everyone can see everything. Admins and authorised roles review it as appropriate.
Common questions
- Can approvals be traced to a clinician? Approval is designed to be a deliberate, attributable action. See Finalising notes.
- Are edits tracked? Record-affecting actions are auditable. Confirm the specifics for your version.