When OCR opens an investigation or sends a data request, the first question is rarely “Are you secure?” It is “Show us.” Organizations that have done reasonable compliance work still struggle when the risk analysis is three versions out of date, BAAs are scattered across inboxes, and training records live in a former employee’s spreadsheet.
Audit readiness is about being able to produce accurate, current evidence of your HIPAA program on short notice. We help you assemble it, test it with a mock request, and keep it maintained.
Key points
- We prepare you for audits and investigations — we do not conduct government audits.
- Focus is on documentation and evidence, not just controls.
- A mock document request reveals what you cannot produce before a regulator does.
- Readiness also helps with customer audits, insurer questionnaires and due diligence.
Service overview
Audit readiness sits between assessment and response. It assumes some compliance work exists and asks whether it is documented, current and retrievable. We review your documentation set, identify missing or outdated items, run a mock request and help you build an evidence library organized by HIPAA requirement.
Who needs audit readiness
- Organizations that have reported a breach affecting 500 or more individuals, which HHS posts publicly and which commonly prompts OCR review.
- Organizations that have received a patient complaint or an OCR data request.
- Hospitals and health systems preparing for internal audit, accreditation-related reviews or board scrutiny.
- SaaS vendors and business associates facing customer audits or security reviews — see HIPAA consulting for SaaS companies.
- Any organization that wants confidence it could respond quickly and accurately if asked.
Regulatory considerations
OCR’s oversight takes several forms, and readiness looks slightly different for each.
| Type | What triggers it | What readiness means |
|---|---|---|
| Complaint investigation | A complaint filed with OCR by a patient, employee or other party | Ability to explain and evidence how you handled the specific issue and the related policies |
| Compliance review | Often a breach report or other information OCR receives | Current risk analysis, risk management, policies and incident documentation available promptly |
| OCR audit program | Selection under an OCR audit initiative; OCR has run audit phases in the past, most notably 2016–2017 | Organized evidence for the protocol areas OCR selects; verify whether an audit cycle is currently active |
| Customer or partner audit | Contract terms, procurement or vendor risk programs | Evidence package mapped to customer questions, with clear distinction between HIPAA and contractual requirements |
Common readiness challenges
- The risk analysis exists but the risk management plan showing what was done about it does not.
- Policies are current, but prior versions were not retained — §164.316(b) and §164.530(j) require six-year retention.
- BAAs cannot be located for some vendors, or were signed on outdated templates.
- Training completion cannot be shown for specific workforce members or dates.
- Breach risk assessments for incidents that were judged “not a breach” were never written down.
- Nobody is designated to coordinate a response, so requests bounce between departments.
Our approach
We use the published OCR audit protocol and the structure of 45 CFR Part 164 as a reference for which documents an inquiry may cover. We focus on the core items that come up repeatedly in OCR enforcement: an accurate and thorough risk analysis, evidence of risk management, policies and procedures, workforce training, business associate agreements, access and activity review, and incident and breach documentation.
Mock document request
We issue a realistic request for a defined set of documents and evidence with a deadline, then review what comes back for completeness, currency and consistency. This tests both the evidence and your internal process for producing it. A typical mock request draws on items such as:
- Current and prior versions of the risk analysis, with the risk management plan and status of remediation.
- Security and privacy policies and procedures, with version history covering the retention period.
- Training materials and completion records for a sample of workforce members.
- Business associate inventory and executed BAAs for a sample of vendors.
- Evidence of information system activity review, such as audit log review records.
- Incident log and breach risk assessments, including incidents determined not to be reportable breaches.
- Records of individual access requests and response dates.
Evidence library
We help you organize evidence by requirement, with an owner and review date for each item, so readiness does not decay after the engagement. Our HIPAA compliance audit checklist shows the kind of structure we use.
Typical deliverables
- Documentation inventory mapped to HIPAA standards, with status for each item.
- Mock request results and a list of items that were missing, outdated or inconsistent.
- Prioritized action list to close evidence gaps, labelled required or recommended.
- Response playbook: who coordinates, who approves, how documents are reviewed before release, and when to involve legal counsel.
- Evidence library structure and maintenance calendar.
Engagement process
- 1
Context call
We learn whether there is an active inquiry, a known trigger or a general readiness goal, and confirm whether counsel is involved.
- 2
Documentation review
We review the existing documentation set against the requirements in scope.
- 3
Mock request
We issue a mock document request and assess the response and the internal process behind it.
- 4
Close evidence gaps
We help update or create missing documents and records; deeper program gaps may be referred to remediation.
- 5
Playbook and library
We finalize the response playbook and evidence library so the organization can maintain readiness.
Cost factors
Costs depend on whether there is an active OCR matter with a deadline, the number of requirements and entities in scope, the state of current documentation, and how much drafting is needed to fill gaps. If significant program gaps appear, the readiness work is often combined with a HIPAA gap analysis or compliance remediation. Engagements tied to an active investigation are coordinated with your legal counsel.
Frequently asked questions
Can you represent us in an OCR investigation?
We are not a law firm and do not provide legal representation. During an active matter we work alongside your legal counsel, helping assemble documentation and explain technical and operational facts.
Will audit readiness prevent an OCR investigation?
No. OCR may open an investigation based on complaints, breach reports or other information regardless of your preparation. Readiness helps you respond accurately and promptly and shows a functioning compliance program.
Is OCR currently auditing organizations?
OCR has operated audit programs in the past and has indicated interest in continuing them. The status changes over time, so check OCR’s compliance and enforcement pages for current information.
What is the most common missing document?
Evidence of risk management — what the organization actually did about the risks identified in its analysis — is often thinner than the analysis itself. OCR resolution agreements frequently cite failures in both risk analysis and risk management.
How long must we keep HIPAA documentation?
Policies, procedures and required documentation must be retained for six years from the date of creation or the date last in effect, whichever is later (§164.316(b)(2) and §164.530(j)(2)). State law may impose different retention periods for medical records themselves.
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.