See what our clients say about working with Bonami Software across 200+ projects for 18+ industries. EXPLORE NOW!
We don't just build software. We deliver results. EXPLORE NOW!
See why businesses choose Bonami Software for reliable, scalable solutions. EXPLORE NOW!
We turn ideas into scalable products with proven delivery across 18+ industries. EXPLORE NOW!
See what our clients say about working with Bonami Software across 200+ projects for 18+ industries. EXPLORE NOW!
We don't just build software. We deliver results. EXPLORE NOW!
See why businesses choose Bonami Software for reliable, scalable solutions. EXPLORE NOW!
We turn ideas into scalable products with proven delivery across 18+ industries. EXPLORE NOW!

HIPAA Requires a Thorough Risk Analysis. OCR Looks for It First.

We conduct the ePHI inventory, threat and vulnerability analysis, and gap analysis the Security Rule requires — producing written documentation that satisfies regulators, passes enterprise vendor security reviews, and drives a prioritized remediation roadmap.

BrowserStack
Persistent
Yatra
Kellton
Jade Global
Optum
PokerBaazi
Walmart
BrowserStack
Persistent
Yatra
Kellton
Jade Global
Optum
PokerBaazi
Walmart

Book a HIPAA Risk Assessment Consultation

Talk to our team about your ePHI environment and compliance posture. We reply within 24 hours.

  • We respond within 24 hours, fully NDA-protected.
BrowserStack
Persistent
Yatra
Kellton
Jade Global
Optum
PokerBaazi
Walmart
BrowserStack
Persistent
Yatra
Kellton
Jade Global
Optum
PokerBaazi
Walmart

Trusted by startups and global leaders

BrowserStack
Persistent
Yatra
Kellton
Jade Global
Optum
PokerBaazi
Walmart
BrowserStack
Persistent
Yatra
Kellton
Jade Global
Optum
PokerBaazi
Walmart

What a HIPAA Risk Assessment Covers

The HIPAA Security Rule requires a thorough, accurate assessment of every risk to ePHI — where it lives, what threatens it, and what controls close the gaps. OCR cites inadequate risk analysis in nearly every major enforcement action.

ePHI Inventory & Data Flow Mapping

Every location where ePHI is created, stored, processed, or transmitted — databases, backups, email, mobile devices, third-party apps, and integration points. Organizations consistently find more ePHI than they expected once a thorough inventory is conducted.

Threat & Vulnerability Identification

External attackers, insider threats, system failures, and environmental disasters — each evaluated against the technical and operational weaknesses they could exploit, including unpatched software, weak authentication, and inadequate access controls.

Likelihood & Impact Analysis

Each threat-vulnerability combination is scored by the probability it materializes and the impact if it does — regulatory penalties, patient harm, reputational damage, and business disruption. Risk scores drive prioritization, not guesswork.

Control Evaluation & Gap Analysis

Current security controls are documented and tested against each identified risk. Gaps are mapped to HIPAA Security Rule implementation specifications — distinguishing required from addressable — so remediation targets the right controls in the right order.

Remediation Planning

A prioritized, owner-assigned remediation plan with target timelines — the organization's roadmap from current risk posture to defensible compliance. Updated as gaps close and the environment changes.

OCR-Ready Documentation

A written risk assessment report retained for six years — the document OCR auditors request first. Methodology, scope, findings, risk scores, current controls, identified gaps, and remediation recommendations, at a depth that withstands regulatory scrutiny.

HIPAA Risk Analysis Is Foundational — Not Optional

Hover to explore what the risk analysis requirement means, what OCR looks for, and what happens when it is missing.

How We Conduct a HIPAA Risk Assessment

A five-step methodology from scope definition to OCR-ready documentation — producing a written risk analysis that satisfies regulators, passes enterprise vendor security reviews, and drives a prioritized remediation roadmap.

STEP 1 — Scope Definition

