Compliance · HIPAA
HIPAA: who touched patient data, and where it went.
The HIPAA Security Rule asks you to control access to electronic protected health information and record what happens to it. GuardStance supports these safeguards with technical controls.
Book a demoWhich safeguards does GuardStance support?
| Requirement | What it asks | How GuardStance supports it |
|---|---|---|
| §164.308(a)(1)(ii)(D) | Information system activity review: regularly review records such as audit logs and access reports. | Case timelines and reports show activity on patient data. |
| §164.312(a)(1) | Access control: limit systems holding ePHI to people and software with access rights. | Policies by user and group decide who can move patient data, and where. |
| §164.312(b) | Audit controls: record and examine activity in systems that hold or use ePHI. | Every sharing attempt is recorded with the user, the file and the destination. |
| §164.312(e)(1) | Transmission security: guard against unauthorized access to ePHI sent over networks. | Email, web and cloud uploads of patient data are checked before they leave. |
GuardStance supports these requirements with technical controls. This is not legal advice; confirm legal questions with your counsel.