Skip to content
Intruno
  • Platform
    • Platform Overview
    • Patient Privacy Monitoring
    • Investigations
    • Compliance Operations
    • Analytics & Reporting
    • Integrations
    • Exclusion Check
    • Hotline Nate
  • Solutions
  • Resources
  • Company
    • About
    • Careers
    • Contact
Request a Demo
  • Platform
    • Platform Overview
    • Patient Privacy Monitoring
    • Investigations
    • Compliance Operations
    • Analytics & Reporting
    • Integrations
    • Exclusion Check
    • Hotline Nate
  • Solutions
  • Resources
  • Company
    • About
    • Careers
    • Contact
Request a Demo
What HIPAA actually…What an audit log can…Building a review routine…Where Intruno fits
Home›Resources›Guide
Guide

EHR audit log review: what HIPAA requires and how to run it

What the Security Rule asks for, what an audit log can and cannot tell you and how to build a review routine you can defend.

Intruno · Reviewed November 2026 · 3 min read

What HIPAA actually requires

Two parts of the HIPAA Security Rule apply to EHR access. The audit controls standard requires covered entities and business associates to put in place hardware, software or procedures that record and examine activity in systems holding electronic protected health information (45 CFR §164.312(b)). The information system activity review specification requires them to regularly review those records, such as audit logs, access reports and security incident tracking reports (§164.308(a)(1)(ii)(D)).

HIPAA does not name a tool, a sample size or a review frequency. Each organization decides what “regularly” means based on its risk analysis, then documents that decision and follows it. Policies and procedures, and records of the actions they require, are kept for six years (§164.316(b)(2)).

What an audit log can tell you

An EHR audit log records who opened which patient’s record, when, from which workstation or application and what they did: viewed, edited, printed or exported. That is enough to answer “who looked?” It is not enough to answer “should they have?”

The log does not know that the user is on the patient’s care team, works night shifts in another department or lives on the same street. Those facts sit in scheduling, HR, identity and clinical systems. Reviewing raw logs line by line means finding that context by hand for every entry, which is why manual review rarely gets past spot checks.

Building a review routine you can defend

  1. Decide what you review and how often. Write down the scenarios that matter to your organization, such as VIP and employee records, family members, coworkers and neighbors. Set the cadence for each.
  2. Add context before anyone reviews. Bring role, department, schedule and care relationship into the review so analysts start from a question, not a log line.
  3. Review by exception. Clinicians open thousands of records a day for good reasons. Focus human review on the access that lacks an explanation.
  4. Document every decision. Record what was reviewed, what was found, who decided and why, including the reviews that found nothing wrong.
  5. Close the loop. Feed outcomes back into training, policy and the scenarios you review. Report the trend to leadership.

The documentation is what makes the program defensible. When OCR, auditors or your own leadership ask how you monitor access, the answer is the record of reviews and decisions, not the existence of a log.

Where Intruno fits

Intruno Patient Privacy Monitoring reads access events from your EHR audit logs, adds the context the log is missing, such as role, department, schedule and care relationship. It raises an alert when an access needs a closer look. Each alert can become an investigation with its evidence attached, so the review and its outcome stay in one record.

General information, not legal advice. Check the current rules and talk to counsel about your situation.

RelatedPatient Privacy Monitoring →Questions privacy and compliance teams ask →Glossary of terms →

More from Resources

ArticleBreak-the-glass access: what privacy teams should reviewGuideThe HIPAA breach risk assessment and its four factorsArticleHow often should you check the OIG exclusion list?
Nate AI assistant · Intruno

Tell Nate what the email should say. It drafts a subject and body you can send from your own inbox.

Subject
Body
Open in email →
Intruno
SOC 2

The operating system for healthcare privacy and compliance programs.

LinkedIn
Platform
  • Overview
  • Patient Privacy Monitoring
  • Investigations
  • Compliance Operations
  • Analytics & Reporting
  • Integrations
  • Exclusion Check
  • Hotline Nate
Solutions
  • CISO & Security
  • Privacy Operations
  • Compliance
  • Human Resources
  • Health Information Mgmt
  • IT / Administration
Resources
  • All resources
  • Certifications
  • Articles
  • Access walkthrough
Company
  • About
  • Careers
  • Contact
  • Request a Demo

© 2026 Intruno, Inc. All rights reserved.

  • Privacy Policy
  • Security
  • Terms