
That mismatch is expensive. IBM's 2026 breach report puts healthcare's average breach cost at $6.64 million, the highest of any industry for the 13th year running. It is a benchmark from a nonstatistical sample, not a prediction for your practice.
A gap analysis compares what HIPAA expects with what your systems, vendors, devices, and staff actually do. This guide covers how it differs from a risk analysis, what it reviews, how the process runs, and how to fix what you find.
Key Takeaways
- A gap analysis compares your safeguards with HIPAA requirements; it does not replace the required risk analysis.
- Review people, processes, technology, facilities, vendors, and documentation.
- Each finding needs a requirement, weakness, risk level, evidence, owner, fix, and retest.
- Reassess periodically and after major changes to systems, vendors, staff, or locations.
What Is a HIPAA Security and Compliance Gap Analysis, and Why Does It Matter?
A HIPAA gap analysis is a structured comparison between your current privacy and security program and the requirements that apply to you as a covered entity or business associate. It finds safeguards that are missing, incomplete, or only exist on paper.
HIPAA does not name a standalone "gap analysis." It does require a documented risk analysis. The gap analysis is a practical tool, not a regulatory deliverable.
Who benefits most:
- Independent medical and dental practices and clinics
- Healthcare service providers
- Business associates that create, receive, maintain, or transmit PHI
Gap Analysis vs. Risk Analysis
The two are different exercises, and each should feed the other.
| Gap analysis | Risk analysis | |
|---|---|---|
| Core question | Are required safeguards, policies, and evidence present and working? | What threats and vulnerabilities could harm ePHI, and how likely and damaging are they? |
| Output | List of missing or weak controls | Ranked risks to confidentiality, integrity, and availability |
Under 45 CFR 164.308(a)(1)(ii)(A), the risk analysis must be accurate and thorough. OCR requires it to be documented but prescribes no format. NIST also cautions that using an assessment tool does not by itself establish compliance, so a checklist alone will not satisfy the requirement.
What You Get Out of It
- Clear priorities for security spending, training, vendor reviews, and backup planning
- Visibility into policy-versus-reality gaps, such as an encryption policy not enforced on every laptop
- A documented, risk-based process that shows diligence in an audit, incident investigation, or leadership review
It does not prevent penalties or guarantee compliance. It gives you evidence of a serious, ongoing effort.
How a HIPAA Security and Compliance Gap Analysis Works
A good process moves from scope to evidence, mapping, prioritization, remediation, validation, and reassessment. It does not end with a static checklist.

Step 1: Define the Scope
Map where ePHI is created, received, maintained, transmitted, backed up, accessed, and disposed of. Include:
- EHR/EMR systems, email, servers, and cloud platforms
- Laptops, phones, and paper-to-digital workflows
- Staff, contractors, business associates, subcontractors, locations, and remote workers
Step 2: Gather Requirements and Evidence
Build your criteria from HHS/OCR guidance, the HIPAA Rules in the eCFR, and NIST SP 800-66 Rev. 2, which maps Security Rule standards to NIST frameworks. It is guidance, not regulation.
Collect evidence such as:
- Policies and risk assessments
- Asset inventories and access reviews
- Training records and incident logs
- Backup-test results and configurations
- Vulnerability reports and BAAs
Separate evidence that exists from controls that only appear in a policy.
Step 3: Compare and Document Each Gap
For every requirement, record current practice, supporting evidence, the deficiency, affected systems, and a status: implemented, partially implemented, undocumented, or not applicable.
Handle "addressable" specifications carefully. Addressable does not mean optional. You assess whether the safeguard is reasonable and appropriate, implement it if so, or document why not and adopt an equivalent alternative.
Step 4: Rate and Prioritize
Use one consistent method. Weigh impact on ePHI, likelihood of exploitation, scope of exposure, operational consequences, contractual duties, and remediation effort.
Items that usually jump the queue:
- Uncontrolled administrative access
- Missing BAAs
- Exposed systems
- Backups that have never been restored
- Unencrypted devices
- No incident procedures or incomplete risk analysis
Step 5: Remediate, Validate, and Reassess
Give every action an owner, a change, a target date, dependencies, and a place to store proof of completion. Then retest. Verbal confirmation is not enough:
- Confirm removed access is actually removed
- Check encryption is enforced, not just available
- Restore a backup to prove it works
- Confirm alerts are reviewed
- Match policies to practice and verify training completion

On timing, OCR calls risk analysis and management ongoing. The evaluation standard requires periodic review and re-evaluation after environmental or operational changes. OCR says frequency varies, and there is no universal annual deadline in the rule.
Example Case Walkthrough
This fictional example is illustrative only. It is not a QTSI case study.
A small medical practice uses an EHR, cloud email, remote access, laptops, an outsourced billing vendor, and an outside IT provider.
Finding 1: Shared Login and Unverified Encryption
The policy requires unique accounts and encrypted laptops. The review finds a shared administrative login still active and one laptop with no verified encryption.
- Documented: requirement, evidence screenshots, affected systems
- Prioritized: high, because admin access and a portable device both expose ePHI
- Assigned: the IT provider owns both fixes, with a two-week target
- Corrected: the shared login is disabled and individual admin accounts created; encryption is enabled
- Retested: the account is confirmed gone and encryption status verified in the management console