Identify every system, location, and business process where ePHI is created, stored, processed, or transmitted — production environment, development and staging, backups, employee devices, and third-party services that handle ePHI. Scope gaps produce assessment gaps that surface in OCR audits.

STEP 2 — Asset Inventory & Data Flow Mapping

Document every asset within scope and trace ePHI flows between them. This step regularly surfaces undocumented data flows — PHI in system logs, ePHI exported to analytics tools, or patient data shared with support vendors during troubleshooting. The inventory becomes a living document updated as the environment changes.

STEP 3 — Threat & Vulnerability Analysis

Systematically identify threats applicable to each asset and the vulnerabilities they could exploit — referencing NIST Cybersecurity Framework and HHS SRA Tool guidance. Analysis covers threats specific to the organization's technology stack alongside industry-wide healthcare threats, producing a complete threat picture rather than a generic one.

Why a Current Risk Assessment Is a Compliance Necessity

OCR audits begin with the risk analysis. Enterprise healthcare customers require it in vendor reviews. A missing or stale assessment is the one finding that immediately puts an organization on the defensive.

Book a Risk Assessment Consultation
OCR First
OCR audit protocols specifically examine whether a risk analysis exists, whether it was thorough and accurate, whether it has been updated regularly, and whether a risk management plan addresses the findings. Organizations without a current risk analysis are immediately on the defensive.
Pass Reviews
Enterprise health systems and payers request the risk assessment as part of vendor security reviews before signing contracts. A complete, documented risk analysis is a commercial prerequisite — not just a compliance one — for selling to healthcare organizations.
Prioritized
Risk scoring produces a prioritized remediation roadmap — high-likelihood, high-impact risks first. Without it, security spending is guesswork. With it, every dollar targets the controls that reduce the highest actual risk to patient data.
Always Live
A one-time risk assessment conducted at launch and never revisited fails HIPAA's ongoing requirement. Every new system, new vendor, or significant change in PHI processing restarts the clock. The assessment must keep pace with the organization.
6 Years
HIPAA requires that risk analysis documentation be retained for six years. The written report must be detailed enough for a regulator to reconstruct the thoroughness of the analysis during an audit or investigation — long after the assessment was conducted.
PHIPA Too
Canadian digital health companies face parallel obligations under PHIPA in Ontario, HIA in Alberta, and equivalent provincial legislation. The risk assessment requirement is a common thread across North American health information privacy law, not a U.S.-only concern.

The Five Components HIPAA Requires Your Risk Analysis to Cover

The Office for Civil Rights evaluates risk assessments against each of these components. A gap in any one of them is a finding in an audit or investigation.

ePHI Inventory

Where ePHI Lives

A complete inventory of every location where electronic protected health information exists across the organization's environment.

  • Databases and data warehouses
  • Backup and archive media
  • Email and messaging systems
  • Mobile devices and laptops
  • Third-party applications and APIs
Threats

Threat Identification

The realistic threat actors and events that could compromise ePHI confidentiality, integrity, or availability.

  • External attackers and ransomware
  • Phishing and social engineering
  • Malicious or negligent insiders
  • System and hardware failures
  • Natural and environmental events
Vulnerabilities

Vulnerability Assessment

Technical and operational weaknesses that threats could exploit to compromise ePHI.

  • Unpatched software and dependencies
  • Weak or shared authentication
  • Inadequate access controls
  • Misconfigured cloud services
  • Undocumented data flows
Risk Scoring

Likelihood & Impact

Each threat-vulnerability pair is scored by likelihood and potential impact to produce a prioritized risk register.

  • Likelihood rating per threat
  • Impact on ePHI confidentiality
  • Impact on ePHI integrity
  • Impact on ePHI availability
  • Combined risk level and priority
Controls

Current Controls & Gaps

Existing security controls are evaluated against each risk, and gaps are mapped to HIPAA Security Rule specifications.

  • Required specification compliance
  • Addressable specification review
  • Control effectiveness evaluation
  • Gap identification and documentation
  • Remediation priority assignment
