Tarasoff and HIPAA: Duty to Warn vs. Patient Privacy Explained

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

Tarasoff and HIPAA: Duty to Warn vs. Patient Privacy Explained

Kevin Henry

HIPAA

May 10, 2026

7 minutes read
Share this article
Tarasoff and HIPAA: Duty to Warn vs. Patient Privacy Explained

Overview of the Tarasoff Duty to Warn

The Tarasoff doctrine arose from landmark California cases that reframed a clinician’s responsibilities when a patient threatens violence. It evolved from a narrow “duty to warn” potential victims to a broader Duty to Protect them through reasonable steps tailored to the risk.

The duty is typically triggered when you learn of a serious, credible threat against an identifiable person or group. Once triggered, you must take reasonable steps to prevent harm, which may include warning the intended victim, notifying law enforcement, increasing clinical supervision, adjusting treatment, or arranging hospitalization.

States differ: some impose a mandatory duty, others make warning or protection permissive, and a few limit or define it narrowly. Always align your actions with your state’s statutes, case law, and professional ethics while documenting your Good Faith Belief and reasoning.

HIPAA Privacy Rule Exceptions

HIPAA generally protects a patient’s Protected Health Information (PHI). However, it allows a targeted Health and Safety Disclosure under the Imminent Threat Exception when you believe, in good faith, that disclosure is necessary to prevent or lessen a serious and imminent threat to health or safety.

The “serious and imminent threat” standard

Under this exception, you may share PHI with those reasonably able to prevent or lessen the threat—commonly the identifiable target, law enforcement, or other providers positioned to intervene. Your disclosure should be grounded in a Good Faith Belief based on your professional judgment and the facts available at the time.

Other relevant HIPAA permissions

  • Required by law: HIPAA permits disclosures when another law compels you to act (for example, certain state Tarasoff statutes or court orders).
  • Law enforcement and public safety: Limited disclosures are permitted to support active safety interventions or locate a suspect when tied to the threat.
  • Minimum necessary: Except where inapplicable (such as for treatment), disclose only the information reasonably necessary to achieve the protective purpose.

Balancing Patient Confidentiality and Safety

Your clinical task is to balance therapeutic confidentiality with the duty to prevent harm. Begin by assessing the threat’s specificity, intent, means, proximity in time, and potential targets, and by weighing protective factors and alternatives to a Confidentiality Breach.

  • Use a structured risk formulation and consult supervisors or legal counsel when feasible without delaying urgent action.
  • Prefer the least intrusive intervention that still protects safety; escalate only as needed.
  • Limit disclosures to what is necessary, preserve the therapeutic alliance when possible, and explain to the patient why safety measures are required.
  • Document the assessment, your Good Faith Belief, the options considered, and the Reasonable Steps taken.

HIPAA sets a federal privacy floor, but state law defines and often expands your duties under Tarasoff. Where state law is more stringent or imposes a duty to warn/protect, you must follow it. HIPAA does not block disclosures that are required by law or that fit the Imminent Threat Exception.

  • State variability: Some states mandate warning or protection; others provide permission and immunity when you act in good faith; a few have narrower duties.
  • Protected populations and settings: Rules can differ for minors, campus settings, and involuntary treatment contexts.
  • Other federal rules: Substance use disorder records may be subject to additional protections beyond HIPAA, requiring careful analysis before disclosure.
  • Telehealth and licensure: When treating across state lines, the patient’s location often controls the applicable Tarasoff framework.

In practice, follow the most protective rule that applies, verify any mandatory steps in your jurisdiction, and ensure your actions remain consistent with professional standards.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Procedures for Breaching Confidentiality

When safety concerns rise to the level of a potential Confidentiality Breach, use a clear, defensible workflow to ensure compliance and patient protection.

  1. Recognize and triage: Identify specific threats, targets, means, and time frame. Prioritize immediate safety if danger appears imminent.
  2. Formulate risk: Record the clinical facts, direct quotes, and your risk rating. State your Good Faith Belief and the legal-ethical basis for considering a Health and Safety Disclosure.
  3. Consult rapidly: When time allows, consult a supervisor, risk manager, or counsel. Do not delay urgent protective action.
  4. Select Reasonable Steps: Choose interventions proportionate to the risk—safety planning, increased contact, voluntary or involuntary hospitalization, warning the target, and/or notifying law enforcement.
  5. Limit PHI: Share only the minimum necessary details with individuals reasonably able to prevent or lessen the harm.
  6. Document thoroughly: Note who you contacted, what was disclosed, when, why, and how it was intended to reduce risk. Capture unsuccessful contact attempts and follow-up plans.
  7. Follow up: Reassess risk, adjust treatment, and continue coordination with involved parties until the acute threat resolves.
  8. Debrief and improve: Review the event for policy updates, training needs, and EHR workflows that can streamline future responses.

Implications for Healthcare Providers

Managing Tarasoff and HIPAA decisions impacts clinical outcomes, liability exposure, and patient trust. Clear policies, team training, and ready access to legal support reduce errors on both under- and over-disclosure.

  • Risk management: Standardize assessments, escalation pathways, and after-hours coverage for threat reporting.
  • Clinical quality: Embed checklists for the Imminent Threat Exception and “minimum necessary” prompts in your EHR.
  • Workforce readiness: Conduct drills and case reviews so staff can act decisively and document their Good Faith Belief and Reasonable Steps.
  • Trust and transparency: Explain limits of confidentiality at intake and revisit them when risk emerges to preserve the therapeutic alliance.

Case Studies Illustrating Tarasoff and HIPAA Interactions

Case 1: Specific threat with means

A patient identifies a former coworker by name, describes a plan, and has access to a weapon. You determine an imminent risk. You warn the named target and notify law enforcement, disclose only essential PHI, arrange same-day evaluation, and document your rationale and contacts.

Case 2: Vague anger, no plan

A patient expresses rage at “people at work” but denies intent, plan, or means. You increase visit frequency, create a safety plan, obtain releases to coordinate with an in-house EAP, and monitor closely. No Health and Safety Disclosure is made because the threat is not imminent or specific.

Case 3: Third-party report

A family member reports that the patient threatened an ex-partner. You verify details, assess the patient, and conclude the risk is substantial. You notify law enforcement and attempt to warn the identifiable target, sharing only minimum necessary information to reduce danger.

Together, these scenarios show how Tarasoff and HIPAA: Duty to Warn vs. Patient Privacy Explained plays out in practice—your actions should be proportionate, legally grounded, minimally intrusive, and thoroughly documented.

FAQs.

What is the Tarasoff duty to warn?

It is a legal-ethical obligation that arises when a patient makes a serious threat against an identifiable person. Depending on your state, it may impose a Duty to Protect through Reasonable Steps—such as warning the target, notifying law enforcement, modifying treatment, or arranging hospitalization.

How does HIPAA allow exceptions to patient privacy?

HIPAA permits a targeted Health and Safety Disclosure under the Imminent Threat Exception when you have a Good Faith Belief that sharing limited PHI is necessary to prevent or lessen a serious and imminent threat, and you disclose it to someone reasonably able to help avert the harm.

Common situations include a serious and imminent threat to health or safety, disclosures required by law (such as a state Tarasoff statute or court order), and certain law-enforcement or public-safety contexts. In all cases, limit disclosures to the minimum necessary to accomplish the protective purpose.

Risks include HIPAA penalties for improper PHI disclosures and civil liability or licensure actions for either failing to protect when required or over-disclosing without legal justification. Many states offer immunity when you act in good faith and take Reasonable Steps consistent with applicable law and professional standards.

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Related Articles