Skip to content
HIPAA ComplianceConsulting

HIPAA Resource

HIPAA Compliance Audit Checklist: Preparing for OCR and Internal Audits

What to gather, how to organize evidence and how to prepare people before an OCR data request or an internal HIPAA compliance audit.

6 min read Reviewed

Most organizations first think seriously about audit readiness when a letter arrives from the HHS Office for Civil Rights (OCR) — usually after a complaint or a reported breach. At that point the question is not whether you have a HIPAA program, but whether you can prove it with dated, organized documentation within the deadline in the data request.

This checklist is built for that moment and for the calmer one before it: an internal audit you run on your own schedule. It covers the document inventory, the evidence that shows policies are actually followed, and how to prepare the people who will be interviewed. It is a preparation aid, not legal advice; when OCR is involved, coordinate your response with qualified legal counsel.

Key points

  • An internal audit or consultant assessment is not a government audit and cannot certify compliance — HIPAA has no official certification.
  • OCR asks for evidence: dated risk analyses, risk management plans, policies, training records, BAAs and logs.
  • 45 CFR §164.316 requires documentation to be retained for six years from creation or last effective date.
  • The single most commonly scrutinized document is the enterprise-wide risk analysis under §164.308(a)(1)(ii)(A).

Internal audit vs. OCR investigation vs. compliance review

The word "audit" is used loosely. It helps to be precise about which situation you are preparing for, because the stakes, the audience and the timeline differ.

Three situations people call a HIPAA audit
SituationWho runs itTypical triggerWhat it can and cannot do
Internal audit or assessmentYour compliance team or an outside consultant you engagePlanned program review, new leadership, customer request, pre-acquisition diligenceFinds gaps and builds a remediation plan; it is not a regulatory finding and does not certify compliance
OCR complaint investigationHHS Office for Civil RightsA complaint from a patient, employee or other personRequests documents and explanations; may close with technical assistance, a resolution agreement or penalties
OCR compliance reviewHHS Office for Civil RightsOften a breach report (especially 500+ individuals) or other information OCR receivesExamines whether the breach reflects broader compliance failures, frequently starting with the risk analysis

Step 1: Build the document inventory

Start by listing what exists, where it lives, who owns it and when it was last reviewed. Missing dates and missing owners are among the most common problems we see during HIPAA audit readiness work. Group the inventory by rule so gaps are easy to spot.

Security Rule documentation

  • Current, enterprise-wide risk analysis covering all ePHI the organization creates, receives, maintains or transmits — §164.308(a)(1)(ii)(A)
  • Risk management plan showing how identified risks are being reduced, with owners and dates — §164.308(a)(1)(ii)(B)
  • Information system activity review procedures and evidence of review — §164.308(a)(1)(ii)(D)
  • Security policies covering administrative, physical and technical safeguards (§164.308, §164.310, §164.312)
  • Documentation of decisions on addressable specifications, including any equivalent alternative measures
  • Contingency plan: data backup, disaster recovery, emergency mode operations — §164.308(a)(7)
  • Periodic evaluation records — §164.308(a)(8)

Privacy Rule and breach documentation

  • Notice of Privacy Practices and evidence of distribution and posting (covered entities)
  • Privacy policies and procedures, including patient right of access handling — §164.524 and §164.530(i)
  • Designation of privacy and security officials — §164.530(a) and §164.308(a)(2)
  • Complaint log and sanctions records — §164.530(d) and (e)
  • Breach risk assessments and notifications, including incidents determined not to be breaches — §164.400–414

Business associate and workforce records

  • Inventory of business associates and signed BAAs — §164.308(b), §164.314(a), §164.504(e)
  • Training materials, attendance records and dates — §164.308(a)(5) and §164.530(b)
  • Workforce access authorization and termination procedures with sample evidence

Step 2: Collect evidence that the program operates

A binder of policies proves only that policies were written. Investigators and good internal auditors look for evidence that the organization follows them. For each key policy, pick a small sample and pull proof.

Policy-to-evidence mapping examples
Policy areaEvidence that it operates
Access managementAccess requests and approvals; termination tickets matched against account deactivation dates
Audit controls (§164.312(b))Log sources enabled for EHR and key systems; records of periodic log review
Workforce trainingCompletion reports by person and date; content showing the topics covered
Risk managementRemediation tracker with closed items, dates and owners; leadership sign-off
Business associatesVendor inventory reconciled with BAAs; due diligence notes for new vendors
Right of accessRequest log showing dates received and fulfilled, and any denials with reasons
Incident responseIncident tickets, investigation notes and breach risk assessment outcomes

