In a healthcare deal, the buyer acquires more than patients, staff and systems. It may also take on the target’s HIPAA problems: an outdated risk analysis, missing business associate agreements or a breach nobody has reported yet.
As auditors, we’ve seen compliance gaps surface months after closing, when they’re far more expensive to fix. This guide explains HIPAA compliance during mergers and acquisitions, from sharing PHI in due diligence to bringing the combined organization into compliance after closing.
Why HIPAA Matters in Healthcare Deals
When you acquire a covered entity or business associate, you generally inherit its compliance history. Past violations, open OCR investigations and undiscovered breaches can all become your responsibility.
The financial exposure is significant. For penalties assessed in 2026, HIPAA civil penalties range from $145 to more than $2.19 million per violation, depending on culpability, with annual caps per type of violation. Settlements also usually include multi-year corrective action plans.
Beyond penalties, HIPAA problems can affect the deal itself. They can change the price, require escrow or special indemnities, or delay integration while you fix them.
Sharing PHI During Due Diligence
Buyers often need to see some PHI to evaluate a deal, such as patient volumes, payer mix or quality data. The Privacy Rule allows this. Its definition of health care operations includes due diligence for a sale, transfer, merger or consolidation. That covers deals with another covered entity, or with an entity that will become one after the deal.
Even so, the minimum necessary standard still applies. In practice, that means:
- Start with de-identified data: Use summary or de-identified data wherever it answers the question.
- Limit who sees PHI: Restrict access to the deal team members who truly need it.
- Use a secure data room: Share files through a controlled platform with access logging, not email.
- Document what you shared: Keep a record of what PHI was disclosed, to whom and why.
Our article on the HIPAA minimum necessary rule explains the standard in detail. Also confirm the deal’s confidentiality terms cover PHI before any is shared.
What to Review in HIPAA Due Diligence
A focused HIPAA review looks at the target’s documents, practices and history. Here’s what we recommend requesting:
| Area | What to request | Red flags |
|---|---|---|
| Risk analysis | The most recent risk analysis and risk management plan | Older than a year or two, or covering only part of the environment |
| Policies | Privacy, security and breach notification policies | Generic templates that don’t match operations |
| Business associates | A list of vendors with PHI and their signed BAAs | Vendors handling PHI with no BAA |
| Breach history | Breach logs, incident reports and HHS submissions | Incidents investigated but never assessed as breaches |
| OCR history | Complaints, investigations and corrective action plans | Open investigations or unmet corrective action terms |
| Training | Training records for the workforce | Gaps in completion or no training at all |
| Technical safeguards | Evidence of encryption, MFA, logging and backups | Unencrypted laptops or no log review |
An independent HIPAA assessment of the target can answer many of these questions faster. Our guide to HIPAA risk analysis explains what a strong analysis looks like.
Planning the Transition of PHI
Integration is often when PHI is most at risk. Systems are migrated, access is reorganized and old platforms linger. A clear transition plan reduces that risk:
Our PHI inventory guide can help with the first step. Mapping the data early also makes your post-closing risk analysis much easier.
Business Associate Agreements and Vendors
Both organizations likely have business associate agreements with many vendors. After the deal, those agreements may need attention:
- Confirm assignment: Check whether each BAA can be assigned to the new entity or needs to be replaced.
- Consolidate vendors: Where both organizations use the same type of vendor, decide which relationship to keep.
- Fill gaps: Sign BAAs with any vendor that handles PHI and lacks one.
- Review downstream vendors: Confirm subcontractors that touch PHI also have agreements in place.
If the target is itself a business associate, review its customer BAAs too. Some include notice or consent requirements for a change of control. Our guide to HIPAA business associate responsibilities covers what these agreements must include.
Breach Risk During and After the Deal
Breaches can surface at any stage, including old incidents you only discover after closing. When one does, the Breach Notification Rule applies:
| Who to notify | When |
|---|---|
| Affected individuals | Without unreasonable delay, and no later than 60 days after discovery |
| HHS, for breaches of 500 or more people | At the same time as individual notice |
| Media, for 500 or more people in a state or jurisdiction | Within the same 60-day window |
| HHS, for breaches under 500 people | Within 60 days after the end of the calendar year |
So update your incident response plan for the combined organization early, and test it. See our guides to the HIPAA Breach Notification Rule and testing an incident response plan. HHS also explains the breach notification requirements on its website.
After Closing: Bringing the Combined Organization Into Compliance
HIPAA compliance during mergers and acquisitions doesn’t end at closing. In the first months, we recommend that you:
- Perform a new risk analysis: Cover the combined environment, not just each organization separately.
- Align policies: Adopt one set of HIPAA policies and retire conflicting ones.
- Update notices: Revise your notice of privacy practices if your practices materially change.
- Retrain the workforce: Train everyone on the combined policies and their responsibilities.
- Consider your structure: Legally separate covered entities under common control may be able to designate themselves as a single affiliated covered entity. Ask counsel whether that fits.
Several states also now require advance notice or review of certain healthcare transactions. Check those requirements with your counsel early in the deal. Our article on SOC 2 compliance during company breakups covers the reverse situation, when organizations separate.
Audit Peak performs independent HIPAA assessments for buyers, targets and newly combined organizations. We help you understand the HIPAA risk before closing and build a compliant program after it.