Skip to content
HIPAA ComplianceConsulting

HIPAA Consulting Service

HIPAA Risk Management Consulting

We help you act on your risk analysis: a working risk register, treatment decisions, documented risk acceptance and a tracking cadence that satisfies §164.308(a)(1)(ii)(B).

Reviewed Request a HIPAA Consultation

Many organizations complete a security risk analysis and then file it. The Security Rule asks for more. Section 164.308(a)(1)(ii)(B) requires covered entities and business associates to implement security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level. That is risk management, and it is a separate required implementation specification from the risk analysis itself.

Our HIPAA risk management service picks up where the analysis ends. We turn findings into a risk register that someone owns, help leadership decide how each risk will be treated, document the decisions you make, and set up a review rhythm so the register stays current as systems and threats change.

Key points

  • Risk analysis (§164.308(a)(1)(ii)(A)) and risk management (§164.308(a)(1)(ii)(B)) are both required.
  • OCR enforcement actions frequently cite failures in one or both.
  • Risk acceptance is legitimate when it is reasoned, approved and documented.
  • Documentation must be retained for six years under §164.316(b)(2).

Service overview

Risk management is the operational half of the Security Rule’s security management process. It converts a list of threats and vulnerabilities into decisions: what you will fix, by when, who is accountable, and what residual risk leadership is prepared to carry.

This service assumes you already have a risk analysis, whether we performed it through our HIPAA security risk assessment or it came from another provider or an internal team. If the analysis is out of date or too thin to work from, we will say so and recommend refreshing it before building a register on top of it.

Who needs this service

  • Organizations with a completed risk analysis but no clear record of what was done about the findings.
  • Compliance or security leads who need a defensible way to present risk to executives and the board.
  • Business associates whose customers ask for evidence of ongoing risk treatment, not just a point-in-time report.
  • Entities responding to an OCR inquiry, or preparing for one, where the investigator is likely to request both the analysis and the risk management plan.
  • Growing organizations (new sites, acquisitions, new platforms) whose risk picture changes faster than an annual review can capture.

Regulatory considerations

The risk management standard is flexible by design. Section 164.306(b) lets each entity consider its size, complexity and capabilities, its technical infrastructure, the cost of security measures and the probability and criticality of potential risks when choosing safeguards. That flexibility is not a loophole: you must be able to explain why the measures you chose reduce risk to a reasonable and appropriate level.

Decisions about addressable implementation specifications belong in the same record. Where you implement an alternative measure or decide a specification is not reasonable and appropriate, §164.306(d)(3) requires you to document why. Policies, procedures and these decisions must be retained for six years from creation or last effective date under §164.316(b)(2), and reviewed periodically.

NIST SP 800-66 Rev. 2 and NIST’s broader risk management publications are useful frameworks for structuring this work; they are guidance rather than HIPAA requirements.

Common risk management challenges

  • Risk analysis findings stated as vague observations (“improve access control”) that cannot be assigned or closed.
  • Every risk rated “high”, which leaves no basis for prioritization or budgeting.
  • Remediation tracked in an IT ticketing system with no link back to the risk it addresses.
  • Risks quietly left open with no record of who decided to accept them, or why.
  • Registers that are updated once a year, so new systems and vendors are never assessed in between.
  • No agreed definition of what “reasonable and appropriate” residual risk means for the organization.

Our methodology

Risk treatment options
OptionWhat it meansWhat to document
MitigateImplement safeguards to reduce likelihood or impactControl to be implemented, owner, target date, evidence of completion
TransferShift some financial impact through contracts or insuranceAgreement or policy reference; note that HIPAA obligations remain
AvoidDiscontinue the activity or system that creates the riskDecision, date and confirmation the activity stopped
AcceptRetain the risk at its current levelRationale, approver with appropriate authority, review date

1. Normalize the findings

We rewrite each finding as a risk statement linking a threat, a vulnerability, the affected ePHI or system, and the likely impact. Duplicates are merged and anything that is really a control description is set aside.

2. Agree a rating scale

We work with you to define likelihood and impact levels in terms that fit your operations — patient care disruption, record volumes, regulatory exposure — so ratings mean the same thing to IT, compliance and leadership.

3. Decide treatment

For each risk, leadership chooses to mitigate, transfer (for example through contract terms or insurance, which does not remove the HIPAA obligation), avoid (stop the activity), or accept. Mitigation entries get an owner, target date and the specific safeguard to be implemented.

4. Build the tracking rhythm

We set a review cadence, triggers for out-of-cycle review (new systems, incidents, vendor changes) and a simple status report so progress is visible. Large remediation programs can move into our HIPAA compliance remediation service.

Typical deliverables

  • A HIPAA risk register (spreadsheet or your GRC tool) with rated, owned risks linked to the source analysis.
  • Risk treatment plan with milestones and dependencies.
  • Risk acceptance form and approval workflow.
  • Documented decisions on addressable implementation specifications.
  • A risk management procedure describing roles, rating criteria, review cadence and escalation.
  • An executive summary suitable for leadership or board reporting.

Engagement process

  1. 1

    Review the risk analysis

    Confirm the analysis is current and enterprise-wide enough to build on; flag gaps if it is not.

  2. 2

    Define the scale

    Agree likelihood, impact and risk-level definitions with compliance, IT and leadership.

  3. 3

    Build the register

    Normalize findings into risk statements, rate them and link them to affected systems and ePHI.

  4. 4

    Treatment workshop

    Facilitated session where owners and leadership decide treatment for each risk.

  5. 5

    Plan and handover

    Deliver the treatment plan, acceptance records and procedure, and run the first status review with your team.

Cost factors

Pricing depends on the number and quality of findings in the existing risk analysis, the number of systems and sites, whether you use a GRC platform we need to configure against, and whether you want us to facilitate recurring reviews afterward. Organizations that want ongoing facilitation often fold it into ongoing HIPAA compliance support.

Frequently asked questions

What is the difference between HIPAA risk analysis and risk management?

Risk analysis, under §164.308(a)(1)(ii)(A), identifies and assesses risks to ePHI. Risk management, under §164.308(a)(1)(ii)(B), is implementing measures to reduce those risks to a reasonable and appropriate level. Both are required implementation specifications.

Can we accept a risk instead of fixing it?

Yes, provided the decision is reasoned and documented, approved by someone with appropriate authority, and periodically revisited. Undocumented, indefinite acceptance of significant risks is difficult to defend.

Do we need special software for a risk register?

No. HIPAA does not require any particular tool. A well-structured spreadsheet works for many organizations; larger ones often prefer a GRC platform. What matters is that it is maintained and retained.

How often should the register be reviewed?

HIPAA requires periodic review and updates in response to environmental or operational changes rather than a fixed frequency. Many organizations review open risks quarterly and trigger out-of-cycle review for significant changes.

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.