Core Platform

Security Risk AssessmentBETA

An honest HIPAA SRA with a living, source-cited evidence binder — free during beta.

Medicare Underpayment Audit

Find potential coding & charge-capture leaks in your paid claims, cited to CMS.

HIPAA Kit

Downloadable policy templates covering all 23 required safeguards.

Free Tools

Doc Builder

FREE

Free AI generator for appeal letters, PA requests, and call scripts.

Ask D3

FREE

AI compliance assistant answering HIPAA & billing questions instantly.

GuidesSign In
HelpGuidesStatesTemplatesAsk D3PrivacyTerms
© 2026 D3rx. All rights reserved.

Questions or feedback? [email protected]

HIPAA Templates/Information System Activity Review Policy
Administrative Safeguards (164.308)

Information System Activity Review Policy

45 CFR § 164.308(a)(1)(ii)(D)

Requires regular review of audit logs, access reports, and security incident tracking across all systems that store or transmit ePHI. Critical for detecting unauthorized access before it becomes a breach.

What's Included

  • Policy document
  • Audit log review checklist
  • Review schedule template
  • Implementation checklist
  • Annual review template
2 pages · ~869 words · 8 sectionsEstimated customization: ~10 minutesLast updated May 2026

Sample Preview

Administrative Safeguards (164.308)Page 1 of 2

Information System Activity Review Policy

Version 1.0·Effective [EFFECTIVE DATE]·Approved by [PRIVACY/SECURITY OFFICER NAME]

1. Purpose

This policy establishes the requirements for regularly reviewing records of information system activity, including audit logs, access reports, and security incident tracking reports, for all systems that contain or process ePHI at [PRACTICE NAME]. Proactive review of system activity is essential for detecting unauthorized access, preventing breaches, and maintaining accountability.

2. Scope

This policy applies to all information systems owned, operated, or managed by [PRACTICE NAME] that create, receive, maintain, or transmit ePHI. This includes EHR systems, practice management software, patient portals, email systems, file servers, cloud services, and any other system or application that processes ePHI. It applies to all workforce members responsible for administering, monitoring, or using these systems.

3. Policy Statement

[PRACTICE NAME] shall implement procedures to regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports, as required by 45 CFR § 164.308(a)(1)(ii)(D). Reviews shall be conducted frequently enough to detect unauthorized activity in a timely manner and at minimum on a [WEEKLY/MONTHLY] basis. Anomalies and potential security incidents identified during review shall be investigated and documented.

4. Definitions

Audit Log: A chronological record of system activities that provides documentary evidence of the sequence of activities affecting a specific operation, procedure, or event. Typically includes user identity, date/time, action performed, and the data or system affected.

Access Report: A summary of user access activities, including successful and failed login attempts, records accessed, and modifications made.

Security Incident Tracking Report: Documentation of suspected or confirmed security incidents, including the nature of the incident, systems affected, and response actions taken.

Anomaly: Any system activity that deviates from expected patterns and may indicate unauthorized access, misuse, or a security incident.

5. Procedures

1. AUDIT LOG CONFIGURATION

1.1 Ensure all systems containing ePHI are configured to generate audit logs that capture at minimum: user identification, date and time of activity, type of action (create, read, update, delete, print, export), the specific records or data accessed, and success or failure of the action.

1.2 Audit logs shall be protected from unauthorized modification or deletion. Logs shall be stored in a separate, secured location or system where feasible.

1.3 As a matter of [PRACTICE NAME] policy, audit logs shall be retained for a minimum of six (6) years from the date of creation or the date when last in effect, whichever is later. (45 CFR § 164.316(b)(2)(i) requires this six-year retention period for required Security Rule documentation — including the records of these reviews and findings; [PRACTICE NAME] applies the same period to the underlying audit logs.)

2. REVIEW SCHEDULE

2.1 The [SECURITY OFFICER/IT MANAGER] shall conduct a review of system activity records no less frequently than [WEEKLY/MONTHLY].

2.2 The following activities shall be reviewed during each cycle: - Failed login attempts (look for patterns indicating brute-force attacks or unauthorized access attempts) - After-hours access to ePHI systems - Access to records outside the user's assigned patients or job function - Bulk record access, exports, or downloads - Changes to user permissions or system configurations - Any access flagged by the EHR's built-in anomaly detection (if available)

2.3 Additional ad-hoc reviews shall be conducted following any security incident, breach report, or workforce complaint.

3. ANOMALY INVESTIGATION

3.1 When an anomaly is detected during review, the reviewer shall document the finding and initiate an investigation within [NUMBER] business days.

3.2 The investigation shall determine: the identity of the user involved, the nature and extent of the activity, whether the activity was authorized, whether ePHI was compromised, and what corrective action is needed.

3.3 If the investigation reveals a potential breach of unsecured PHI, the Breach Notification Policy shall be activated.

3.4 If the investigation reveals a workforce policy violation, the Sanction Policy shall be applied.

4. DOCUMENTATION

4.1 Each review cycle shall be documented with: the date of the review, the systems reviewed, the reviewer's name, a summary of findings (including "no anomalies detected" if applicable), and any follow-up actions taken.

4.2 Review documentation shall be maintained for a minimum of six (6) years.

6. Roles & Responsibilities

Security Officer ([SECURITY OFFICER NAME]): Establishes the review schedule and procedures. Conducts or oversees system activity reviews. Investigates anomalies and documents findings. Reports findings to practice leadership. Ensures review documentation is retained.

IT Manager/Vendor ([IT CONTACT NAME]): Configures audit logging on all ePHI systems. Provides audit log data and access reports to the Security Officer. Assists with anomaly investigation. Ensures log integrity and retention.

Practice Administrator ([ADMINISTRATOR NAME]): Reviews summary reports from the Security Officer. Allocates resources for investigation and remediation. Supports enforcement actions when violations are identified.

All Workforce Members: Use systems only within their authorized scope. Report suspicious activity or potential security concerns to the Security Officer.

7. Review Schedule

This policy shall be reviewed at least annually and updated to reflect changes in information systems, logging capabilities, or regulatory guidance. The review schedule for system activity (e.g., weekly or monthly cycle) shall also be evaluated during the annual policy review to confirm it is adequate for the practice's risk profile.

8. Regulatory References

45 CFR § 164.308(a)(1)(ii)(D) — Information system activity review (Required) 45 CFR § 164.312(b) — Audit controls (Required) 45 CFR § 164.308(a)(6)(ii) — Security incident response and reporting 45 CFR § 164.316(b)(2)(i) — Security Rule documentation retention (6 years) NIST SP 800-92 — Guide to Computer Security Log Management

Continue reading — unlock the full information system activity review policy
D3rx · HIPAA Compliance Templates
Free

while we’re in beta

A professional, CFR-referenced policy template, ready to customize for your practice. Free during the beta.

Open template

Free while we’re in beta

Need more than one?

Get all 23 policies — free

The Complete HIPAA Policy Library — every policy, checklist, and review template. Free while we’re in beta.

Open the library

Free while we’re in beta

Templates require customization and legal review before adoption. Not legal advice. See full disclaimer.