Quick Summary
To prepare for a HIPAA audit, keep current, organized evidence ready before any letter arrives. Most OCR audits are desk audits, so you will send documents such as your security risk analysis, policies, training records, and access logs for review.
- Most OCR audits are desk audits, where you send documents for review.
- The security risk analysis is the first document auditors ask for and the one most often found deficient.
- Build an evidence matrix that maps each HIPAA requirement to a document, an owner, and a location.
- Assign one audit coordinator and respond to the document request within the deadline in your letter.
- Run a mock audit at least once a year and correct gaps between written policies and staff practice.
Table of Contents
- What a HIPAA Audit Is and Why OCR Conducts Them
- Know the Rules: Privacy, Security, and Breach Notification
- HIPAA Risk Analysis: The Foundation Auditors Look For
- HIPAA Audit Checklist: Safeguards, Policies, and Access Controls
- HIPAA Audit Documentation: Building Your Evidence Matrix
- The HIPAA Audit Process: From Document Request to Closing Meeting
- Preparing Staff for Interviews and Mock Audits
- Prioritizing Remediation and Booking Your Readiness Review
Under the US audit regime, OCR (the HHS Office for Civil Rights) decides who gets audited, and most audits are desk audits: OCR sends a document request and reviews what you send back. That is why the preparation work below is mostly about having current, organized evidence ready before the letter arrives. HHS Office for Civil Rights HIPAA audit program overview describes how the audit program is structured and what OCR examines.
Last Updated: November 21, 2026
What a HIPAA Audit Is and Why OCR Conducts Them
A HIPAA audit is a formal review of whether a covered entity or business associate meets the requirements of the HIPAA Privacy, Security, and Breach Notification Rules.
Audits differ from investigations. An investigation usually follows a complaint or a reported breach, while an audit is a proactive check against a defined protocol.
Most of what you will be asked for is paperwork: policies, risk analyses, training records, and access logs. Practices that struggle are rarely missing the underlying controls.
Know the Rules: Privacy, Security, and Breach Notification
Three rules govern nearly every OCR audit. The Privacy Rule governs how protected health information is used and disclosed. The Security Rule governs electronic protected health information (ePHI) and requires administrative, physical, and technical safeguards. The Breach Notification Rule sets the process and timelines for notifying patients, HHS, and in some cases the media after an impermissible disclosure.
For a medical or dental office, the Security Rule is where most findings land. Buying a HIPAA-compliant electronic health record does not satisfy it. A breakdown of common gaps covers what the Security Rule asks of medical and dental offices.
Breach notification adds a clock. The Texas breach notification deadlines explain the state clocks that may run alongside federal requirements. State laws can impose shorter or additional deadlines, so review the rules that apply where your patients live. HHS breach notification rule guidance sets out the federal requirements.
HIPAA Risk Analysis: The Foundation Auditors Look For
The security risk analysis is the first document an auditor asks about, and it is the one most often found deficient. You can check whether your assessment is genuine or a template PDF against five markers of a real one.
A defensible analysis inventories where ePHI lives, including servers, laptops, mobile devices, backups, imaging systems, and cloud services. A written information security program explains what a real security policy must contain beyond a template.
A common mistake is treating the analysis as a one-time form. Auditors expect it to be updated after significant changes, such as a new EHR, a new vendor, or a move to a cloud platform.
HIPAA Audit Checklist: Safeguards, Policies, and Access Controls
Use this checklist to confirm you have the core artifacts before an audit request arrives:
- Current security risk analysis and risk management plan
- Written policies and procedures covering privacy, security, and breach response
- Workforce training records with dates and attendees
Administrative, Physical, and Technical Safeguards
The Security Rule groups its requirements into three safeguard categories. Administrative safeguards cover policies, workforce security, training, and the designation of a security official. Physical safeguards cover facility access, workstation use, and device and media controls, such as how you dispose of old hard drives. Technical safeguards cover access control, audit logging, integrity protections, transmission security, and encryption.
Auditors test each category against your documents and your actual configuration. A policy stating that laptops are encrypted means little unless you can show the encryption status of the laptops in use. Walk through each safeguard yourself before the auditor does, and note where the paper and the practice diverge.
Access Controls and User Permissions
Access control is one of the most frequently questioned areas. Auditors want to see unique user IDs, role-based permissions that match job duties, and prompt removal of access for departed staff.
Audit logs matter as much as the permissions themselves. Confirm that logging is enabled on your EHR, practice management system, and file servers, and that someone reviews the logs on a defined schedule.
HIPAA Audit Documentation: Building Your Evidence Matrix
Auditors score you against provisions, not intentions. An evidence matrix maps each HIPAA requirement to the specific document, record, or screenshot that proves it, names the owner, and states where the evidence lives. Build it once and maintain it, and a document request becomes a packaging exercise instead of a scramble. The matrix below is organized by provision area; adapt the evidence column to your systems, but keep the owner and location columns populated, because an evidence item with no owner is the item that goes missing.
Provision-mapped evidence matrix
| HIPAA provision area | Evidence to gather | Typical owner | Where to find it |
|---|---|---|---|
| Security risk analysis (45 CFR 164.308(a)(1)(ii)(A)) | Current risk analysis with inventory, threat/vulnerability ratings, and date; prior versions | Compliance officer | Compliance shared drive, risk register |
| Risk management plan (45 CFR 164.308(a)(1)(ii)(B)) | Plan with remediation items, owners, due dates, and status | Compliance officer | Risk register, project tracker |
| Workforce training (45 CFR 164.308(a)(5)) | Completion records with dates, names, and content version; annual refresh proof | HR or practice manager | Learning management system or signed rosters |
| Access control (45 CFR 164.312(a)) | Unique user ID list, role matrix, termination checklist, periodic access review log | IT lead | EHR user admin, directory service |
| Audit logging (45 CFR 164.312(b)) | Logging configuration screenshots and a sample of reviewed logs with reviewer and date | IT lead | EHR admin console, SIEM |
| Contingency plan and backups (45 CFR 164.308(a)(7)) | Backup schedule, backup logs, and restore test results with date and outcome | IT lead | Backup console, test records |
| Business associate agreements (45 CFR 164.502(e), 164.504(e)) | Signed BAAs for every vendor touching PHI, with a vendor inventory | Compliance officer | Contract repository, vendor list |
| Breach and incident response (45 CFR 164.308(a)(6), 164.400-414) | Incident response plan, incident log, breach risk assessments, notification records | Privacy officer | Incident tracker, legal files |
| Physical safeguards (45 CFR 164.310) | Facility access records, workstation use policy, device disposal certificates | Facilities or IT | Facilities log, disposal vendor records |
| Policies and procedures (45 CFR 164.316) | Current policy set with version numbers, approval dates, and review dates | Compliance officer | Policy management system |
How to build and maintain the matrix
Start by listing every provision area in scope for your entity type, then for each one write down the single best piece of evidence that would satisfy an auditor.
Set a review cadence: quarterly for access reviews and training records, annually for the full matrix, and immediately after any significant change such as a new EHR, a new vendor, or a move to a cloud platform.
Small-provider and resource-constrained version
A solo practice or a small business associate does not need a compliance platform to run this matrix. A spreadsheet with the same columns works, provided three habits hold: one named owner for the matrix, one indexed folder structure that mirrors the rows, and a calendar reminder for the quarterly and annual reviews.
Watch out: the most common matrix failure is a row marked complete with no date and no owner, which an auditor reads as an unverified claim; every row needs a last-verified date and a named person.
The HIPAA Audit Process: From Document Request to Closing Meeting
An OCR audit is a defined workflow, not an open-ended review. Knowing each stage, who owns it, and what the clock looks like turns a stressful letter into a project plan. The stages below reflect how OCR's audit program has historically run; confirm the specific deadlines in your own request letter, because OCR sets the response window case by case and it can be short.
Stage 1: Notification and scope confirmation
OCR sends a document request letter that names the entity, the audit type (desk audit is the common form; onsite is less frequent), the rules in scope, and the submission deadline.
Watch out: replying to the request letter with a partial submission and a promise to send the rest later is treated as an incomplete response; send one complete package or request a formal extension.
Stage 2: Document submission
OCR typically asks for policies and procedures, the current security risk analysis and risk management plan, training records, business associate agreements, access control documentation, contingency and backup evidence, and breach/incident logs. Build the submission as a single indexed package: a cover memo that lists every requested item, a file naming convention (for example, 01_RiskAnalysis_2026.pdf), and a cross-reference sheet mapping each request line to the file that answers it.
A practical response template for the cover memo has four parts: (1) entity identification and audit reference number, (2) a table of requested items with status (provided, partially provided with explanation, or not applicable with rationale), (3) the name and contact information of the audit coordinator, and (4) a statement that the submission is complete for the items listed. Keep the tone factual; do not volunteer material outside the request.
Stage 3: OCR review and follow-up
OCR reviews the package and may issue follow-up questions or a supplemental document request. Treat follow-ups as a signal of where the evidence was thin, and answer each question directly with the specific document or screenshot requested. If OCR asks for an interview, prepare the named staff member with the same mock-question discipline described later in this guide. Keep a running log of every question asked and every answer given so your responses stay consistent across the audit.
Stage 4: Preliminary findings and response
OCR shares preliminary findings and gives the entity an opportunity to respond before final findings issue. This is the stage where a well-organized corrective action plan pays for itself. For each finding, respond in three parts: what the requirement is, what evidence you have that addresses it (or an acknowledgment that it is a gap), and the remediation step with an owner and a completion date.
Stage 5: Final report and corrective action plan
OCR issues a final report. Significant deficiencies can lead to a corrective action plan (CAP) with defined milestones and reporting obligations. Treat the CAP as a project with a named owner, a milestone calendar, and evidence collection built into each milestone so completion is provable. Even when no CAP is imposed, fold the findings into your annual risk management cycle so the same gap does not reappear at the next review.
A working timeline to plan against
Use this as a planning skeleton, then adjust to the dates in your letter:
| Stage | Typical window | Owner |
|---|---|---|
| Notification and scope confirmation | First 2 business days | Audit coordinator |
| Document package assembly and submission | Per letter deadline (often measured in weeks, not months) | Compliance lead plus IT |
| OCR review and follow-up | Weeks after submission | Audit coordinator |
| Preliminary findings response | Per OCR-set window | Compliance lead with legal review |
| Final report and CAP (if any) | Per report | Executive sponsor |
Watch out: the most common process failure is not a missing control but a missed deadline caused by evidence scattered across EHR vendors, IT consultants, and paper files; assemble the package from one indexed location so the deadline is a packaging exercise, not a scavenger hunt.
Preparing Staff for Interviews and Mock Audits
Staff interviews are where paper policies meet daily practice. Auditors may ask a receptionist how they verify a caller before releasing records, or ask a clinician how they handle a lost laptop.
Run a mock audit at least once a year. Assign someone outside the compliance function to play the auditor, give them a short list of questions, and have staff answer as they would in a real review.
Prioritizing Remediation and Booking Your Readiness Review
Not every gap carries the same weight. Rank findings by risk to patient data and by the effort required to fix them.
Small practices often have limited staff, so focus on a short list of high-impact fixes rather than trying to close everything at once. To discuss your practice's compliance needs, you can schedule a free consultation.
Preparing for a HIPAA audit is less about a single scramble and more about keeping a defensible program current.
Frequently Asked Questions
What are the 5 basic rules of HIPAA?
HIPAA is commonly summarized through five core areas: the Privacy Rule, the Security Rule, the Breach Notification Rule, the Enforcement Rule, and the Omnibus Rule updates that expanded business associate obligations. For audit preparation, the Privacy, Security, and Breach Notification Rules matter most because auditors test whether your policies, safeguards, and incident procedures actually match what the regulations require. Start by confirming you know which rules apply to your practice or firm as a covered entity or business associate.
What are the 7 steps in the audit process?
A typical HIPAA audit follows a sequence: notification and document request, document review, onsite or remote fieldwork, stakeholder interviews, evidence analysis, preliminary findings, and a closing meeting with a final report. Knowing this sequence lets you assign owners to each phase before a notice arrives. Keep a timeline of when each document request is due so your team can respond within the windows the auditor sets.
What documents should you have ready for a HIPAA audit?
Auditors typically request your current risk analysis, risk management plan, written policies and procedures, workforce training records, access control and user permission lists, audit logs, business associate agreements, incident and breach logs, contingency and disaster recovery plans, and proof of sanction policy enforcement. Store each item in one shared, indexed location so you can produce it quickly. Date every version and record who approved it, since undated or unsigned documents are a frequent reason findings are raised.
How do you conduct a HIPAA risk analysis before an audit?
Inventory every system that creates, receives, maintains, or transmits electronic protected health information, including cloud services and vendor-hosted tools. Identify threats and vulnerabilities for each, rate the likelihood and impact of each risk, and document the existing controls. Then record a risk management plan that assigns owners and target dates to each gap. Update the analysis at least annually and after significant changes such as new software or a new location, and keep prior versions to show the process is ongoing.
How can staff prepare for HIPAA audit interviews?
Auditors often interview staff from front desk to IT to leadership, so each person should understand the policies that apply to their role and where to find them. Hold short training sessions that walk through common questions, such as how patient records are accessed, how a suspected breach is reported, and how workstations are locked. Run a mock interview with one or two people playing the auditor. Answer only what you know, say when you need to check a policy, and avoid guessing.
Who can audit covered entities for HIPAA compliance?
In the United States, the Office for Civil Rights at the U.S. Department of Health and Human Services conducts HIPAA compliance reviews and audits, and it can investigate complaints and breach reports. Some state attorneys general and certain contractors acting for federal agencies can also take enforcement action. Understanding who may be reviewing you helps you prepare appropriate evidence, but the core obligation is the same: show that your safeguards and documentation meet the regulations.
What is the difference between a HIPAA audit and a payer audit?
A HIPAA audit tests whether your privacy, security, and breach notification practices meet federal rules, and it is typically initiated by OCR. A payer audit reviews billing, coding, and claims against a health plan's contract terms and payment policies. The two can happen at the same time, but they use different evidence. Keep your compliance documentation and your billing records separate and easy to retrieve so each review can be answered on its own timeline.
How long should you keep HIPAA audit documentation?
HIPAA requires covered entities and business associates to retain required documentation, such as policies, risk analyses, and training records, for six years from the date of creation or the date it was last in effect, whichever is later. Keep audit logs, incident records, and business associate agreements on the same schedule. Set a retention reminder in your document system so older versions are archived rather than deleted, because auditors may ask for the version in force on a specific date.