Skip to content
HIPAA ComplianceConsulting

HIPAA Consulting Service

HIPAA Breach Response Consulting

Preparation and compliance support for security incidents involving PHI: response plans, the §164.402 breach risk assessment, notification timelines and tabletop exercises.

Reviewed Request a HIPAA Consultation

When something goes wrong with PHI — a misdirected mailing, a stolen laptop, ransomware on a file server, an employee looking up a neighbor’s chart — the clock starts at discovery. HIPAA’s Breach Notification Rule (45 CFR §§164.400–414) sets deadlines that run whether or not your team knows what to do next.

Our HIPAA breach response consulting helps you prepare before an incident and supports the compliance workstream during one. We build incident response and breach assessment procedures, rehearse them with tabletop exercises and, when an incident occurs, help structure the breach risk assessment and notification decisions. We work alongside your legal counsel and any forensic firm you retain; we are not a substitute for either.

Key points

  • An impermissible use or disclosure of PHI is presumed to be a breach unless a documented risk assessment shows a low probability of compromise.
  • Individual notice: without unreasonable delay and no later than 60 calendar days after discovery.
  • 500+ affected residents of a state or jurisdiction also triggers prominent media notice; HHS notice timing depends on the 500 threshold.
  • Security incident procedures are a required Security Rule standard under §164.308(a)(6).

Service overview

Breach response has two halves that are often confused. Incident response is the technical and operational work of containing, investigating and recovering from an event. Breach determination is the regulatory analysis of whether that event is a reportable breach of unsecured PHI, who must be notified and by when. Both need to be planned in advance, and both need clear owners.

We focus on the compliance side and the plan that connects the two: who declares an incident, who preserves evidence, when counsel is engaged, how the four-factor risk assessment is documented, and how notification letters, media notice and HHS reports are prepared and tracked.

Who needs this service

  • Covered entities without a written, tested breach response procedure.
  • Business associates that must notify covered entity customers within contractually shortened windows.
  • Organizations that have had a near miss and realized their plan did not answer basic questions.
  • Multi-state providers and digital health companies that may also face state breach notification laws or, for non-HIPAA health apps, the FTC Health Breach Notification Rule.
  • Leadership teams that want a realistic rehearsal before a real ransomware event tests them.

Regulatory considerations

Under §164.402, a breach is the acquisition, access, use or disclosure of PHI in a manner not permitted by the Privacy Rule that compromises its security or privacy. Unless an exception applies, an impermissible use or disclosure is presumed to be a breach unless the entity demonstrates a low probability that the PHI has been compromised, based on a risk assessment of at least four factors. PHI secured according to HHS guidance (for example, properly encrypted) is not “unsecured PHI” and does not trigger notification.

The four-factor breach risk assessment (§164.402)
FactorQuestions to document
Nature and extent of the PHIWhat types of identifiers and clinical or financial data were involved? How likely is re-identification?
The unauthorized personWho used or received the PHI? Are they bound by HIPAA or other confidentiality obligations?
Whether PHI was actually acquired or viewedIs there evidence (logs, forensics) that the data was accessed, or only that it was exposed?
Extent of mitigationWere assurances obtained, data retrieved or destroyed, access revoked? How effective was it?

Notification timelines

  • Individuals: without unreasonable delay and no later than 60 calendar days after discovery (§164.404).
  • Media: for breaches affecting more than 500 residents of a state or jurisdiction, prominent media outlets in that area, within the same timeframe (§164.406).
  • HHS: for 500 or more individuals, contemporaneously with individual notice; for fewer than 500, logged and reported within 60 days after the end of the calendar year (§164.408).
  • Business associates: notify the covered entity without unreasonable delay and no later than 60 days after discovery, unless the BAA sets a shorter period (§164.410).

Common breach response challenges

  • Treating the 60-day limit as the target rather than the outer boundary; the standard is “without unreasonable delay”.
  • Misjudging the discovery date, which runs from when the breach is known, or by exercising reasonable diligence would have been known, to any workforce member or agent other than the person who committed it.
  • Risk assessments that conclude “low probability” without evidence, or are never written down.
  • No contact list for counsel, forensic firm, cyber insurer and key vendors when systems are down.
  • Business associates and covered entities each waiting for the other to act.
  • Ransomware events where the team assumes no breach because data exfiltration is unconfirmed; HHS guidance treats ransomware encryption of ePHI as presumptively a breach unless a low probability of compromise is demonstrated.

Our approach

Preparation work starts with your existing HIPAA policies and procedures and incident handling practices. We map roles and decision points from first report to closure, and write a breach assessment procedure with a standard worksheet for the four factors and the regulatory exceptions.

Tabletop exercises are scenario-based, typically 2–3 hours, and built around incidents relevant to you — a lost unencrypted device, a misconfigured cloud bucket, a vendor breach, or a ransomware event that takes the EHR offline. We observe where decisions stall and turn those observations into plan updates. During a live incident, we support the documentation and notification workstreams under the direction of your counsel.

Typical deliverables

  • Incident response and breach notification plan, with roles, escalation paths and contact lists.
  • Breach risk assessment worksheet and decision log template.
  • Notification templates for individuals, media, HHS submission data and covered entity notice (for BAs), for review by counsel.
  • Tabletop exercise materials, after-action report and plan update list.
  • Breach log for incidents affecting fewer than 500 individuals, supporting annual HHS reporting.

Engagement process

  1. 1

    Current-state review

    Read existing incident and breach procedures, BAAs and insurance requirements; interview IT, compliance and privacy leads.

  2. 2

    Plan design

    Draft or revise the response plan and breach assessment procedure, aligning with counsel’s preferred process.

  3. 3

    Tabletop exercise

    Run a realistic scenario with technical, compliance, legal and leadership participants.

  4. 4

    After-action

    Document gaps observed and update the plan, templates and contact lists.

  5. 5

    Ongoing readiness

    Optional annual exercises and on-call compliance support during live incidents.

Cost factors

Scope depends on whether you need a plan written from scratch or revised, the number of tabletop exercises and participants, the number of business units or affiliated entities covered, and whether you want incident-time support available. Live incident support is typically scoped separately. Our breach notification requirements resource summarizes the rule in more detail, and findings from exercises often feed directly into HIPAA compliance remediation.

Frequently asked questions

Is every security incident a HIPAA breach?

No. A security incident is broader. A breach involves an impermissible acquisition, access, use or disclosure of unsecured PHI that is not covered by an exception and where a risk assessment does not show a low probability of compromise. Each incident still needs to be evaluated and documented.

Do you replace our breach lawyer or forensic firm?

No. Counsel handles legal advice and privilege; forensic firms handle technical investigation. We support the compliance process — documentation, risk assessment structure, notification logistics — under counsel’s direction.

If the PHI was encrypted, do we have to notify?

PHI rendered unusable, unreadable or indecipherable to unauthorized persons in line with HHS guidance is not unsecured PHI, so the notification requirements do not apply. Whether that safe harbor applies depends on the encryption method and whether the key was also compromised.

How often should we run a tabletop exercise?

HIPAA does not set a frequency for exercises. Many organizations run at least one a year and after significant changes, such as a new EHR or a major vendor change.

Does the FTC rule apply to us?

The FTC Health Breach Notification Rule applies to certain vendors of personal health records and related entities not covered by HIPAA. If you are a covered entity or acting as a business associate, HIPAA’s rule generally applies instead. Confirm your status with counsel.

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.