The HIPAA Security Rule does not name products. It sets outcomes, and expects each practice to decide how to meet them based on a documented risk analysis. These are the technical safeguards (45 CFR §164.312) in plain English.
The five technical safeguards
- Access control. Unique logins for every person (no shared front-desk accounts), an emergency access procedure, automatic logoff on idle workstations, and encryption where appropriate.
- Audit controls. Systems that record who accessed patient data and when, and someone who actually reviews those logs.
- Integrity. Protection against patient data being altered or destroyed improperly, including reliable, tested backups.
- Person or entity authentication. Proof that people are who they say they are. In practice that means strong passwords and multi-factor authentication.
- Transmission security. Protecting data in transit: encrypted email for patient information, secure remote access and no unencrypted file transfers.
The parts practices most often miss
- The risk analysis. Required under the administrative safeguards, and the first thing investigators ask for after a breach. It must be documented and kept up to date.
- Business associate agreements (BAAs) with every vendor that handles patient data: your EHR, email provider, backup service and IT provider.
- Laptops and phones. Full-disk encryption on every device that might hold patient data. An encrypted lost laptop is usually not a reportable breach; an unencrypted one is.
No one can sell you "HIPAA compliance" in a box. What we do is implement and document these safeguards and support your risk analysis: see IT for healthcare and cybersecurity.