Washington's RCW 49.19: Investigating Every Violent Incident in a Healthcare Setting

If you know California's workplace violence rules and assume Washington works the same way, you will build the wrong process. Both states require a violent incident log. What they ask you to do next is almost opposite in shape.

The short answer

Under RCW 49.19, a Washington healthcare employer keeps a violent incident record and investigates every incident, bringing a recurring data summary to its safety committee. There is no severity-keyed reporting clock to a state portal in the way California has one. The obligation is continuous rather than triggered.

Log and report, versus log and investigate

It is worth naming the two designs, because they lead to different staffing and different software.

California's model is triggered. Every incident is logged, and a subset crosses a severity threshold that starts a 24-hour or 72-hour clock to notify the Division. Most of the operational pressure sits on recognising the trigger fast enough. Miss it and you have a citation; get it right and many incidents need nothing further.

Washington's model is continuous. Every incident gets investigated. Nothing is beneath attention. There is no clock to sprint against, but there is also no incident that quietly closes itself, and the safety committee expects to see the pattern on a recurring basis rather than a case at a time.

Neither is lighter. They fail differently: California programs fail by missing a deadline, Washington programs fail by accumulating a backlog of uninvestigated incidents that becomes visible at a committee meeting.

What the investigation has to do

An investigation that satisfies a safety committee, and an inspector, generally establishes:

• What happened, in enough detail to distinguish it from superficially similar incidents.
• The circumstances: staffing at the time, physical environment, whether the patient had a known history, whether de-escalation was attempted.
• What, if anything, would plausibly have prevented it.
• What was changed as a result, or a recorded decision that nothing needed changing and why.

That last point is the one people skip. An investigation with no outcome recorded is indistinguishable, months later, from an investigation that never happened.

The recurring summary

The data summary to the safety committee is the part that most rewards having the records in a system rather than a folder. A committee is not looking at individual incidents; it is looking for concentration. Which unit, which shift, which type of incident, which category of assailant, trending which way.

If your log is a spreadsheet, producing that summary is somebody's afternoon every reporting period, and it will be produced late when the afternoon is not available. If the incidents are records, it is a query.

Washington does not require a separate sharps injury log

A detail worth knowing if you operate in both states, because it runs the other way from what people expect. California requires a sharps injury log separate from the 300, with its own fields and its own five-year clock. Washington folds sharps recording into the 300.

So a system that offers a Washington hospital a separate sharps log screen is not being generous. It is inviting a team to maintain a document they have no duty to keep, and to wonder why an inspector never asks for it.

Reporting a serious injury in Washington

Washington operates its own eight-hour reporting clock for serious incidents, separate from the violent incident obligations above. As always, reportability to the regulator and recordability on the 300 Log are different questions with different answers, and folding them into one decision makes both wrong.

If you operate in both states

• Keep one log format. The fields are close enough that a single record works, and it means an incident does not have to be re-entered to satisfy a second regime.
• Do not share a process. The California site needs somebody empowered to notify the Division within 24 hours. The Washington site needs an investigation queue that never grows. These are different jobs.
• Do not give either site the other's screens. A Washington team shown California's reporting clocks will either ignore them or act on them, and both are bad.

What to check this quarter

• How many incidents in the last quarter have a completed investigation with a recorded outcome?
• When did the safety committee last see a data summary, and was it produced from records or assembled by hand?
• Can you show, for any single incident, what changed as a result or why nothing did?

carefoundryESC records the incident once and generates each state's obligations from it: Washington's investigation and committee summary, California's clocks, and the OSHA case underneath both. See how jurisdiction compliance works, or the state-by-state overview.

Verify against the statute

This is an overview, not legal advice. Read the current text of RCW 49.19 and the Department of Labor and Industries guidance before designing a process around it.