HIPAA Risk Assessment for Case Managers: Step-by-Step Guide and Checklist

Product Pricing
Ready to get started? Book a demo with our team
Talk to an expert

HIPAA Risk Assessment for Case Managers: Step-by-Step Guide and Checklist

Kevin Henry

Risk Management

December 02, 2025

9 minutes read
Share this article
HIPAA Risk Assessment for Case Managers: Step-by-Step Guide and Checklist

HIPAA Risk Assessment Overview

A HIPAA risk assessment helps you identify how protected health information moves through your case management activities, where it could be exposed, and which safeguards will reduce that risk. It covers both paper records and electronic protected health information (ePHI) across your tools and workflows.

For case managers, the scope often spans care coordination platforms, EHR access, email, texting, telehealth, cloud storage, and community referrals. Mapping these touchpoints shows how ePHI is created, received, maintained, and transmitted—and where vulnerabilities may exist.

  • Common ePHI sources: EHR notes, care plans, assessment forms, referral packets, eligibility documents, and discharge summaries.
  • Common channels: secure messaging, email, fax, patient portals, mobile apps, and shared drives.
  • Common devices: laptops, smartphones, tablets, home printers/scanners, and removable media.

Leadership is accountable for HIPAA compliance, but you play a central role. A designated Privacy and Security Officer coordinates the program, ensures policies are current, and supports investigations and training. Your documentation, escalation, and day‑to‑day choices directly influence risk.

The main outputs are a documented risk analysis, a prioritized risk management plan, and updated policies. You will also rely on audit logs to monitor access, maintain current Business Associate Agreements, and make sure clients receive and understand the Notice of Privacy Practices.

Steps in Conducting a HIPAA Risk Assessment

Step-by-step checklist for case managers

  • Define scope: list systems, apps, paper files, and devices used to handle PHI, including remote and field work.
  • Map data flows: show where PHI/ePHI is collected, who touches it, how it’s shared, and where it’s stored or archived.
  • Identify threats and vulnerabilities: human error, misdirected emails/faxes, lost devices, weak passwords, unsecured Wi‑Fi, overbroad access, and risky vendor tools.
  • Evaluate existing safeguards: administrative policies, physical protections, and technical controls already in place.
  • Analyze likelihood and impact: rate each risk (low/medium/high) to prioritize what to fix first.
  • Create a risk management plan: define mitigation actions, owners, timelines, and success metrics.
  • Implement controls: update policies, train staff, enable technical protections, and execute Business Associate Agreements where needed.
  • Monitor and maintain: use audit logs, spot checks, and periodic reviews to verify controls are working.
  • Report and iterate: summarize progress to the Privacy and Security Officer and update the plan after incidents or changes.

Practical tips

  • Limit content to the minimum necessary; avoid PHI in subject lines or calendar invites.
  • Use secure messaging/portal links instead of attachments when possible.
  • Confirm that every vendor touching ePHI has signed compliant Business Associate Agreements.
  • Adopt multi‑factor authentication and strong passphrases for all systems with ePHI.

Administrative Safeguards

Administrative safeguards are the policies, procedures, and governance that guide how you protect PHI. They clarify who can access what, how incidents are handled, and how you keep knowledge current through training and audits.

  • Governance: appoint and empower a Privacy and Security Officer; review the compliance program at least annually.
  • Policies: minimum necessary, role‑based access, sanction policy, remote work, device use, and data retention.
  • Workforce management: screening, onboarding, training, and documented competency for HIPAA topics relevant to case managers.
  • Vendor oversight: maintain current Business Associate Agreements before sharing any ePHI with external services.
  • Operational workflows: identity verification, accurate authorization, and standardized release-of-information steps.
  • Contingency planning: backup, emergency operations, and downtime procedures for client care continuity.
  • Incident handling: reporting paths, triage criteria, documentation templates, and a tested breach response plan.
  • Program improvement: translate findings from audits and incidents into the living risk management plan.

Case manager checklist

  • Confirm a current policy set exists and you know where to find it during field work.
  • Verify recipient identity before sharing PHI; double‑check addresses and fax numbers.
  • Use only approved systems for PHI; no personal cloud drives or texting apps without authorization and BAAs.
  • Document disclosures and client preferences; escalate unusual requests to the Privacy and Security Officer.
  • Complete required training and attestations on schedule.

Physical Safeguards

Physical safeguards prevent unauthorized hands-on access to PHI, whether you are in a clinic, at home, or in the community. They cover buildings, workstations, devices, and paper records.

Ready to assess your HIPAA security risks?

Join thousands of organizations that use Accountable to identify and fix their security gaps.

Take the Free Risk Assessment
  • Facility access: badge controls, visitor logs, and locked storage for paper files and removable media.
  • Workstation security: privacy screens, auto‑lock timers, and clean‑desk practices that keep PHI out of view.
  • Device and media controls: check‑in/check‑out logs, secure transport, disposal/shredding, and inventory tracking.
  • Mobile safeguards: never leave devices in cars; use carrying cases and enable full‑disk encryption and remote wipe.
  • Home and field practices: store paper in locked containers, avoid printing when feasible, and secure home printers/scanners.
  • Fax/print safety: confirm numbers, use cover sheets, and promptly retrieve printed PHI.

Technical Safeguards

