# EHR Audit Trail: What It Records and How Long to Keep It

Source: https://www.longevityehr.com/blog/ehr-audit-trail

What an EHR audit trail records, how it differs from the patient chart, what HIPAA requires, and how cash-pay clinics should review and retain audit logs.

Last updated: 2026-11-10

## Key takeaways

- An audit trail records user, date, time, action and the item touched. It is metadata about system activity, not the patient's clinical record.
- The HIPAA Security Rule requires mechanisms that record and examine activity in systems containing electronic PHI. It sets no separate retention period for raw logs.
- Required Security Rule documentation must be kept for six years, and many organizations align log retention to that. Longer standards and state rules may apply.
- A trail only helps if someone reviews it. Define who reviews, how often, and what triggers escalation.
- When choosing software, ask how access is controlled, whether data is isolated per clinic, and whether a BAA is available.

An EHR audit trail is the chronological, system-generated record of who did what inside your electronic health record: who logged in, which chart they opened, what they changed, and when. It is metadata about activity, separate from the clinical content of the chart. For a cash-pay longevity, functional medicine, concierge or hormone clinic, it is the evidence you rely on when a patient asks who viewed their file, when a note is questioned, or when a privacy incident needs to be investigated. This guide explains what the trail contains, what HIPAA says about it, how long to retain it, and how to build a review routine that a small practice can sustain.

This is general information for clinic owners and operators in the United States, not legal, compliance or financial advice. Have your healthcare attorney or compliance professional review your own policies.

## What an EHR audit trail is

