HealthITPrep
CPHIMS guide Concepts Features Pricing FAQ
Sign in Start free
العربية

Risk analysis and risk responses: accept, avoid, transfer or mitigate

By Adel Moustafa, CPHIMS® · Updated 22 October 2026

How a healthcare organization finds its risks, ranks them, and decides what to do about each one.

In short: a risk analysis finds the threats and vulnerabilities to information and rates each risk by its likelihood and its impact. Each risk then gets one of four responses: mitigate it with controls (encryption, access control, training), transfer part of it to another party (insurance, a contract), avoid it by stopping the activity, or accept it, knowingly and on record. What is left after the response is the residual risk.
The terms The analysis The four responses ALE Under HIPAA Common mistakes Summary Sources

What are threat, vulnerability and risk?

  • Asset: what needs protecting, such as patient records, a server, a medical device or the EHR's availability.
  • Threat: something that could cause harm: a thief, ransomware, a flood, a careless user.
  • Vulnerability: a weakness a threat can use: an unencrypted laptop, an unpatched server, a shared password.
  • Risk: the chance that a threat uses a vulnerability, combined with the harm that would follow. No vulnerability, or no threat, means little risk.
  • Control (safeguard): a measure that lowers the likelihood or the impact.

How is a risk analysis done?

A common sequence, from HHS's risk analysis guidance (which draws on NIST SP 800-30):

  1. Scope and inventory: where electronic protected health information is created, received, kept and sent, including laptops, phones, devices and vendors.
  2. Threats and vulnerabilities: what could happen, and what weaknesses would let it.
  3. Current controls: what is already in place.
  4. Likelihood and impact: each rated, often as low, medium or high.
  5. Risk level: likelihood and impact combined, often on a matrix, so the risks can be ranked.
  6. Document and repeat: the results go in a risk register with an owner for each risk, and the analysis is reviewed regularly and after major changes (a new system, a move, an incident).

A qualitative analysis uses ratings (high, medium, low) and is quick and common. A quantitative one puts money on the risks (below), which helps compare a control's cost with the loss it prevents, but needs data that is often uncertain.

What are the four risk responses?

ResponseWhat it meansExample (an unencrypted laptop with patient data)When it fits
Mitigate (reduce)Add controls that lower the likelihood or the impact.Full-disk encryption, strong sign-in, remote wipe.The usual answer when a reasonable control exists, especially for a high risk.
Transfer (called "share" in ISO 31000)Move part of the financial consequence to another party.Cyber insurance; a contract that makes a vendor pay for its failures.Rare, costly events; beside controls, not instead of them.
AvoidStop or change the activity so the risk no longer exists.No patient data stored on laptops; staff work through a secure remote session.When the activity is not needed, or the risk outweighs its benefit.
AcceptDecide, on record, to live with the risk.Not reasonable here; fits a low risk whose control costs more than the harm.Low risks, or residual risk within the organization's risk appetite, approved by someone with authority.

