164.308(a)(4)(ii)(A) Isolating Health Care Clearinghouse Functions (Required if applicable)
If a clearinghouse is part of a larger organization, isolate ePHI from the larger organization. NIST recommends network segmentation and separate access domains.
Source: HIPAA Security Rule, 164.308(a)(4)(ii)(A). The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open HIPAA Security Rule in the compliance library.
Applies to covered entities and business associates. An addressable specification can be met by a documented, reasonable alternative.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Firewall rules separating clearinghouse · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Network segmentation design · Policy repository / GRC workspace
- Clearinghouse isolation policy · Policy repository / GRC workspace
- Access boundary documentation · Policy repository / GRC workspace
First move
Common gaps auditors find
- Logical isolation incomplete
- Shared administrative accounts cross boundary
- No periodic isolation verification
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet164.308(a)(4)(i) Information Access Management (Standard) · 164.308(a)(4)(ii)(B) Access Authorization (Addressable)