Documentation

OCR-Ready Report

Written documentation retained for six years and detailed enough to withstand regulatory scrutiny.

  • Assessment methodology and scope
  • Full findings and risk scores
  • Current controls documented
  • Gaps mapped to Security Rule
  • Prioritized remediation roadmap

The Risk Assessment Framework We Work From

Standards-based tooling and regulatory guidance — referenced to produce a risk analysis that satisfies OCR, enterprise healthcare customers, and provincial health privacy regulators.

HIPAA Security Rule H HIPAA Security Rule
45 CFR 164.308(a)(1) 4 45 CFR 164.308(a)(1)
HHS SRA Tool H HHS SRA Tool
PHIPA (Ontario) P PHIPA (Ontario)
HIA (Alberta) H HIA (Alberta)
Your Risk Assessment Is the Document OCR Asks For First.

A thorough, documented HIPAA risk analysis is the foundation of defensible compliance — and the first thing regulators request. We conduct the assessment, produce OCR-ready documentation, and deliver a prioritized remediation roadmap your team can act on.

Book a Risk Assessment Consultation
AI Readiness

Award-Winning AI Development & Consulting

2025

100 Fastest Growth Companies

2025

Global Spring Winner

2025

Top App Development Company

2024

AWS Partner Network

2024

Google Cloud Partner

2025

Highly Rated on Trustpilot

2024

Verified Agency

2024

Top App Development Company

2024

ASSOCHAM Member

Frequently Asked Questions

[ 1 ]

How often should a HIPAA risk assessment be updated?

HIPAA does not specify a fixed reassessment interval, but the Security Rule's ongoing risk analysis requirement means the assessment must be revisited whenever significant changes occur — a new system deployed, a new business associate engaged, a security incident, or a material change in how ePHI is processed. Most healthcare compliance professionals recommend a full reassessment at least annually. For fast-growing digital health startups adding features and integrations regularly, this means the risk assessment is a living document rather than a periodic exercise.

[ 2 ]

What is the HHS Security Risk Assessment Tool?

The HHS Office for Civil Rights and the Office of the National Coordinator for Health Information Technology jointly developed the Security Risk Assessment Tool — commonly called the SRA Tool — as a free resource to help smaller healthcare organizations conduct HIPAA risk assessments. It provides a structured questionnaire covering the HIPAA Security Rule's requirements, guidance on evaluating threats and vulnerabilities, and functionality to document findings and generate a risk assessment report. While the SRA Tool is most appropriate for smaller organizations with less complex environments, it can be a useful starting point for understanding assessment scope.

[ 3 ]

What is the difference between a HIPAA risk assessment and a security audit?

A HIPAA risk assessment is an internally focused exercise that systematically evaluates the organization's own risks, vulnerabilities, and controls against HIPAA Security Rule requirements. It is conducted to understand risk posture and identify what needs to improve. A HIPAA security audit is typically an external assessment conducted by a third party evaluating whether the organization's practices and controls meet HIPAA requirements. Audits may be conducted voluntarily for external validation, by healthcare enterprise customers as part of vendor due diligence, or by OCR as part of its compliance oversight program. A solid, current risk assessment is the foundation that makes an external audit go smoothly.

[ 4 ]

Does the HIPAA risk analysis requirement apply to Canadian companies?

HIPAA's risk analysis requirement applies to any covered entity or business associate that handles ePHI belonging to U.S. patients, regardless of where the organization is located. A Canadian digital health company serving U.S. healthcare organizations is a Business Associate under HIPAA and must comply with the Security Rule — including conducting a risk analysis. For the Canadian patient population, PHIPA in Ontario and equivalent legislation in other provinces impose comparable risk assessment obligations on health information custodians and agents.

Global presence

Two offices. One team.

Hi, I'm ARIA. Ask me anything about Bonami's AI agents.