Finding 2: Vendor Without a BAA
The billing vendor handles PHI, but no signed BAA exists. The practice then:
- Confirms what data flows to the vendor
- Reviews the relationship and executes the BAA
- Files the BAA with data-flow notes for future reviews
OCR's $31,000 settlement with a small pediatric practice involved the same gap: no signed BAA for PHI disclosures.
Core Areas Reviewed in a HIPAA Gap Analysis
Administrative Safeguards and Governance
Review these administrative controls:
- Security management process, risk analysis, and risk management actions
- Assigned security and privacy roles
- Workforce clearance, termination, and awareness training
- Incident response, contingency planning, and periodic evaluations
Confirm policies match real workflows and that training is role-appropriate and documented.
Physical Safeguards and Device Handling
Examine physical and device controls across:
- Facility access, workstation placement, and screen privacy
- Remote work, laptops, mobile devices, and removable media
- Equipment movement, disposal, and reuse
Keep an asset inventory and chain-of-custody records for anything that can touch ePHI.
Technical Safeguards and Access Security
Review technical controls such as:
- Unique user IDs, authentication, and least-privilege access
- Administrator accounts, remote access, and MFA where appropriate
- Audit controls, log review, and integrity protections
- Transmission security, patching, endpoint protection, and encryption
Test configurations and logs. Written policies and vendor assurances prove little on their own.
Privacy, Disclosure, and Breach Response
Assess privacy and breach duties, including:
- Minimum-necessary access, patient-rights workflows, and authorizations
- Incident reporting, investigation, mitigation, and breach notification
Individual notice is due without unreasonable delay and no later than 60 calendar days after discovery. A Security Rule review alone does not cover every Privacy Rule or Breach Notification Rule duty.

Business Associates, Documentation, and Audit Evidence
- Inventory vendors and subcontractors that handle PHI, including cloud, email, backup, telehealth, billing, and IT providers
- Confirm BAAs and define shared responsibilities
- Verify version control, approvals, review dates, and retention (six years for required documentation)
- Keep remediation records, training evidence, access reviews, and test results together
How QTSI Can Help
QTSI is a managed IT and cybersecurity provider based in Wayne, New Jersey, serving independent medical and dental practices across New Jersey, New York, Pennsylvania, and the Tri-State area. QTSI does not certify any organization as HIPAA-compliant. Its role is strengthening the technical and operational safeguards a gap analysis flags.
Relevant capabilities include:
- Managed IT, endpoint protection, firewalls, and access management
- Cloud services, backup, and disaster recovery
- Networking and secure connectivity
- 24x7 live support with continuous monitoring
- IT consulting and virtual CIO planning, including vendor management
For practices without a large internal IT team, personalized human support and more than 20 years of experience matter most. Engagements start by learning your infrastructure, pain points, and goals. From there, QTSI can:
- Turn gap-analysis findings into a technology roadmap
- Work with practice leadership and compliance stakeholders
- Implement agreed technical and operational controls
- Provide ongoing support and documentation
If you want to talk through your environment, known gaps, and remediation priorities, QTSI offers a free IT assessment. Confirm legal, regulatory, and audit requirements with qualified compliance or legal professionals.
Conclusion
A gap analysis turns broad regulatory expectations into a documented view of your safeguards, deficiencies, priorities, owners, and next steps. It works best alongside the required risk analysis, verified fixes, current evidence, and reassessment whenever systems, vendors, staff, or locations change.
Frequently Asked Questions
What is a HIPAA risk analysis?
It identifies and evaluates threats and vulnerabilities to the confidentiality, integrity, and availability of ePHI. The Security Rule requires it, and it is distinct from a gap analysis.
What is an example of a gap analysis?
Compare the requirement for controlled access with a practice's shared admin account or missing access reviews. Then document the fix, such as individual accounts, and the evidence proving it.
What are the new HIPAA compliance requirements for 2026?
The Security Rule overhaul proposed in January 2025 (MFA, encryption, asset inventories, 72-hour restoration, annual audits) is still a proposal. HHS says the current rule remains in effect, and no final rule has been issued. Verify status with HHS/OCR before acting.
What is a HIPAA gap analysis?
It compares your policies, safeguards, practices, and evidence with applicable HIPAA requirements to identify and prioritize deficiencies.
How is a HIPAA gap analysis different from a risk analysis?
A gap analysis checks control and regulatory coverage. A risk analysis weighs threats, vulnerabilities, likelihood, and impact. Most organizations need both.
How often should a HIPAA gap analysis be performed?
HIPAA sets no interval for a standalone gap analysis. Evaluate periodically and reassess after significant changes to systems, vendors, workforce, facilities, or operations.