An audit trail (also called an audit log or event log) is a secure, time-ordered record of actions taken in a system. In an EHR, it typically captures the date, the time, the person who accessed the record, the user ID, the action taken and the items viewed. [Legal scholarship on routine disclosures](https://lawreview.law.uic.edu/news-stories/metadata-how-technology-has-changed-routine-disclosures/) describes it as metadata that records system activity, in contrast to the medical record, which holds health and treatment information.

The AHIMA guidance on [managing audit trails](https://journal.ahima.org/Portals/0/archives/AHIMA%20files/Managing%20Audit%20Trails.pdf) adds that useful entries show who accessed the system, when, and what operations were performed, with context such as the user, the application, the workstation and a description of the event.

Two properties matter in practice:

- **Chronological.** Entries are written in the order events occur, so the trail can reconstruct a sequence.
- **Tamper-resistant.** The trail is only credible if ordinary users, including the clinicians whose actions it records, cannot edit or delete it.

### Audit trail versus the patient's clinical record

The two serve different purposes, and clinics sometimes confuse them.

| | Clinical record | Audit trail |
|---|---|---|
| Content | Diagnoses, notes, labs, care plans, intake forms | Who accessed or changed what, and when |
| Main purpose | Patient care and continuity | Security, privacy, integrity, investigation |
| Written by | Clinicians and patients (intake) | The system, automatically |
| Typical HIPAA status | Part of the designated record set | Generally metadata, outside the designated record set |

The same legal source notes that audit trails are generally not part of the designated record set under HIPAA, although they may be produced in litigation discovery when specifically requested. Your counsel should advise on how that applies to your state and your situation.

## What the HIPAA Security Rule requires

The Security Rule's technical safeguards include a standard for audit controls. The regulation text at [45 CFR 164.312(b)](https://www.bricker.com/insights/resources/key/hipaa-security-regulations-security-standards-for-the-protection-of-electronic-phi-technical-safeguards-164-312) calls for hardware, software or procedural mechanisms that record and examine activity in information systems that contain or use electronic protected health information.

Two verbs in that sentence carry the obligation:

1. **Record.** The system must capture activity.
2. **Examine.** Someone must actually look at it, under a documented procedure. A log that nobody reads satisfies the first verb and fails the second.

The rule does not prescribe exactly which events to log or how often to review. That is left to your risk analysis, which is why a five-provider concierge practice and a multi-location group will end up with different review routines.

## What a good audit trail records

The AHIMA guidance and the ASTM audit log standard (E2147) point toward a consistent set of elements. A practical checklist:

- **Authentication events:** successful and failed logins, logouts, lockouts.
- **Record access:** which chart was opened, by which user, from which workstation or device.
- **Create, change and delete actions:** including the prior value where the system supports it.
- **Note signing and addenda:** when a note was signed and any later amendments.
- **Disclosures and exports:** printing, downloads, sharing, bulk exports.
- **Permission changes:** new users, role changes, deactivations.
- **Patient portal activity:** logins and actions by patients or proxies.

### A fictional example entry

The entry below is invented for illustration and describes no real patient or user.

| Timestamp | User ID | Role | Action | Item | Source |
|---|---|---|---|---|---|
| 2026-03-12 09:14:07 | u-2041 | Front desk | View | Demographics, patient 00417 | Workstation 3 |
| 2026-03-12 09:41:52 | u-1007 | Physician | Edit | Progress note, signed version 1 to addendum | Office laptop |
| 2026-03-12 17:55:30 | u-2041 | Front desk | View | Lab results, patient 00982 | Home IP address |

A reviewer reading this would see three different stories. The first line is routine. The second shows a signed note amended through an addendum, which is the correct pattern. The third deserves a question: a front desk user viewing lab results after hours from outside the office, for a patient with no scheduled visit. It may have a benign explanation, but the trail is what lets you ask the question and document the answer.

## What clinics use audit trails for

### Privacy and security monitoring

The primary use is detecting inappropriate access: snooping on a celebrity or acquaintance's chart, a former employee's account still active, or credentials used from an unexpected location. AHIMA notes that audit trails may consist of several audit files on different network entities, so monitoring inappropriate behavior may require feedback from several systems, not just the EHR. Larger organizations often centralize logs in a SIEM, as [one compliance vendor describes](https://www.accountablehq.com/post/hipaa-compliant-siem-implementation-requirements-for-healthcare-organizations), but a small practice can start with a documented periodic review of the EHR's own log.

![Privacy and security monitoring](https://www.longevityehr.com/media/blog/ehr-audit-trail/1.jpg)

### Record integrity

ASTM International's E31 committee holds in its [E2147 specification](https://www.astm.org/e2147-18.html) that audit logs, maintained alongside records, help confirm the integrity and accuracy of the underlying medical data and create a self-authenticating history. For a clinic, that means you can show that a note was written when you say it was, and that a later change was an addendum rather than a rewrite.

### Workflow and operations analysis

Researchers use event logs to study how clinicians and teams work. A paper on [event logs in EHR research](https://pmc.ncbi.nlm.nih.gov/articles/PMC9748581/) describes how they allow study of workflows and team dynamics, and of links between EHR use and burnout, without the costs or biases of surveys or direct observation. A practice can borrow the idea informally: if the trail shows notes routinely finished late in the evening, documentation burden may be a scheduling problem.

### Disputes and claims

When a late edit, a missing note or a timing gap is alleged, the trail is often the first thing requested. That is a reason to establish habits now: sign notes promptly, use addenda rather than overwriting, and never alter records after a complaint arrives. Ask your attorney how to respond to any request for audit data.

## How long to retain EHR audit logs

Retention is easy to get wrong, because the answer has layers.

**HIPAA.** The Security Rule does not set a separate retention period for raw audit logs. It does require that [Security Rule documentation be retained for six years](https://medcurity.com/hipaa-audit-log-requirements/), and many organizations align log retention with that period so logs are available for investigations and audits.

**ASTM E2147-18.** The standard recommends keeping audit data at least as long as the medical records themselves, typically at least 10 years or, for minors, two years after they reach the age of majority, whichever is longer. It is a [consensus standard](https://www.astm.org/e2147-18.html), not a federal statute, but it is a reasonable benchmark when you set policy.

![HIPAA and ASTM audit log retention periods](https://www.longevityehr.com/media/blog/ehr-audit-trail/2.jpg)

**State law.** Medical record retention periods vary by state, and some states treat related data differently. Confirm the rule for each state where you hold patients, especially if you operate across state lines or run telehealth.

**Other jurisdictions.** Rules elsewhere can be stricter. Ontario's PHIPA regulations, for example, [treat audit logs as part of the health record](https://www.dermadex.ca/blog/audit-logging-in-healthcare-apps-what-phipa-requires) and require keeping them at least 10 years from the last entry, or until the patient turns 18, whichever is longer. That is Canadian law and does not apply to a US practice, but it shows why a longer retention horizon is common.

| Source | Period | Applies to |
|---|---|---|
| HIPAA Security Rule documentation | 6 years | US covered entities and business associates |
| ASTM E2147-18 recommendation | At least 10 years, or age of majority plus 2 years for minors | Voluntary standard |
| State medical records law | Varies by state | Check each state of operation |

A sensible default is to set audit log retention to match your medical record retention, document it in a written policy, and have your attorney confirm it. Also decide who can read the logs, because AHIMA advises restricting access to them and having HIM staff confirm they contain adequate metadata.

## Building an audit review routine for a small clinic

A routine that exists on paper but never happens is worse than none. A workable structure for a cash-pay practice:

1. **Name an owner.** One person, usually the privacy or security officer, is accountable for review. In a small practice that is often the operations lead, with clinical leadership as backup.
2. **Confirm logging is on.** AHIMA's guidance is that audit trails must be enabled and functioning. Verify this when you onboard any system and after major updates.
3. **Define review triggers.** Examples: access to charts of staff members or their relatives, after-hours access, bulk exports, repeated failed logins, access by deactivated users.
4. **Set a cadence.** Monthly spot checks and an immediate review after any report of a concern is a common starting point. Your risk analysis should drive the actual frequency.
5. **Document the outcome.** Record what you reviewed, what you found and what you did, even when the answer is "nothing unusual." That documentation is itself part of your compliance record.
6. **Tie it to offboarding.** When a team member leaves, deactivate the account the same day and review the final week of activity.
7. **Train the team.** Make sure every staff member knows that access is logged and reviewed.

### Role-based access reduces what you have to review

The fewer people who can open a given record, the smaller the trail you need to scrutinize. Role-based access limits front desk staff, coaches and clinicians to what their work requires, and tenant-isolated data keeps one clinic's records separate from another's. These controls complement an audit trail, they do not replace it.

## What to ask when evaluating EHR software

Before signing with any vendor, put these questions in writing:

- Is activity logging on by default, and can users edit or delete log entries?
- Which events are captured, and what fields does each entry contain?
- Can an administrator view or export the log, and who else can see it?
- How long are logs kept, and what happens to them if you cancel?
- Is a business associate agreement (BAA) available?
- How are roles and permissions defined, and is each clinic's data isolated from other customers?

We describe our compliance approach at the [HIPAA security page](https://www.longevityehr.com/security): LongevityEHR is HIPAA, with a BAA on request, and uses role-based access and tenant-isolated data.

## Perspective

> Clinic owners often treat the audit trail as an IT detail until the day they need it. We think it belongs in the same conversation as clinical documentation, because both answer the same question: can you show what happened, who did it and when?
>
> Longevity and functional medicine practices handle many kinds of data per patient: lab panels, biomarker trends, care plans, memberships, telehealth visits. More data means more places where access should be controlled and understood. Our approach is to keep the patient care loop in one platform, with role-based access and data isolated per clinic, so that the question of who can see what has a clear answer rather than being spread across a dozen tools.
>
> Our advice to operators is simple. Choose software where the people, roles and records are defined clearly, put a review routine in writing, and sign a BAA with every vendor that touches PHI. A small practice that does these three things is better positioned than a large one that has logs nobody reads.

## Run your clinic's records in one HIPAA-ready platform

LongevityEHR is white-label EHR software for cash-pay longevity, functional medicine, concierge and hormone clinics. It brings AI lab extraction into your own biomarker ranges, care plans from your clinic templates, clinical notes, intake forms, scheduling with video visits, memberships and payments through your own Stripe account, and a branded patient portal into one place. Every plan includes unlimited patients, and annual billing is 30% off.

![LongevityEHR](https://www.longevityehr.com/media/blog/ehr-audit-trail/3.jpg)

The Trial plan is $0 for 15 days. Core is $99 per provider a month, or $69.30 a month billed annually ($831.60 a year). Scale is $199 per provider a month, or $139.30 a month billed annually ($1,671.60 a year). Enterprise is custom pricing. See the [current plans on our pricing page](https://www.longevityehr.com/pricing), or read how the platform supports [longevity clinic workflows](https://www.longevityehr.com/ehr-for-longevity-clinics).

## Common mistakes to avoid

- **Editing instead of amending.** Overwriting a signed note creates exactly the late-edit pattern that raises questions. Use addenda with a date and reason.
- **Shared logins.** A trail that records "front desk" instead of a named person cannot attribute any action. Every user needs a unique ID.
- **Forgetting departed users.** Check for active accounts of former employees in every access review.
- **Treating the log as the whole story.** A trail shows that a record was opened, not why. Pair it with documented policies on legitimate purposes.
- **No written retention policy.** Decide the period, put it in writing, and have counsel confirm it against your state's rules.
- **Ignoring the clinical side.** Good documentation habits, such as structured [clinical notes](https://www.longevityehr.com/clinical-notes) signed promptly, make the trail easier to interpret.

## Frequently asked questions

### What is an example of an EHR audit trail entry?

A typical entry lists a timestamp, a user ID, the user's role, an action such as view, edit or sign, the record touched and the device or location. For instance, a physician amending a signed progress note through an addendum at 9:41 a.m. from an office laptop. The fictional table above shows how a reviewer reads several such lines together.

### Is an audit trail part of the patient's medical record?

Generally no. It is metadata about system activity, and it is usually treated as outside the designated record set under HIPAA. It can still be requested in litigation. Ask your attorney how your state treats audit data, since the answer can differ.

### How long must EHR audit logs be retained under HIPAA?

HIPAA sets no separate period for raw logs, but Security Rule documentation must be kept for six years, and many organizations align logs to that. The ASTM E2147-18 standard recommends at least as long as the medical record, typically 10 years or more. Check state law and confirm your policy with counsel.

### Who should review audit logs in a small clinic?

Assign one accountable person, usually the privacy or security officer, with a named backup. Review on a set cadence and after any concern, using defined triggers such as after-hours access or bulk exports. Record each review and its outcome.

## Sources

- [Metadata: How Technology Has Changed Routine Disclosures (UIC Law Review)](https://lawreview.law.uic.edu/news-stories/metadata-how-technology-has-changed-routine-disclosures/)
- [Managing Audit Trails (AHIMA)](https://journal.ahima.org/Portals/0/archives/AHIMA%20files/Managing%20Audit%20Trails.pdf)
- [Using event logs to observe interactions with electronic health records (PMC)](https://pmc.ncbi.nlm.nih.gov/articles/PMC9748581/)
- [ASTM E2147-18 Standard Specification for Audit and Disclosure Logs](https://www.astm.org/e2147-18.html)
- [HIPAA Security Regulations, Technical Safeguards, 45 CFR 164.312](https://www.bricker.com/insights/resources/key/hipaa-security-regulations-security-standards-for-the-protection-of-electronic-phi-technical-safeguards-164-312)
- [HIPAA Audit Log Requirements (Medcurity)](https://medcurity.com/hipaa-audit-log-requirements/)
- [HIPAA-Compliant SIEM Implementation Requirements (Accountable)](https://www.accountablehq.com/post/hipaa-compliant-siem-implementation-requirements-for-healthcare-organizations)
- [PHIPA Audit Log Requirements for Healthcare Apps (DermaDex)](https://www.dermadex.ca/blog/audit-logging-in-healthcare-apps-what-phipa-requires)
