Skip to content
HIPAA ComplianceConsulting

Assessment Service

HIPAA Gap Analysis

A structured comparison of what HIPAA requires against what you actually do and can prove, with every gap classified and prioritized.

Reviewed Request a HIPAA Consultation

A gap analysis is the most direct way to answer “What are we missing?” It walks through HIPAA requirement by requirement and compares each one with your written policies, your day-to-day practice and the evidence you could produce if asked.

Where a risk analysis looks outward at threats to ePHI, a gap analysis looks at your program against the rules themselves. It is particularly useful when building or rebuilding a compliance program, preparing for customer due diligence, or deciding where to spend a limited compliance budget.

Key points

  • Covers the Privacy, Security and Breach Notification Rules — or a subset you choose.
  • Tests three layers: written policy, actual practice and available evidence.
  • Distinguishes required, addressable and recommended items.
  • Complements, but does not replace, the required security risk analysis.

Service overview

Our HIPAA gap analysis uses a requirement matrix built from 45 CFR Part 164. For each standard and implementation specification in scope, we record what the rule requires, what your policy says, what staff actually do, and what evidence exists. The difference between those layers is the gap.

Gaps are rarely just “no policy.” More often, a policy exists but is not followed, or a practice exists but nobody can prove it. Those distinctions change how you fix the problem, so we record them separately.

How we classify each requirement
StatusMeaningTypical fix
MetPolicy, practice and evidence all align with the requirementMaintain and review on schedule
Partially metSome elements in place; others missing or inconsistentTargeted update to policy or process
Not evidencedPractice appears to happen but cannot be demonstratedCreate logs, records or sign-offs
Not metRequirement not addressedDesign and implement a control or procedure
Addressable — decision undocumentedAddressable specification with no recorded assessmentDocument the reasonableness decision and any alternative

Who needs a gap analysis

  • Organizations building a HIPAA program for the first time and wanting a clear starting list.
  • Practices that have a risk analysis but are unsure whether their Privacy Rule and breach procedures are complete.
  • Business associates responding to customer security and privacy questionnaires — see HIPAA consulting for business associates.
  • Organizations after a merger or acquisition that need to reconcile two sets of policies.
  • Compliance teams preparing a budget request and needing an objective list of what is missing.

Regulatory considerations

The Security Rule distinguishes required implementation specifications from addressable ones. A gap analysis is where that distinction gets tested in practice.

RequiredAddressable
What the rule expectsImplement the specificationAssess whether it is reasonable and appropriate; implement it, implement an equivalent alternative, or document why neither is reasonable
ExamplesRisk analysis; unique user identification; audit controls; data backup planEncryption at rest; automatic logoff; security reminders
Common gapSpecification missing or not operatingDecision never documented, or “addressable” treated as optional

Common gaps we find

  • No documented decisions for addressable specifications.
  • Notice of Privacy Practices out of date or not posted as required.
  • No log of individual access requests or response dates.
  • Business associates without BAAs, or BAAs missing provisions required by §164.504(e).
  • Sanction policy written but never applied or documented.
  • Breach procedures that do not reflect current notification timing or the four-factor risk assessment.
  • Training records incomplete for new hires or contractors.

Methodology

  • Requirement matrix drawn from 45 CFR Part 164, Subparts C, D and E, scoped to your role as covered entity, business associate or both.
  • Document review of policies, procedures, BAAs, training records, prior assessments and incident logs.
  • Interviews with the privacy and security officials and with front-line staff in representative roles.
  • Sampling to test evidence: for example, a handful of access requests, terminations or vendor files.
  • Prioritization by legal obligation and risk, informed by your security risk analysis where one exists.

Choosing the right scope

A Security Rule–only gap analysis suits organizations, such as many business associates, whose main exposure is ePHI in their systems. A full three-rule review suits covered entities, which carry Privacy Rule obligations to patients such as access, amendment and the Notice of Privacy Practices. A targeted review — for example, only breach notification readiness — can make sense after an incident.

Whatever the scope, we record what was excluded so the report is not later read as covering more than it did.

Why we test three layers

Checking policy alone tells you what the organization intended. Interviews tell you what people believe they do. Evidence sampling tells you what actually happened. Requirements often look met at the first layer and fail at the third, and those are the gaps that matter most when someone outside the organization asks for proof.

Typical deliverables

  • Gap matrix listing every requirement in scope, its status and supporting notes.
  • Narrative summary of the most significant gaps and their likely consequences.
  • Prioritized remediation plan with suggested owners and sequencing.
  • List of documents to create or update, which can feed directly into HIPAA policies and procedures work.
  • Leadership briefing.

Engagement process

  1. 1

    Scope the rules

    We agree which rules and entities are in scope and confirm whether you act as a covered entity, business associate or both.

  2. 2

    Collect documents

    You provide policies, BAAs, training records, logs and prior assessments through a secure channel.

  3. 3

    Interview and sample

    We interview key staff and test samples of evidence against the requirement matrix.

  4. 4

    Classify gaps

    Each requirement is marked met, partially met, not evidenced, not met or undocumented addressable.

  5. 5

    Prioritize and report

    We deliver the matrix, narrative and remediation plan, and walk your team through it.

Cost factors

Scope is the biggest driver: a Security Rule–only gap analysis is narrower than one covering all three rules. Other factors include the number of entities and locations, the volume of existing documentation to review, how many interviews and samples are needed, and whether the gap analysis is combined with a risk analysis. Combining them avoids collecting the same information twice. Our HIPAA compliance checklist can help you estimate how much is already in place.

Frequently asked questions

Is a gap analysis required by HIPAA?

Not as a named requirement. The Security Rule requires a risk analysis and periodic evaluation (§164.308(a)(8)); a gap analysis is a practical way to support evaluation and to show where your program falls short.

Can a gap analysis replace our risk analysis?

No. A gap analysis checks your program against requirements; the risk analysis assesses threats and vulnerabilities to ePHI. OCR expects the risk analysis specifically. The two are complementary.

Does a clean gap analysis mean we are compliant?

It means that, on the date of the review and based on the evidence sampled, requirements in scope appeared to be met. It is not a certification or a government determination, and compliance must be maintained as your organization changes.

Should we include the Privacy Rule if we are a business associate?

Often yes. Business associates must comply with the Security Rule and with Privacy Rule limits on uses and disclosures set by their BAAs. We tailor the requirement matrix to your role.

Authoritative sources

This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.

Talk through your HIPAA obligations with a consultant

Tell us about your organization, how you handle patient information, and what’s prompting the review. We’ll suggest a practical scope — and tell you if you don’t need us.