Project management uses the same four for threats to a project and adds escalate (the risk is outside the project's authority, so it goes up). For opportunities it uses the mirror image: exploit, enhance, share, accept, and escalate as well.

Transfer moves money, not responsibility. Insurance can pay for a breach, but the covered entity stays responsible under HIPAA for protecting the data and notifying the people affected; a business associate agreement shares obligations but does not remove the covered entity's own.

How is risk calculated in money (SLE, ARO, ALE)?

  • Single loss expectancy (SLE) = asset value × exposure factor (the share of the value lost in one event).
  • Annualized rate of occurrence (ARO): how many times a year the event is expected (0.5 means once every two years).
  • Annualized loss expectancy (ALE) = SLE × ARO.

Made-up figures, for illustration only: an event would cost 100,000 dollars in all (asset value 100,000, exposure factor 100%), so SLE = 100,000. It is expected once every four years, so ARO = 0.25 and ALE = 25,000 a year. A control that costs 8,000 a year and brings ARO down to 0.05 (ALE 5,000) saves 20,000 a year in expected loss for 8,000: worth it. A control costing more each year than the loss it removes is hard to justify on money alone, though patient safety, the law and reputation may still require it.

What does HIPAA require?

The HIPAA Security Rule lists risk analysis and risk management as required implementation specifications of its security management process (45 CFR 164.308(a)(1)), together with two others, a sanction policy and information system activity review. Risk analysis and risk management mean an accurate and thorough assessment of the risks to the confidentiality, integrity and availability of electronic protected health information, and security measures that reduce those risks to a reasonable and appropriate level. The rule does not prescribe one method, and HHS guidance expects the analysis to be documented and kept up to date. A missing or outdated risk analysis is one of the findings HHS's Office for Civil Rights reports most often in its enforcement actions.

What do candidates get wrong?

  • Calling inaction "acceptance". Accepting a risk is a documented decision by someone with authority; ignoring a finding is not a response at all.
  • Choosing insurance for a risk that has a reasonable control. Transfer is beside controls, not a replacement, and it never transfers legal responsibility.
  • Confusing threat and vulnerability. The thief is the threat; the unencrypted laptop is the vulnerability.
  • Aiming for zero risk. The goal is a reasonable and appropriate level; some residual risk always remains.
  • Doing the analysis once. It is repeated regularly and after significant changes.

Summary for revision

  • Risk = likelihood that a threat uses a vulnerability × impact.
  • Mitigate with controls; transfer money through insurance or contracts; avoid by stopping the activity; accept on record.
  • Residual risk is what remains after the response.
  • ALE = SLE × ARO, and SLE = asset value × exposure factor.
  • HIPAA requires a documented risk analysis and risk management to a reasonable and appropriate level.

Sources

  • 45 CFR 164.308(a)(1), HIPAA Security Rule: security management process, risk analysis and risk management.
  • HHS Office for Civil Rights, Guidance on Risk Analysis Requirements under the HIPAA Security Rule.
  • NIST Special Publication 800-30 Revision 1, Guide for Conducting Risk Assessments; NIST SP 800-39, Managing Information Security Risk.
  • Project Management Institute, A Guide to the Project Management Body of Knowledge (PMBOK Guide): risk responses.

Related free practice questions

  • Lowering risk to an acceptable level: mitigation with controls

The site files this concept under the domain Healthcare Information and Systems Management.

Try exam-style questions

A 20-question trial exam with an explanation for every option and a score per domain, drawn from 40 free questions. No payment method needed.

Start the trial exam

Questions about the exam: CPHIMS guide · What is CPHIMS? · Exam cost · Eligibility · Passing score · Renewal · Exam day · How long to study · Is it worth it? · What is CAHIMS?

Concepts explained: HL7 v2 vs FHIR · Capitation vs fee-for-service · Safe Harbor vs Expert Determination · Incident vs problem vs change · Backup types, RTO and RPO · Privacy Rule vs Security Rule · CDS five rights · Lewin vs Kotter · SDLC and go-live strategies · Testing types · Earned value (SPI, CPI) · Structure, process, outcome · HIE models · Six Sigma vs Lean · Levels of interoperability · Bandwidth vs latency · EMTALA · RACI matrix · Build vs buy · Sunk vs opportunity cost · Data governance

The four domains: Healthcare and Technology Environments · Clinical Informatics · Healthcare Information and Systems Management · Management and Leadership

Written by Adel Moustafa, About us

Written and checked against the sources above on 22 October 2026. An independent site, not affiliated with or endorsed by HIMSS. CPHIMS® is a registered trademark of HIMSS.

CPHIMS guide Compare certifications Free practice questions Concepts explained About us Terms of Use Privacy Policy Refund Policy Contact us

© 2026 HealthITPrep. This site is not affiliated with or endorsed by HIMSS. CPHIMS is a registered trademark of HIMSS.