Threat Assessment
When to Involve Law Enforcement in a Threat
Deciding whether to call law enforcement on a healthcare threat is a judgment call surveyors and courts review. Learn the decision factors and how to document the call — either way.
Deciding whether to involve law enforcement in a healthcare threat is one of the most consequential — and most reviewed — judgment calls in a workplace violence program. Call too readily and you risk criminalizing a patient in crisis and eroding trust; hesitate when danger is real and you expose staff and the facility. The defensible answer is not a reflex either way. It is a documented decision made against defined criteria, captured whether the answer is yes or no, because surveyors and courts review the reasoning either direction.
This article lays out the factors that drive the decision, why the decision not to call is the one facilities most often fail to document, and how to keep the law-enforcement question consistent with your confidential reporting and anti-retaliation commitments.
#Why this is a documented decision, not a reflex
After an incident, two questions surface in survey and in litigation: Did the facility involve law enforcement when it should have? And if it did not, why not? Both are answerable only if the decision was made deliberately and recorded. A facility that called reflexively on every agitated patient looks indiscriminate; one that never called and then suffered an assault looks negligent. The defensible posture is a decision tied to criteria and documented in the threat assessment record.
The requirements assume a functioning decision pathway. The Joint Commission's workplace violence requirements (effective Jan. 1, 2022 for hospitals) expect a defined response and follow-up. A facility-specific plan under Texas HSC Chapter 331 requires post-incident response. Neither dictates when to call law enforcement — that is your facility's judgment to define — but both expect that the judgment is structured rather than ad hoc.
#The factors that drive the decision
The threat assessment team — or, in a genuine emergency, the responder in the moment — weighs a consistent set of factors. The clearer the imminence and the more a threat exceeds what clinical and administrative measures can contain, the stronger the case for law enforcement.
| Factor | Pulls toward involving law enforcement | Pulls toward internal management |
|---|---|---|
| Imminence | Danger is immediate; assault in progress | Concern is prospective, not acute |
| Weapon | Weapon present or credibly threatened | No weapon indicated |
| Specificity | Specific target, plan, or stated intent | Vague, diffuse frustration |
| Clinical driver | Conduct beyond a treatable acute state | Behavior driven by a manageable clinical state |
| Capacity to manage | Exceeds clinical/administrative controls | Within de-escalation and care-team measures |
| Legal obligation | A mandatory-reporting trigger applies | No reporting duty triggered |
These are decision aids, not a formula. The acutely psychotic patient and the visitor making a calculated threat may present identical words but call for very different responses — which is exactly why the decision belongs in a structured threat assessment process for non-emergent concerns, with the team weighing clinical context alongside safety.
#The emergency line is bright; the gray zone is the hard part
For imminent danger — an assault in progress, a weapon, a credible immediate threat — the decision is not really a decision: activate emergency response and 911. That line should be bright, trained, and unhesitating, and every staff member must know they have the authority to make that call.
The hard cases live in the gray zone: the discharged patient who said he would "come back and make them pay," the visitor whose escalating messages stop short of an explicit threat, the domestic situation following a patient into the building. These are where the threat assessment team earns its keep — weighing the factors, deciding on proportionate management, and, critically, documenting the reasoning.
#Documenting the decision NOT to call
The single most overlooked step is recording a decision not to involve law enforcement. Facilities reliably document calls they made; they rarely document the deliberate choice that a concern could be managed internally. Yet that is the decision discovery most often attacks: you knew about this person and chose not to call the police — show us why.
A defensible "no" record states the concern, the factors weighed, the conclusion that internal measures were proportionate and sufficient, the management plan adopted instead, and the review trigger that would change the answer. Written this way, the decision not to call reads as a reasoned clinical-and-safety judgment — not as inaction.
#Keeping this consistent with confidential reporting and anti-retaliation
A common worry is that emphasizing law-enforcement involvement undercuts a culture of internal reporting. It does not, when the policy is written correctly. A confidential reporting and anti-retaliation policy protects staff who raise concerns and must never be read to discourage anyone from calling 911 in an emergency. The two coexist explicitly: encourage internal reporting and preserve every staff member's right and authority to summon law enforcement when safety requires it. Spell both out so no employee ever believes that "we handle things internally" means they cannot dial 911.
#Coordinating the relationship in advance
The time to define the facility's relationship with law enforcement is before a crisis. Establish — within the WVP plan and in coordination with risk, legal, and security/safety leadership — who decides, who places the call, what information is shared, and how the facility's role as a caregiving institution shapes the handoff. This is a compliance and coordination function, not the creation of an investigative or guard capability; the facility convenes and decides, it does not police.
#How VIGILO helps
VIGILO helps facilities build the law-enforcement decision into the written WVP plan and policies and the threat assessment program — defining the emergency line, the gray-zone factors, the document-the-decision-either-way discipline, and language that keeps the call consistent with confidential reporting and anti-retaliation commitments. The framework is coordinated with your risk and legal functions, trained through staff education, and refreshed in an annual program review. For Texas facilities it aligns with HSC Chapter 331. To pressure-test your current decision pathway, start with the Chapter 331 compliance checklist.
VIGILO provides compliance, training, and consulting assistance and supports survey-readiness and preparedness; it does not provide legal advice, does not guarantee safety outcomes, and does not provide security guard, patrol, or investigative services. Law-enforcement decisions should be coordinated with your risk, legal, and security/safety functions. Sources: The Joint Commission Workplace Violence Prevention requirements (defined response and follow-up; effective Jan. 1, 2022 for hospitals); Texas Health & Safety Code Chapter 331 (SB 240, 88th Leg., 2023) and 26 TAC §133.55; OSHA General Duty Clause §5(a)(1) and Publication 3148.