HIPAA Logging Requirements for Therapy Practices
Outline
HIPAA audit log review card
Event | Why log it | Who reviews it | How often |
|---|---|---|---|
Sign-in, sign-out, and failed sign-in | Detect unusual access attempts and support account investigation | Security or privacy owner | Weekly exception review; monthly trend review |
Client-record view | Identify access to a record and compare it with assigned work | Practice owner or privacy delegate | Monthly, plus triggered review |
Note or record edit | Establish what changed and when for an investigation | Clinical supervisor or privacy delegate | Monthly sample; triggered review |
Export, download, or bulk report | Detect copies leaving the primary system | Security or privacy owner | Weekly exception review |
Permission or role change | Show who gained, lost, or changed access | Practice owner and system administrator | Each change; monthly reconciliation |
Use this card as an operating baseline for HIPAA logging requirements, not as a claim that HIPAA names these five rows as a complete mandatory list. The Security Rule’s audit-control standard is at 45 CFR 164.312(b), and its information-system-activity-review standard is at 45 CFR 164.308. Your risk analysis should determine whether additional events matter for your systems and workflow.
HIPAA logging requirements are about making activity review possible. They are not a promise that a dashboard alone makes a practice compliant, and they do not replace access controls, workforce procedures, incident response, or a documented risk analysis. Use this guide to give your reviewer a defined event set, owner, cadence, and evidence trail. It is educational guidance for US therapy practices, not legal advice.
Start with the systems that handle electronic PHI
List each EHR, scheduling system, telehealth tool, storage location, export destination, and integration that creates, receives, maintains, or transmits electronic protected health information. Record whether the system produces an audit record, where that record lives, who can access it, and whether the record can be exported for review.
When a clinician drafts in Microsoft 365, check what a Copilot note-drafting session leaves behind, including which interaction records the practice can review.
The HIPAA risk-analysis guide can help you connect the log review to threats, vulnerabilities, and safeguards. The goal is not to collect every technical event forever. The goal is to identify activity that could show inappropriate access, an unsafe configuration, a mistaken export, or a change that needs investigation.
Choose events that answer a review question
Start each event category with the question your reviewer needs to answer:
- Who entered the system? Capture successful and failed sign-ins, sign-outs, session termination, and account or authentication changes where the system makes them available.
- Whose record was opened? Capture client-record views and searches when the platform supports them, with the user, timestamp, and record or object involved.
- What changed? Capture note, demographic, treatment-plan, permission, and configuration edits, including the actor and timestamp.
- What left the system? Capture downloads, exports, print actions, bulk reports, API transfers, and other routes that create a copy outside the primary record system when those events are available.
- Who gained access? Capture role assignment, permission changes, invitations, deactivation, and reactivation.
Treat the event labels as operational categories. The exact fields and availability depend on your vendor, configuration, and risk analysis. Do not tell a reviewer that a system captures a field until you have confirmed it in the product’s documentation or a test account.
A filled review example
This example shows the decision trail a reviewer needs. It does not prove that a real vendor produces every field shown, and it does not certify the practice or the vendor.
Assign a reviewer and a trigger path
A log that nobody owns is an archive, not an activity-review control. Name a primary reviewer, a backup, the system administrator who can retrieve records, and the person who decides whether an anomaly becomes an incident. Keep those roles separate when the practice’s size and risk make separation practical.
Set routine review and triggered review separately. A routine review looks for patterns such as repeated failed sign-ins, access outside a user’s caseload, unusual bulk exports, or permission changes without a matching personnel record. A triggered review starts after a lost device, suspected credential sharing, client complaint, termination, vendor change, or system alert.
Your reviewer should record what was examined, the date and time range, exceptions found, the decision, the escalation path, and the evidence location. A short review record is more useful than an unannotated screenshot of a dashboard.
Set a cadence you can defend
HIPAA’s information-system-activity-review standard requires a covered entity to implement procedures to regularly review records of information-system activity, such as audit logs, access reports, and security-incident tracking reports. The regulation does not prescribe one universal weekly, monthly, or quarterly cadence for every practice. Set a cadence that follows your risk analysis, system use, staffing, and event volume, then document why it is appropriate.
A small practice can begin with this structure:
- Each access change: Review the permission event and reconcile it with the approved request.
- Weekly: Review exceptions and high-risk events, including failed sign-ins, bulk exports, and activity outside assigned work.
- Monthly: Review a defined period of access, edits, exports, and role changes; document the outcome.
- After a trigger: Preserve relevant records and investigate promptly under the practice’s incident procedure.
- At least annually: Revisit the event set, reviewer, cadence, system inventory, and risk analysis, and after a material system or workflow change.
These are implementation choices, not a federal schedule. Adjust them when your risk analysis, state law, contract, insurer, or system design calls for a stricter process.
Document retention without inventing a HIPAA log period
Do not write that HIPAA requires every audit log to be kept for six years. The Security Rule provisions cited above do not set one universal audit-log retention period for every practice or technical record. Set a documented period through risk analysis, system limits, applicable state law, contracts, and preservation needs.
Instead, write a retention policy that identifies:
- The audit records your practice treats as evidence of required policies, procedures, actions, activities, and assessments
- The system’s native retention and export limits
- The date the retention period starts and the event that closes it
- Preservation steps for an active incident, complaint, investigation, litigation hold, or regulatory request
- State-law, contract, insurer, and business requirements that may be stricter
- The owner who reviews the policy when a system, vendor, or legal requirement changes
Ask qualified counsel or a privacy professional to apply the rule to your facts, especially when a state requirement, payer contract, breach investigation, or litigation hold affects the schedule. The HIPAA compliance checklist provides a broader practice-level review; the HIPAA encryption guide covers a different technical safeguard and should not be substituted for activity review.
What to include in each review record
Keep a review record that lets another authorized person understand what happened without opening every raw event. Include the system and date range, reviewer, event categories examined, filters or sample method, exceptions, supporting evidence, decision, escalation, and closure date. Do not copy more client information into the review record than the reviewer needs for the defined purpose.
If the reviewer finds an unexplained access or export, preserve the relevant raw records before normal retention or rotation removes them. Follow the practice’s incident-response process, investigate the account and record involved, and document the decision. Do not silently edit or delete an event to make the review look clean.
For a solo practice, the owner may review the records and document the decision; the solo-practice HIPAA guide adds the one-person operating context. For a group practice, assign the reviewer by role, keep a backup, and reconcile permissions to the workforce roster. The group-practice HIPAA guide covers the wider governance structure.
Keep the control useful
A large log collection can still fail the practical test if nobody can interpret it. Start with the activity that could affect confidentiality, integrity, or availability of electronic PHI. Test retrieval, confirm timestamps and user identity, check that exports are readable, and record gaps that need a vendor or configuration decision.
Review the control after you add an AI tool, connect a new integration, change roles, move records, adopt remote work, or change the way clinicians access the chart. Revisit your HIPAA logging requirements when the systems or risks change. Emosapien can help keep approved documentation and workflow context together for clinician review; it does not determine your HIPAA obligations, set your retention period, investigate an incident, or replace your privacy lead and counsel.
Turn your logging plan into a reviewable workflow
Emosapien helps keep approved documentation and workflow context together for clinician review, while your practice sets its own HIPAA controls and retention rules.
Start free- No credit card
- HIPAA-ready
Transcript
“…honestly my sleep has been rough again this week, and it’s making everything harder.”
Co-therapist suggestion
Sleep came up in 3 of the last 4 sessions. Consider revisiting sleep-hygiene CBT and the 4-7-8 technique.
References
Related reading
42 CFR Part 2 Therapy Guide: Consent and Mixed Records
42 CFR Part 2 therapy after the 2024 final rule: program status, TPO consent, redisclosure notices, SUD counseling notes, and mixed-record checks.
Read article →ACA Ethical Codes: Principles and Section-by-Section Practice Guide
Use the ACA ethical codes as a practice guide. Match each ACA Code of Ethics section to the counseling decision in front of you.
Read article →Get the therapist toolkit
Practical, plainspoken notes on AI for therapy practices. No spam, unsubscribe any time.