HIPAA
Compliance

Meet all HIPAA Security Rule, Privacy Rule, and Breach Notification Rule obligations, ensuring Protected Health Information (PHI) remains protected across your covered entity or business associate organisation.

Security Risk Analysis BA Agreements 60-Day HHS Notification Admin + Physical + Technical
PHI Access Monitor
Encryption
AES-256
Access
RBAC
Audit
Active
Backup
Daily
Administrative SafeguardsCompliant
Physical SafeguardsCompliant
Technical SafeguardsCompliant
Breach Notification ProtocolReview
Business Associate AgreementsActive
HIPAA
PHI Secured
BAA Ready
ePHI OK

HIPAA That Withstands OCR Investigation

HIPAA compliance requires administrative, physical, and technical safeguards for electronic PHI (ePHI) and documented proof that they work. The HHS Office for Civil Rights has levied over $130M in penalties since 2016. Our programme is designed to produce the documented evidence that OCR investigators look for: a completed Security Risk Analysis, documented risk treatment, trained workforce, and a tested breach notification procedure.

Security Risk Analysis (SRA)

Complete the mandatory SRA per 45 CFR 164.308(a)(1)(ii)(A), identifying and assessing risks to ePHI across all systems.

BAA Programme

Review, remediate, and track BAAs with every vendor handling PHI per 45 CFR 164.502(e) and 164.314(a)(2).

Technical Safeguards

Assess access controls, audit logging, automatic logoff, ePHI encryption, and integrity controls per 45 CFR 164.312.

Administrative Safeguards

Assess workforce security, information access management, training, contingency planning, and evaluation per 45 CFR 164.308.

Physical Safeguards

Assess facility access controls, workstation security, and device/media controls per 45 CFR 164.310 across all ePHI locations.

Breach Notification

Implement 60-day breach notification per 45 CFR 164.408 to HHS and affected individuals, with media notification thresholds.

ePHI Encryption Deployment

Implement ePHI encryption at rest and in transit per 45 CFR 164.312(a)(2)(iv) and 164.312(e)(1) across all systems and backups.

Access Control Configuration

Deploy RBAC, unique user IDs, emergency access, and automatic logoff per 45 CFR 164.312(a)(1) for all ePHI systems.

Audit Logging Setup

Implement audit logging per 45 CFR 164.312(b) covering login events, PHI access, modifications, and disclosures with tamper-resistant storage.

Workforce Training Programme

Deploy role-based HIPAA training per 45 CFR 164.308(a)(5) covering PHI handling, security awareness, and sanctions for violations.

Contingency Planning

Develop and test contingency plans per 45 CFR 164.308(a)(7) including data backup, DR, emergency mode operations, and testing procedures.

Device and Media Controls

Implement disposal and reuse policies per 45 CFR 164.310(d) for electronic media containing ePHI, including data wiping and accountability.

Annual SRA Update

Update SRA per 45 CFR 164.308(a)(1)(ii)(A) reflecting new systems, changed environments, and emerging threats.

BAA Review and Tracking

Ongoing BAA review and tracking per 45 CFR 164.314(a)(2), monitoring vendor compliance, renewals, and new vendor onboarding.

Security Awareness Refresher

Annual security awareness refresher per 45 CFR 164.308(a)(5) with phishing simulation and scenario-based PHI handling drills.

Breach Notification Drills

Periodic tabletop exercises testing 60-day HHS notification per 45 CFR 164.408 with documented outcomes.

Policy and Procedure Review

Annual review of HIPAA policies and procedures reflecting regulatory changes, OCR enforcement, and operational changes.

OCR Investigation Preparation

Maintain investigation-ready documentation: SRA results, risk treatment plans, training records, BAA inventory, and breach response evidence.

Does HIPAA Apply to Your Organisation?

Covered Entities

Healthcare providers (hospitals, clinics, physicians), health plans, and healthcare clearinghouses that create, receive, maintain, or transmit PHI must comply with all HIPAA Rules.

Healthcare Technology (Business Associates)

EHR vendors, telehealth platforms, healthcare data analytics companies, billing services, and any IT provider accessing PHI on behalf of a covered entity is a HIPAA Business Associate.

Cloud Providers Serving Healthcare

AWS, Azure, GCP and other cloud providers serving healthcare customers execute BAAs, but SaaS companies built on cloud who process PHI must implement their own HIPAA controls.

How We Build Your HIPAA Compliance Programme

A structured six-phase process from the mandatory Security Risk Analysis through to ongoing compliance maintenance and OCR investigation readiness.

Phase 01
Security Risk Analysis (SRA)

Complete the mandatory SRA: threat, vulnerability, and risk assessment across all ePHI systems, identifying gaps and producing a prioritised risk treatment plan.

01
02
Phase 02
Administrative Safeguard Implementation

Implement administrative safeguards including workforce security, information access management, security awareness training, contingency planning, and evaluation programmes.

Phase 03
Technical Safeguard Deployment

Deploy technical safeguards including access controls, audit logging, automatic logoff, ePHI encryption at rest and in transit, and integrity controls per HIPAA Technical Safeguard standards.

03
04
Phase 04
Physical Safeguard and BAA Programme

Implement physical safeguards covering facility access, workstation security, and device/media controls. Execute BAAs with all business associates handling PHI.

Phase 05
Breach Notification and Training

Establish breach notification procedures meeting 60-day HHS notification requirements, conduct workforce HIPAA training, and test incident response through tabletop exercises.

05
06
Phase 06
Ongoing Compliance and SRA Updates

Annual SRA updates, BAA review and tracking, security awareness refreshers, breach notification drills, policy and procedure reviews, and OCR investigation readiness maintenance.

Questions We Get Asked Often

HIPAA (Health Insurance Portability and Accountability Act) is a US federal law that establishes national standards for protecting sensitive patient health information (PHI), applicable to covered entities and business associates.

HIPAA applies to covered entities (healthcare providers, health plans, healthcare clearinghouses) and business associates (vendors, contractors, and subcontractors that handle PHI on behalf of covered entities).

A Security Risk Analysis (SRA) is the mandatory foundational requirement of the HIPAA Security Rule. It identifies and assesses risks to ePHI confidentiality, integrity, and availability across all systems handling PHI.

OCR imposes civil penalties from $100 to $50,000 per violation (up to $1.5M per category per year). Criminal penalties range from $50,000 and 1 year imprisonment for wrongful disclosure to $250,000 and 10 years for intent to sell or exploit PHI.

A Security Risk Analysis and baseline compliance programme typically takes 3 to 6 months. Full implementation of administrative, physical, and technical safeguards across complex health systems may take 9 to 12 months.

Implement a Defensible HIPAA Programme

Start with the mandatory Security Risk Analysis and build a complete HIPAA compliance programme.