Texas HSC Chapter 331
Chapter 331 Confidential Reporting & Anti-Retaliation
Texas HSC Chapter 331 requires confidential incident reporting and anti-retaliation protections. Here is what your policy must say and the evidence surveyors review.
Texas Health & Safety Code Chapter 331 requires every covered facility to give staff a confidential way to report workplace violence and to protect reporters from retaliation. These are not optional culture statements — they are program elements a surveyor verifies, and the policy language that backs them is reviewed for substance, not just existence. A facility that encourages reporting in spirit but cannot point to written confidentiality and anti-retaliation provisions has a documentation gap.
This article explains what Chapter 331 expects your reporting and anti-retaliation policy to say, why surveyors and plaintiff's counsel both care, and the evidence that proves the policy is real. For the full statute, see Texas SB 240 explained. The pillar is Texas SB 240 & HSC Chapter 331 compliance.
#What the statute expects
Chapter 331 frames reporting and non-retaliation as two halves of the same requirement: staff must be able to report, and reporting must be safe to do. The written plan is expected to describe both (Texas HSC Chapter 331; SB 240, 88th Leg., 2023). In practice, that breaks into three commitments your policy must make explicit:
- A defined reporting channel. Staff must know how to report an incident — a form, a system, a designated recipient — without having to invent the path under stress.
- Confidentiality of the report. The reporting employee's information is protected to the extent the facility can protect it, so fear of exposure does not suppress reports.
- Protection from retaliation. An employee who reports a workplace violence incident in good faith — and, in defined circumstances, who declines to provide care that would expose them to a serious safety risk — may not be retaliated against for doing so.
The reason the statute pairs these is operational: underreporting is the enemy of a defensible program. If staff do not report, the facility's incident data understates the hazard, the worksite analysis is built on a false floor, and the corrective actions never target the real problem. Confidentiality and anti-retaliation are what keep the data honest.
#What your written policy must say
A surveyor reading your policy is looking for specific, actionable language — not aspiration. The policy should state, in plain terms:
| Element | What the policy language must do |
|---|---|
| How to report | Name the channel(s): the form, the system, the role to notify, and that reports can be made promptly |
| Confidentiality | State that the facility protects the confidentiality of the reporter to the extent permitted |
| Anti-retaliation | State plainly that no employee will face retaliation for a good-faith report |
| Scope of protection | Cover both reporting and, where applicable, declining unsafe care, consistent with the statute |
| No discouragement of law enforcement | Make clear the policy does not discourage an employee from contacting law enforcement when warranted |
That last row matters. A reporting policy that, in practice, routes everything through internal channels and chills calls to 911 creates both a safety problem and a litigation problem. The policy should make internal reporting easy and preserve the employee's right to involve law enforcement. For the broader policy build, see writing a WVP policy that maps to Chapter 331.
#Why surveyors and litigators both care
Confidential reporting and anti-retaliation sit at the intersection of two exposures, which is why they get attention from both directions.
At survey, the surveyor traces the thread: Does the policy exist? Do staff know how to report? Were reports actually captured? Did the committee review them? A facility can have a beautifully written policy and still fail this tracer if frontline staff, when interviewed, cannot describe how to report — the policy-to-practice gap is the most common way good policies still draw a deficiency.
In litigation, the reporting record cuts both ways. A facility that captured reports, protected reporters, and acted on the data demonstrates a program that took the hazard seriously. A facility whose staff were afraid to report — or whose log shows reports that triggered no response — hands plaintiff's counsel a narrative of a known, ignored danger. The exposure runs through licensure deficiencies and discovery, not a fine: Chapter 331 has no penalty schedule, which is precisely why the documented record is the whole game.
#The evidence that proves the policy is real
A written policy is necessary but not sufficient. The evidence set a surveyor opens the binder to find includes:
- The written reporting and anti-retaliation policy, current and version-controlled, with adoption dates.
- The reporting channel itself — the incident report form or system staff actually use, built to capture what surveyors need.
- The incident log, showing that reports were received, logged, and routed — confidentiality maintained, not abandoned.
- Training records proving staff were taught how to report and that they are protected, at orientation and annually.
- Committee minutes showing reported incidents were reviewed and that trends informed corrective action.
When those five align, the policy is demonstrably operational. When the policy exists but the log is empty, or the log shows reports with no committee follow-up, the program looks performative — and that is the impression you least want a surveyor or a jury to form.
#Common deficiencies to avoid
- A policy with no channel. It promises confidentiality but never tells staff how to report.
- Confidentiality without anti-retaliation, or vice versa. Both must be explicit; one without the other is half a requirement.
- A chilling effect on law enforcement. Language that implies internal reporting is the only acceptable path.
- An empty or stale log. Reporting is "encouraged" but the data shows almost nothing — a classic sign of underreporting the surveyor will probe.
- No committee linkage. Reports go in but never surface in minutes or corrective actions, breaking the chain from report to response.
#How to make it survey-ready
- Audit the gap with a survey-readiness audit that scores your reporting and anti-retaliation language against the Chapter 331 and 26 TAC §133.55 checklist.
- Build defensible policy through a workplace violence prevention program that pairs the written policy with a working reporting channel, an incident log, and the committee process that closes the loop.
- Keep it current with annual program reviews so the policy, the channel, and the evidence stay aligned year over year.
For a self-guided start, the Chapter 331 compliance checklist shows where the reporting and anti-retaliation evidence should live in your binder.
Confidential reporting and anti-retaliation are how a Chapter 331 program earns the honest data it needs — and how it proves, to a surveyor and to a court, that staff were safe to speak up. The policy is the promise; the log, the training, and the minutes are the proof.
Sources: Texas Health & Safety Code Chapter 331 (SB 240, 88th Leg., 2023); 26 TAC §133.55 (adopted Oct. 11, 2024); HHSC Provider Letter PL 2024-10. This article is general compliance information, not legal advice.