In short
- A HIPAA audit by HHS's Office for Civil Rights is first a document review: in the Phase 2 desk audits, selected entities had 10 business days to upload policies, procedures and evidence that they were followed.
- The Security Rule controls tested in those desk audits were risk analysis and risk management, and OCR's 2024 to 2025 audits of 50 covered entities and business associates again focus on selected Security Rule provisions.
- The practical checklist is evidence you can find today: a dated risk analysis, a risk management plan that traces to it, log reviews, signed business associate agreements and six years of documentation.
A HIPAA audit is a compliance review run by the Office for Civil Rights (OCR) at the US Department of Health and Human Services. In practice it starts as a document request. OCR emails the selected organization, asks for specific policies, procedures and proof that they were followed, and reviews what comes back. In OCR's Phase 2 desk audits, the analysis was based only on the documents submitted in response to that request, and entities had 10 business days to respond. If your evidence already exists and you can find it, an audit is manageable. If it lives in people's heads, ten business days is not enough time to write it down.
Product, engineering and compliance leads can prepare before any letter arrives: learn which controls the program has looked at, know what a risk analysis needs to show, and keep the evidence on the checklist below up to date.
Who gets a HIPAA audit, and is it an enforcement action?
HIPAA audits cover two groups: covered entities (health care providers, health plans and clearinghouses) and their business associates, meaning vendors that handle protected health information on a covered entity's behalf. A software company that hosts or processes patient data for a clinic is usually a business associate.
OCR has run the program in phases. The first, in 2011 and 2012, was a set of comprehensive on-site audits of 115 covered entities. Phase 2, presented by OCR in October 2016, included both covered entities and business associates, with over 200 desk audits and a smaller number of comprehensive on-site audits. To pick covered entities, OCR built pools by size, affiliation, location, public or private status and provider type, then ran a randomized selection algorithm that produced 167 covered entities. The business associate pool came largely from lists the covered entities supplied; OCR said those lists identified over 20,000 business associates.
OCR described the audits as primarily a compliance improvement activity, used to understand how organizations comply and to decide what guidance and technical assistance to build. It also said it would not post a list of audited entities or entity-identified findings. That does not make an audit risk free. OCR stated that, under its separate authority to open compliance reviews, it could open a review if an audit revealed significant threats to the privacy and security of health information.
The program is active again. In its 2024 to 2025 audits, OCR said it would review 50 covered entities and business associates for compliance with selected Security Rule provisions. In the same period OCR ran a Risk Analysis Initiative, launched under director Melanie Fontes Rainer, to put a spotlight on the Security Rule's risk analysis requirement.
What happens, step by step, in a HIPAA desk audit?
The Phase 2 desk audit is the best documented version of the process. OCR's own description of it ran like this:
- Notification by email. The selected entity received two separate requests: one listing the policies, procedures and other documentation to provide, and one asking for a list of all its business associates.
- The business associate list was due back by email within 10 business days. Everything else went through a secure online portal linked in the notification.
- Entities had 10 business days to respond with the specified documentation: policies, procedures and evidence of implementation. OCR asked for complete and relevant material and warned against superfluous documents. Uploads had a 10MB file size limit.
- OCR reviewed the submission and shared draft findings by email.
- The entity could respond to the draft findings within 10 days. Written responses were included in the final report.
- The final audit report described how the audit was conducted, presented any findings and contained the entity's responses.
- On-site audits came later and evaluated auditees against a comprehensive selection of controls in the audit protocol. A desk audit subject could also be picked for an on-site audit.
For a software organization, the timeline is short and the request is specific. OCR asks for named documents and proof that they were used, and a walkthrough of your architecture will not stand in for them.
Which HIPAA rules and controls does an audit check?
Phase 2 desk audits were limited to seven controls drawn from the Privacy, Security and Breach Notification Rule protocols. Covered entities were audited either on Security Rule controls or on Privacy and Breach Notification controls. Business associates were audited on security and breach notification.
- Privacy Rule: notice of privacy practices and its content (§164.520(a)(1) and (b)(1)).
- Privacy Rule: provision of the notice electronically (§164.520(c)(3)).
- Privacy Rule: the individual's right of access to their records (§164.524).
- Breach Notification Rule: timeliness of notification (§164.404(b)).
- Breach Notification Rule: content of notification (§164.404(c)(1)).
- Security Rule: security management process, risk analysis (§164.308(a)(1)(ii)(A)).
- Security Rule: security management process, risk management (§164.308(a)(1)(ii)(B)).
The two Security Rule controls are the ones software teams own most directly, and they are also the subject of OCR's later Risk Analysis Initiative. On-site audits go wider and use the full protocol.
The full Security Rule is organized into administrative, physical and technical safeguards, plus requirements for business associate contracts and for policies and documentation. Each standard may have implementation specifications, which are either required or addressable. Addressable does not mean optional. To meet an addressable specification you assess whether it is reasonable and appropriate in your environment. If it is, you implement it. If it is not, you document why and implement an equivalent alternative measure. Either way, the assessment and the decision must be documented. Encryption of data at rest and in transit are both addressable specifications, which is why an auditor will look for that written decision.
What does a HIPAA risk analysis need to show an auditor?
The Security Rule requires an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of electronic protected health information (ePHI). OCR does not prescribe a methodology. The most practical public reference is NIST Special Publication 800-66 Revision 2, published in February 2024, which lists key activities and sample questions for every Security Rule standard. For risk analysis, its questions include:
- Has all ePHI that the organization generates, stores, processes and transmits been identified, including where it enters, moves within and leaves the organization?
- Is the inventory of hardware and software that holds or transmits ePHI updated regularly, including removable media and remote access devices?
- Is the current configuration of systems documented, including connections to other systems?
- What are the human, natural and environmental threats to those systems, and what are the current and planned controls?
- Have likelihood, impact and risk ratings been determined for the relevant threats and vulnerabilities?
- Is there an analysis of current safeguards and how effective they are against the identified risks?
Risk management is the second half. The Security Rule requires security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level. NIST's sample questions ask whether leadership takes part in risk decisions, whether a risk management program with its own policy exists, and whether the results of the risk analysis were actually used to choose controls. A list of risks with no plan attached answers only half the question.
Smaller providers can start with the Security Risk Assessment Tool from the Office of the National Coordinator for Health IT, built with OCR. Its disclaimer says the tool is aimed at small and medium providers, may not suit larger organizations, and using it is neither required by nor a guarantee of compliance.
HIPAA audit checklist for software and product teams
Each item below maps to a Security Rule standard as described in NIST SP 800-66r2. The point is to have the evidence on file, dated and findable, before anyone asks.
- ePHI inventory and data-flow diagram for every system, including logs, backups, analytics tools and AI vendors.
- A dated risk analysis with likelihood, impact and risk ratings, updated when systems or vendors change.
- A risk management plan that traces each mitigation back to a risk in the analysis, with an owner and a date.
- Written decisions for every addressable specification, including encryption at rest and in transit.
- Audit controls: a decision on which activities are logged (creating, accessing, modifying, transmitting and deleting ePHI) and what each record contains, such as the user, event type, date and time.
- Information system activity review: a policy and procedure for regularly reviewing audit logs, access reports and security incident tracking, plus evidence that the reviews happened.
- Access control: unique user identification and an emergency access procedure (both required), automatic logoff (addressable).
- Business associate agreements with every vendor that creates, receives, maintains or transmits ePHI for you, and agreements between business associates and their subcontractors.
- A sanction policy for workforce members who break security policy, and records of how it has been applied.
- A contingency plan covering backup, disaster recovery and emergency operation.
- Documentation kept for six years from the date it was created or last in effect, whichever is later, and available to the people who carry out the procedures.
- For covered entities: the notice of privacy practices, a working right-of-access process and breach notification procedures.
What should engineering own, and what should compliance own?
Compliance leads usually own policies, risk decisions and the response to OCR. Engineering owns the evidence that those policies run: system inventories, architecture and data-flow diagrams, log configuration, access lists, change records and security test reports. Audits get hard when the two sets of documents disagree, for example when the policy says access is reviewed quarterly and the access list has no review dates.
On the engineering side, some habits produce evidence as a by-product. On our projects we sign a business associate agreement before we touch any PHI, we run penetration tests before launch, and we design access so that each clinician sees only their own patients. Each of those leaves a document or a configuration a customer can put straight into their risk analysis and audit file.
How should you respond if an audit letter arrives?
- Read the request line by line and answer exactly what it asks. OCR asked Phase 2 auditees not to send superfluous material.
- Name one owner and keep one evidence folder, so nothing is sent twice or contradicts itself.
- Start with the business associate list. In Phase 2 it was due by email within the same 10 business days, and it is often the hardest list to assemble.
- Do not backdate anything. A dated document is evidence; a policy written the week the letter arrived shows exactly that.
- Use the draft findings window. In Phase 2 entities had 10 days to respond, and the response went into the final report.
Want a second pair of eyes on your evidence?
Onix Systems has built software since 2000 and has 370+ engineers. If you want to know where your product's HIPAA evidence is thin before an auditor does, talk to one of our engineers. We offer a 5-day free technical audit that ends with a written report you can hand to your compliance lead.
Sources
- OCR: HIPAA Privacy, Security and Breach Notification Compliance Audits, Phase 2 (October 2016)
- NIST SP 800-66 Rev. 2: Implementing the HIPAA Security Rule, A Cybersecurity Resource Guide
- TechTarget: How HHS enforces the HIPAA Security Rule and Privacy Rule (February 2025)
- HealthIT.gov: Security Risk Assessment Tool