The short definition

Enacted 1996, expanded by HITECH 2009 and the Omnibus Final Rule 2013, HIPAA covers two domains: portability (continuity of insurance coverage) and accountability (privacy and security of health information). The Privacy Rule defines who can access PHI and under what conditions; the Security Rule mandates safeguards on electronic PHI (ePHI). Enforcement runs through the HHS Office for Civil Rights (OCR), which audits covered entities and pursues settlements after breaches.

For security integrators, HIPAA shows up in three places: camera placement and access control at healthcare facilities, BAA execution with cloud video and access vendors, and breach notification when an incident exposes PHI.

The Security Rule's three categories

  • Administrative safeguards. Risk analysis, workforce training, access management, contingency planning, audit controls. Camera and access-control system administration falls here.
  • Physical safeguards. Facility access controls, workstation security, device and media controls. Cameras and badge readers are physical safeguards. Camera placement decisions, retention, and access to footage are governed under this category.
  • Technical safeguards. Encryption, access controls on data, audit controls, integrity monitoring, transmission security. Cloud video platforms must encrypt footage at rest and in transit; on-prem VMS deployments must enforce role-based access on user logins.

Camera placement at healthcare facilities

Five rules of thumb that keep camera deployments HIPAA-defensible.

  • Avoid patient-care areas. Exam rooms, ICU bedside, surgical suites, mental-health treatment areas. Common areas (waiting rooms, hallways, parking lots) carry far less PHI exposure.
  • Mask the screen-capture problem. Cameras pointed at workstations can record EHR screens. Re-aim the camera or mask the screen region in the VMS.
  • No microphones in PHI zones. Audio of patient conversations is a HIPAA risk multiplier. Disable camera audio wherever PHI conversations occur.
  • Restrict access to footage. Role-based VMS access. Security operators see camera live; clinical staff have no VMS access. Audit-log every export.
  • Document the design in the HIPAA risk assessment. Annual or biennial. Justifies each camera's placement and the PHI exposure considered.

See the hospital security AI entry for the analytics-layer angle.

BAA requirements and vendor selection

Any vendor whose service might handle PHI must sign a BAA. For commercial security:

  • Cloud VMS vendors. Verkada, Eagle Eye Networks, Avigilon Alta, Genetec Stratocast all sign BAAs. Confirm in writing before deployment.
  • Cloud access-control platforms. Brivo, Avigilon Alta Access, Verkada Access. BAA required if logs include PHI-related access events.
  • Verified monitoring services. Central station agents may see PHI in dispatch footage. BAA required.
  • Integrators (Tec-Tel and peers). If we touch the system, we sign a BAA. Standard practice.

Penalties and recent enforcement

HIPAA penalties tier by culpability:

  • Tier 1: did not know. $137 to $68,928 per violation, capped at $2,067,813 per year per identical provision (2024 adjusted figures).
  • Tier 2: reasonable cause. $1,379 to $68,928 per violation, same annual cap.
  • Tier 3: willful neglect, corrected. $13,785 to $68,928 per violation, same cap.
  • Tier 4: willful neglect, uncorrected. $68,928 per violation, capped at $2,067,813 per year.

OCR settlements have ranged from $25K to over $115M. The willful-neglect tier hits hardest at organizations that ignored repeated audit findings or skipped the HIPAA risk assessment.

When to ask Tec-Tel about HIPAA-compliant security

Healthcare security designs land or fall on the HIPAA risk assessment. We'll walk a facility, scope the camera and access plan with HIPAA in mind, sign the BAA, and document the placement decisions for the audit. Free scoping call.