Step 3: Prepare for interviews

OCR investigators and internal auditors often speak with the privacy official, the security official, IT leadership and front-line staff. The goal of preparation is accuracy, not scripting. People should describe what actually happens and know where the supporting documents are.

  • Confirm who the designated privacy and security officials are and that they can explain their responsibilities.
  • Walk the security official through the most recent risk analysis: scope, methodology, top risks and what has been done since.
  • Ask IT to explain how access is granted, reviewed and removed, and how logs are monitored.
  • Ask front-desk or operations staff how they verify identity, handle record requests and report a suspected incident.
  • Agree on a single point of contact for document production and on who coordinates with legal counsel.
  • Instruct people not to guess; "I'll confirm and follow up" is a better answer than an inaccurate one.

Step 4: Run the internal audit

  1. 1

    Define scope

    Name the entities, locations, systems and time period in scope. Include business associate relationships, not just internal systems.

  2. 2

    Gather the inventory

    Collect the documents listed above with dates, versions and owners. Note anything missing rather than recreating it on the spot.

  3. 3

    Test a sample

    For each control area, test a handful of real records — new hires, terminations, access reviews, incidents — against the written policy.

  4. 4

    Interview key roles

    Confirm that practice matches policy and that responsibilities are understood.

  5. 5

    Rate findings

    Rank gaps by risk to ePHI and regulatory exposure. A missing or stale risk analysis typically ranks at the top.

  6. 6

    Build the remediation plan

    Assign owners and target dates, and track to closure. Feed results into your HIPAA risk management process.

Common gaps that surface during reviews

Many of these overlap with the items on our broader HIPAA compliance checklist and the more technical HIPAA risk assessment checklist.

  • A risk analysis that covers only the EHR and ignores email, file shares, cloud apps, mobile devices and backups.
  • A risk analysis that is years old and was never updated after new systems or locations were added.
  • Risks identified but no documented risk management plan showing what was done about them.
  • Addressable specifications treated as optional with no documented reasoning — "addressable" requires an assessment and a documented decision.
  • Vendors that handle PHI with no signed BAA, or BAAs that cannot be located.
  • Training records with no dates, or training that was never repeated.
  • Right-of-access requests answered late or with unreasonable fees.

If you receive an OCR data request

  • Read the request carefully and log every item requested, with the deadline.
  • Produce what exists; do not backdate or fabricate documents. Documents created after the request should be clearly dated as such.
  • If the honest answer is that something was not done, remediation already under way is worth describing accurately.
  • Keep a copy of everything produced and a record of what was sent and when.

After the audit: keep it current

Audit readiness decays. Policies age, systems change and staff turn over. Organizations that stay ready usually schedule an annual internal review, update the risk analysis when the environment changes, and keep a living evidence folder rather than assembling one under pressure. Some choose ongoing HIPAA compliance support to keep that cadence.

Frequently asked questions

Is an internal HIPAA audit the same as an OCR audit?

No. An internal audit or consultant assessment is a private review you commission to find gaps. An OCR investigation or compliance review is conducted by the government and can result in corrective action or penalties. A clean internal audit does not certify compliance or bind OCR.

What document does OCR most often ask for first?

The risk analysis required by §164.308(a)(1)(ii)(A) is commonly among the first items requested, along with the risk management plan, policies and procedures, training records and business associate agreements. The exact list depends on the request.

How long do we need to keep HIPAA documentation?

Required documentation must be retained for six years from the date of creation or the date it was last in effect, whichever is later, under §164.316(b)(2) for the Security Rule and §164.530(j) for the Privacy Rule. State law or other obligations may require longer retention.

Can a consultant guarantee we will pass an OCR investigation?

No. Nobody can guarantee an investigation outcome. A consultant can help you identify gaps, organize evidence and remediate issues, which improves your position, but OCR makes its own determinations.

How often should we run an internal HIPAA audit?

HIPAA does not set a fixed audit interval, but §164.308(a)(8) requires periodic technical and non-technical evaluation, and the risk analysis must be kept current. Many organizations review annually and after significant operational or technology changes.

Authoritative sources

This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.

Talk through your HIPAA obligations with a consultant

Tell us about your organization, how you handle patient information, and what’s prompting the review. We’ll suggest a practical scope — and tell you if you don’t need us.