A hospital is almost always a HIPAA covered entity: it furnishes care and conducts standard electronic transactions such as claims and eligibility checks. That part is not in doubt. What makes hospital compliance difficult is everything around it — the employed and affiliated physician groups, the joint arrangements with medical staff, the research institute, the foundation, the thousands of workforce members with some level of EHR access, and the network segments full of devices that were never designed with the Security Rule in mind.
Our HIPAA compliance consulting for hospitals starts by drawing the organization’s legal and technical boundaries accurately, because a risk analysis that covers the wrong scope cannot support defensible decisions. From there we focus on the areas where hospital risk concentrates and help leadership turn findings into a funded, sequenced plan.
Key points
- Confirm how affiliated entities are structured: single covered entity, affiliated covered entity, hybrid entity or OHCA participant.
- The enterprise-wide risk analysis under §164.308(a)(1)(ii)(A) must include medical devices, not just servers and laptops.
- EHR access reviews and audit-log monitoring are where hospital privacy incidents most often surface.
- An assessment prepares you for OCR scrutiny; it is not a government audit and cannot guarantee an outcome.
Start with structure: who is the covered entity?
Before anyone opens a vulnerability scanner, a health system needs a clear answer to a legal question: which entities are covered, and how do they relate to each other? HIPAA offers several organizational options, and the choice affects whose policies apply, who signs business associate agreements and how PHI may flow between entities. We work alongside your legal counsel on the interpretation; our role is to make sure the compliance program reflects the structure counsel confirms.
| Arrangement | What it means | Compliance implication |
|---|---|---|
| Affiliated covered entity (§164.105(b)) | Legally separate covered entities under common ownership or control designate themselves as a single covered entity | One set of policies and one designation document can apply across affiliates; the designation must be documented and retained |
| Hybrid entity (§164.105(a)) | A single legal entity with both covered and non-covered functions designates its health care components | Firewalls are required between health care components and the rest of the organization, such as a university or employer function |
| Organized health care arrangement (OHCA, defined at §160.103) | Clinically integrated settings, such as a hospital and its independent medical staff, where individuals expect joint care | Participants may share PHI for the joint arrangement’s operations and may use a joint notice of privacy practices under §164.520(d) |
| Separate covered entities | Affiliates operate independently for HIPAA purposes | Each needs its own program; sharing outside treatment, payment and operations needs a permitted basis |
Where PHI actually lives in a hospital
Hospitals rarely lack documentation. They usually lack an up-to-date inventory that connects systems to the PHI they hold and the people and vendors who can reach it. Our assessments build that map first, because NIST SP 800-66 Rev. 2 and HHS risk analysis guidance both treat identifying where ePHI is created, received, maintained and transmitted as the foundation of the analysis.
EHR and clinical applications
The EHR is the system of record, but PHI also sits in departmental systems — lab, pharmacy, radiology PACS, anesthesia, cardiology, oncology — plus interface engines and reporting databases. Role-based access is often broad by design so that clinicians can treat patients, which shifts the control burden to monitoring. Information system activity review under §164.308(a)(1)(ii)(D) and audit controls under §164.312(b) become the practical safeguard against snooping on employees, neighbors and VIP patients.
Medical devices and IoMT
Infusion pumps, imaging modalities, patient monitors and lab analyzers often store or transmit ePHI, run older operating systems and cannot be patched on the hospital’s schedule. They still fall within the scope of the risk analysis. Manufacturer disclosure documents such as the MDS2 form help, but the hospital must still decide how to segment, monitor and compensate for devices it cannot harden directly.
Third parties and patient-facing technology
Hospitals typically work with hundreds of vendors, from transcription and coding to cloud hosting and revenue cycle. Websites, portals and scheduling tools add another dimension: OCR has issued guidance on online tracking technologies, part of which a federal court vacated in 2024, so hospitals should review what their web analytics collect and verify the current state of that guidance with counsel.
Challenges we see repeatedly in hospital programs
- Risk analyses scoped to the IT department’s asset list, leaving out clinical engineering, research and affiliated practices.
- Risk registers with hundreds of open items and no clear owner, budget or target date — which undermines the risk management requirement in §164.308(a)(1)(ii)(B).
- Access provisioning that works well but de-provisioning that lags, especially for contracted staff, students and departed medical staff members.
- Business associate agreements that exist for the large vendors but not for smaller departmental purchases made outside procurement.
- Downtime and contingency procedures under §164.308(a)(7) that were written for a single system failure rather than an enterprise-wide ransomware event.
- Policies that cite the current rule correctly but do not match what units actually do on the floor.
How we tailor a hospital engagement
Hospital engagements are almost never a single deliverable. Most begin with an enterprise HIPAA security risk assessment scoped to include clinical devices and affiliates, followed by a HIPAA gap analysis of Privacy Rule processes such as right of access, minimum necessary and accounting of disclosures. Where third-party exposure is the main concern, we add a review of the vendor inventory and contracts through our business associate compliance work.
Findings feed a prioritized plan through HIPAA risk management support, with each item tied to an owner and a realistic timeline. Hospitals preparing for an OCR investigation, a payer review or a board-level question often finish with HIPAA audit readiness work, which assembles the documentation trail that §164.316 requires you to keep for six years.
What hospital leadership usually needs from us
Compliance officers, CISOs and general counsel often agree on the problems but need a shared, documented picture to prioritize them. We write findings so they can be read at three levels: a short board-ready summary of risk posture, a management view organized by owner and cost driver, and technical detail for the teams doing the work. That structure also makes it easier to show regulators how decisions were reached, which is what the documentation requirements are really testing.
A practical starting checklist for hospitals
- 1
Confirm the legal structure
Document whether you operate as a single covered entity, an affiliated covered entity, a hybrid entity or an OHCA participant, and confirm it with counsel.
- 2
Rebuild the ePHI inventory
Include clinical engineering’s device list, departmental applications, research data stores and cloud services — not just central IT assets.
- 3
Check the date and scope of your last risk analysis
If it predates major system changes, mergers or an EHR migration, it probably no longer reflects your environment.
- 4
Review EHR access monitoring
Confirm who reviews audit logs, how often, what triggers investigation and how sanctions under §164.308(a)(1)(ii)(C) are applied consistently.
- 5
Reconcile vendors against BAAs
Compare accounts payable and departmental purchasing data with your signed agreements to find vendors handling PHI without one.
- 6
Test enterprise downtime
Run a tabletop exercise assuming the EHR and imaging systems are unavailable for days, not hours.
Frequently asked questions
Does each hospital in our system need its own risk analysis?
Not necessarily. If affiliates are designated as an affiliated covered entity, an enterprise risk analysis can cover them, provided it actually assesses each location’s systems and threats. What matters is that the analysis is accurate and thorough for everything in scope.
Are medical devices really in scope for the HIPAA Security Rule?
If a device creates, receives, maintains or transmits ePHI, it belongs in the risk analysis. You may not be able to patch it, but you are expected to identify the risk and document how you manage it, for example through network segmentation and monitoring.
Can you tell us whether our physician group is part of an OHCA?
We can map the clinical and operational relationships and explain how the OHCA concept is typically applied, but the determination is a legal one. We work alongside your counsel so the compliance program reflects their conclusion.
Will your assessment satisfy an OCR investigation?
No consultant can promise that. A well-documented assessment and an active risk management plan are what OCR typically asks to see, and our work is designed to produce that evidence, but outcomes depend on your full program and the facts of any incident.
How long does a hospital engagement take?
It depends on the number of facilities, systems and affiliates in scope and how current your inventory is. We set the timeline during scoping, after reviewing your environment, rather than quoting a fixed duration up front.
Authoritative sources
- HHS — Guidance on Risk Analysis
- eCFR — 45 CFR Part 164
- NIST SP 800-66 Rev. 2
- HHS 405(d) Health Industry Cybersecurity Practices
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.