Technical safeguards protect ePHI within systems and over networks. They include access control, encryption, monitoring, and protections against alteration or unauthorized transmission.

  • Access control: unique user IDs, least‑privilege roles, and timely removal of access when duties change.
  • Authentication: multi‑factor authentication for all ePHI systems; use a password manager for strong credentials.
  • Automatic logoff: short inactivity timeouts on laptops, mobile devices, and web apps.
  • Encryption: data encrypted at rest on devices and in transit via TLS; use secure portals for sharing files.
  • Device management: mobile device management with remote lock/wipe and enforced updates.
  • Audit controls: enable and review audit logs for access, downloads, printing, and after-hours activity.
  • Integrity controls: hashing/checksums, versioning, and restricted edits to safeguard data accuracy.
  • Transmission security: avoid unencrypted email/texting of PHI; if used, apply approved secure messaging with recipient verification.
  • Resilience: routine backups, tested restores, and patching to address known vulnerabilities.

Monitoring with audit logs

Use audit logs to flag unusual patterns, such as repeated access to VIP or former client records, bulk exports, or access outside assigned panels. Review logs on a set cadence and after any reported incident, and document the results and actions taken.

Breach Notification and Response

Your breach response plan defines how to recognize, investigate, and report privacy or security incidents. Not every incident is a breach, but each one requires prompt assessment and thorough documentation.

  • Contain and preserve: secure the system or record, stop further disclosure, and preserve audit logs and messages.
  • Notify quickly: alert your supervisor and the Privacy and Security Officer immediately; do not delete evidence.
  • Investigate: determine what PHI was involved, who received it, whether it was actually viewed or acquired, and mitigation steps taken.
  • Assess breach status: apply the HIPAA risk factors; if breach, initiate required notifications.
  • Notify affected individuals: provide content that explains what happened, what information was involved, steps taken, and how to get help.
  • Regulatory reporting: coordinate notices to regulators and, when applicable, the media.
  • Document and improve: record timelines, decisions, and lessons learned in the risk management plan.

60‑day timeline and thresholds

  • Notify individuals without unreasonable delay and no later than 60 days from discovery.
  • For breaches affecting 500 or more residents of a state/jurisdiction, notify HHS and prominent media outlets within 60 days.
  • For fewer than 500 individuals, report to HHS annually within the required window.
  • Business associates must notify the covered entity; covered entities notify individuals and regulators.
  • Law enforcement requests can delay notice when properly documented.

Case manager scenario

A referral email with a full clinical summary is accidentally sent to the wrong agency. You immediately recall the message if possible, inform the Privacy and Security Officer, preserve the email and logs, contact the unintended recipient to request deletion, and document the outcome. The organization conducts the breach assessment, sends required notifications if needed, and updates training and templates to prevent a repeat.

Client Rights and Communication

Clients have specific HIPAA rights, and your role is to explain options, verify identity, respect preferences, and document actions. Clear, empathetic communication builds trust and reduces risk.

  • Right of access: provide timely access to records in the requested format when feasible; verify identity first.
  • Amendment: help clients request corrections; route to clinical leadership when applicable.
  • Restrictions: honor reasonable requests to limit disclosures and note them in the record.
  • Confidential communications: accommodate alternate addresses or channels when safety or privacy is a concern.
  • Accounting of disclosures: record non‑routine disclosures so the organization can produce an accounting on request.
  • Notice of Privacy Practices: ensure the client receives, understands, and acknowledges the Notice of Privacy Practices.

Communication best practices

  • Confirm who you are speaking with before sharing PHI; use two identifiers.
  • Follow the minimum necessary standard; avoid over‑sharing in emails, texts, and voicemails.
  • Use approved secure channels first; if a client insists on unsecure methods, document their preference per policy.
  • Accommodate language needs and accessibility; provide plain‑language explanations.
  • Document every disclosure, preference, and exception; escalate complex questions to the Privacy and Security Officer.

Conclusion

A strong HIPAA risk assessment translates your daily case management work into clear safeguards and accountable actions. By mapping data flows, prioritizing risks, executing a practical risk management plan, maintaining current Business Associate Agreements, and following a tested breach response plan, you protect clients and your organization while enabling coordinated, person‑centered care.

FAQs

What are the key steps in a HIPAA risk assessment for case managers?

Define scope and map PHI flows, identify threats and vulnerabilities, evaluate current safeguards, analyze likelihood and impact, and prioritize actions in a written risk management plan. Implement controls, train staff, enable audit logs, monitor results, and update the plan after incidents or operational changes.

How do administrative safeguards protect PHI?

They set the rules and accountability for handling PHI: appointing a Privacy and Security Officer, enforcing minimum necessary and role‑based access, maintaining Business Associate Agreements, training the workforce, planning for contingencies, and running a documented incident process that feeds improvements back into the program.

What is required in a breach notification and response plan?

A clear triage and escalation path, preservation of evidence and audit logs, documented risk assessment of incidents, defined notification content and timelines, regulator and media thresholds, roles for covered entities and business associates, and a continuous improvement loop to update policies and training.

How often should HIPAA risk assessments be conducted?

Assess at least annually and whenever you introduce new technology, vendors, locations, or workflows—or after any significant incident. Routine monitoring and periodic audits help you verify that safeguards remain effective between formal assessments.

Share this article

Ready to assess your HIPAA security risks?

Join thousands of organizations that use Accountable to identify and fix their security gaps.

Take the Free Risk Assessment

Related Articles