Skip to content
HIPAA ComplianceConsulting

Assessment Services Overview

HIPAA Risk Assessment Services

An overview of the assessment family — formal risk analysis, gap analysis, technical safeguards review and audit readiness — and how to decide which one you need first.

Reviewed Request a HIPAA Consultation

“We need a HIPAA risk assessment” can mean four different things. Sometimes it means the formal security risk analysis the Security Rule requires. Sometimes it means a gap analysis against the full rule set, a hands-on review of technical controls, or a dry run before a regulator or customer starts asking questions. Buying the wrong one wastes budget and can leave the actual legal requirement unmet.

This page explains the family of HIPAA risk assessment services, how they relate to each other, and how to choose a starting point based on where your organization is today. Each service has its own detailed page if you already know what you need.

Key points

  • The Security Rule requires an accurate and thorough risk analysis — a gap analysis alone does not satisfy it.
  • Different assessments answer different questions: “What could go wrong?” versus “What are we missing?” versus “Can we prove it?”
  • No assessment is a government audit, and none results in an official HIPAA certification.
  • Most organizations start with the risk analysis and layer other reviews on top.

What HIPAA risk assessment services cover

Our assessment work is organized as a small set of distinct engagements rather than one generic checklist. Each produces a different kind of evidence and supports a different decision. They share a common discipline — scoping where electronic protected health information (ePHI) actually lives, testing what is in place rather than what is written down, and documenting findings in a form you can defend later.

The HIPAA assessment family at a glance
ServiceCore question it answersPrimary output
Security risk analysisWhat threats and vulnerabilities could affect the confidentiality, integrity and availability of our ePHI, and how serious is each risk?Risk register with likelihood, impact and risk ratings
Gap analysisWhich HIPAA standards and implementation specifications are we not meeting, or cannot evidence?Requirement-by-requirement gap matrix
Technical safeguards assessmentDo our access controls, audit logging, integrity and transmission protections actually work as configured?Control test results and technical findings
Audit readinessIf OCR or a customer asked tomorrow, could we produce the documents and evidence?Evidence inventory and readiness findings

Risk analysis vs. risk assessment: why the wording matters

The regulation uses the term “risk analysis” (45 CFR §164.308(a)(1)(ii)(A)). In the market, “risk assessment” is often used loosely for almost any HIPAA review. The distinction matters because the risk analysis is a required implementation specification with a specific purpose: an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of all ePHI the organization creates, receives, maintains or transmits.

A checklist that asks “Do you have a password policy?” is not a risk analysis. A risk analysis identifies where ePHI flows, what could plausibly go wrong, how likely and how damaging that would be, and what the current controls do about it. We cover the terminology in more depth in our guide to risk analysis vs. risk assessment.

Who needs a HIPAA risk assessment

Every covered entity and business associate that handles ePHI is subject to the risk analysis requirement. In practice, organizations come to us at predictable moments:

  • A clinic or specialty practice that has never documented a risk analysis, or last did one before moving to a cloud EHR.
  • A digital health or SaaS company whose hospital customers are asking for evidence of a current risk analysis during procurement.
  • A medical billing company or other business associate that signed BAAs before building a compliance program.
  • A hospital or health system that completed an internal assessment and wants an independent view before a board review.
  • Any organization that has just had a security incident, a merger, a major system change or a new line of service.

Regulatory considerations

The risk analysis sits at the start of the Security Rule’s security management process. It feeds directly into risk management (§164.308(a)(1)(ii)(B)), which requires implementing security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level. Without a credible analysis, decisions about addressable specifications — and documentation of why an alternative was chosen — have nothing to stand on.

Separately, the evaluation standard (§164.308(a)(8)) requires periodic technical and nontechnical evaluation in response to environmental or operational changes. The rule does not set a fixed frequency for the risk analysis; HHS guidance describes it as an ongoing process that should be revisited as the environment changes. Documentation of assessments, decisions and actions must be retained for six years under §164.316(b).

The HHS Security Risk Assessment (SRA) Tool, published by ONC and OCR, is a free resource that smaller organizations can use. Using it does not by itself ensure compliance, and it is only as good as the inventory and answers that go into it. HHS has also proposed changes to the Security Rule in a notice of proposed rulemaking published January 6, 2025; those changes are proposed, not final, so verify their current status before planning around them.

Common challenges we see

  • Incomplete scope: the analysis covers the EHR but misses email, fax-to-email services, shared drives, billing platforms, backups and staff mobile devices.
  • Templates presented as analysis: a generic document with the organization’s name inserted and no evidence of actual testing.
  • Risk ratings without reasoning: “High” and “Low” labels with no recorded likelihood or impact rationale.
  • No link to remediation: findings sit in a report while nobody owns a risk management plan.
  • Stale results: the last analysis predates a cloud migration, a new telehealth platform or a change in vendors.

How to choose the right assessment

Start from the decision you need to make, not the name of the product. The table below is the rule of thumb we use during scoping calls.

Your situationUsual starting pointOften added
No documented risk analysis, or one older than your current systemsSecurity risk analysisGap analysis
Analysis exists but policies and training are uncertainGap analysisPolicies and procedures work
Customers or insurers asking about specific controlsTechnical safeguards assessmentRisk analysis update
Recent breach report, complaint or OCR data requestAudit readinessTargeted risk analysis update
Building a program from scratchRisk analysis plus gap analysisOngoing support

Our assessment methodology

All assessments in this family follow the same foundation, adapted to the engagement type:

  • Asset and data-flow inventory: systems, vendors, devices and workflows that create, receive, maintain or transmit ePHI.
  • Evidence over attestation: configuration screenshots, system exports, sample logs and walkthroughs rather than yes/no questionnaires.
  • Framework alignment: NIST SP 800-30 for risk methodology and NIST SP 800-66 Rev. 2 for mapping to Security Rule standards.
  • Clear separation of what HIPAA requires from what is recommended good practice, so you can prioritize legal obligations first.
  • Findings written for two audiences: an executive summary for leadership and technical detail for the people who will fix things.

Typical deliverables

  • Scope statement and ePHI inventory or data-flow diagram.
  • Findings report with risk ratings or gap status, depending on the engagement.
  • Prioritized remediation roadmap that distinguishes required actions from recommendations.
  • Supporting evidence index you can retain under your six-year documentation obligation.
  • Executive briefing for leadership or the board.

Engagement process

  1. 1

    Scoping call

    We discuss your organization, systems, vendors and what prompted the request, then recommend which assessment (or combination) fits.

  2. 2

    Document and data request

    You share existing policies, prior assessments, system lists, BAAs and network information through a secure channel.

  3. 3

    Interviews and walkthroughs

    We speak with the security or privacy official, IT, clinical or operations leads and key vendors as needed.

  4. 4

    Testing and analysis

    We review configurations and evidence, rate risks or gaps, and validate preliminary findings with your team.

  5. 5

    Report and briefing

    You receive the written deliverables and a walkthrough of priorities, with time for questions.

  6. 6

    Next steps

    Many clients move into HIPAA compliance remediation or periodic updates; others handle remediation internally.

Cost factors

We scope every assessment individually and do not publish fixed prices. The main drivers are the number of locations and legal entities, the number of systems and vendors handling ePHI, whether technical testing is included, how much existing documentation is usable, and the deadline. Combining a risk analysis and gap analysis in one engagement is usually more efficient than running them separately. Our risk assessment cost resource explains these drivers in more detail.

Frequently asked questions

Is a HIPAA risk assessment required by law?

The Security Rule requires covered entities and business associates to conduct an accurate and thorough risk analysis of risks to ePHI (45 CFR §164.308(a)(1)(ii)(A)). Other assessments, such as gap analyses or audit readiness reviews, are not individually mandated but help demonstrate and maintain compliance.

How often should we repeat a risk assessment?

HIPAA does not specify a fixed interval. HHS describes risk analysis as ongoing, and the evaluation standard requires reassessment in response to environmental or operational changes. Many organizations review annually and after significant changes such as new systems, vendors or locations.

Will we receive a HIPAA certification after an assessment?

No. HHS does not recognize any official HIPAA certification for organizations or consultants. An assessment documents your current state and risks; maintaining compliance is an ongoing responsibility.

Can we just use the HHS SRA Tool ourselves?

Yes, and some small practices do. The tool is free and structured, but it relies on the accuracy of your inputs and does not test controls. Using it does not by itself ensure compliance. Some organizations use it internally and engage outside help for validation or more complex environments.

Is a risk assessment the same as an OCR audit?

No. An assessment is a voluntary review you commission. OCR investigations, compliance reviews and audits are conducted by the government. A good assessment can help you prepare, but it is not a regulatory determination.

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.