Metrics & Leadership
Incident Data Quality: The Foundation of WVP Metrics
Why incident data quality and completeness decide whether your workplace violence metrics hold up — the capture, completeness, and integrity practices surveyors and boards rely on.
Incident data quality and completeness decide whether your workplace violence metrics mean anything: every board scorecard, trend, and benchmark is only as good as the incidents actually captured. Underreporting and inconsistent fields can make a deteriorating environment look safe — so data quality is the foundation the entire measurement program rests on, not a back-office detail.
This article supports our pillar, the metrics every hospital board should see. It is written for the risk manager, safety director, and quality lead who own the incident data set and have learned the hard way that a polished dashboard built on thin data is worse than no dashboard at all.
#The foundation problem
It is tempting to start a metrics program at the dashboard. But a trend line, a board KPI, and a peer benchmark all sit on the same base layer: the individual incidents staff did or did not report, recorded well or recorded badly. If that base is incomplete or inconsistent, everything above it is unreliable — and dangerously so, because a clean-looking chart projects false confidence.
The Joint Commission's workplace violence requirements (effective January 1, 2022 for hospitals; TJC R3 Report Issue 45) presume a trustworthy data set when they call for reporting, tracking, and trending. Texas Health & Safety Code Chapter 331 routes that data to the governing body (SB 240, 88th Leg., 2023). Neither obligation is met by data that is silently incomplete.
#Why healthcare workplace violence is underreported
The single biggest data-quality threat is underreporting, and its causes are cultural before they are technical:
- A normalized belief that assault is "part of the job," especially in the ED and behavioral health.
- Fear of retaliation or of being seen as unable to handle patients.
- Cumbersome reporting tools that cost more time than staff will spend.
- Genuine uncertainty about what counts as a reportable incident.
This is why a confidential reporting and anti-retaliation policy is not only a compliance requirement under Chapter 331 — it is a data-quality control. The statute bars discipline or retaliation against good-faith reporters and forbids discouraging staff from contacting law enforcement; both provisions directly attack the fear-and-culture causes of missing data. A strong reporting policy makes the data more complete, which makes every metric above it more trustworthy.
#Reading the reporting rate correctly
Because of underreporting, the reporting rate has to be read as a culture signal before it is read as a risk signal. A rising count of reported incidents often means the reporting culture is improving, not that violence is increasing. The sector scale tells you the events are out there to be captured: the healthcare workplace-violence injury rate ran roughly 5x the private-sector average in 2018 (BLS, 2018, via NIOSH/CDC), and healthcare absorbs roughly three-quarters of nonfatal intentional-violence injuries with days away from work (BLS, recent years).
So a healthy program wants reports going up while it watches severity and injury rate to judge whether the environment is actually improving. Pairing the two — reporting volume as culture, severity as outcome — is the leading-versus-lagging discipline applied to the question of whether your data can be trusted.
#Completeness: finding the incidents you never logged
Completeness is the other half of data quality, and it is testable. Triangulate your incident log against other records that should agree with it:
| Cross-reference | What a mismatch reveals |
|---|---|
| OSHA 300 log | Injury events recorded for OSHA but missing from the WVP log |
| ED / behavioral health notes | Behavioral emergencies and restraints that involved staff aggression but were never reported as WV |
| Security / EOC records | Events handled operationally but never captured as incidents |
| Workers'-comp claims | Assault-related claims with no matching incident report |
Every mismatch is a hole in the data — an event that happened but never reached the metrics. Closing those holes is one of the highest-value, lowest-cost things a program can do, and it is exactly the kind of completeness audit a defensible worksite analysis relies on.
#Field-level integrity: consistent, complete, current
Beyond capturing the right number of incidents, each record has to be usable. Field integrity practices that keep the data set trend-ready:
- Consistent required fields — type, unit, shift, severity band, antecedent — so the data can be cut every way the trend needs.
- A controlled vocabulary rather than free text for the dimensions you trend, so "ED," "Emergency," and "ER" do not fragment into three units.
- Timely entry, so the record is captured while detail is fresh and the post-incident response is documented.
- A periodic field-completeness audit — sample recent incidents and score how many fields are complete and consistent.
These integrity practices are what let the trending analysis slice the data cleanly. Without them, even a complete set of incidents resists analysis.
#Common data-quality mistakes
- Building a dashboard before auditing the data — confident charts on incomplete capture.
- Reading a reporting rise as a violence rise instead of a culture signal.
- Never cross-referencing the WV log against OSHA, ED, security, and comp records.
- Free-text dimensions that fragment the data and break trending.
- Treating the reporting policy as paperwork rather than the data-quality control it is.
- Stats without a year or denominator, which no amount of clean capture can rescue.
#How VIGILO helps
VIGILO treats data quality as the foundation of the metrics program — auditing reporting completeness, cross-referencing the incident log against OSHA, ED, security, and comp records, and tightening field integrity so the trends and board metrics built on top are trustworthy. This is compliance and survey-readiness assistance, not a guarantee of any safety outcome, and VIGILO operates strictly as a compliance, training, and consulting firm.
To strengthen the data your metrics rely on, start with a flat-fee survey-readiness audit, or maintain it through an annual program review. For what the clean data then drives, see trending incident data the way surveyors expect.
Sources: Texas Health & Safety Code Chapter 331 (SB 240, 88th Leg., 2023); The Joint Commission Workplace Violence Prevention requirements (effective Jan. 1, 2022 for hospitals; R3 Report Issue 45); OSHA General Duty Clause §5(a)(1) and Publication 3148; BLS 2018 incidence data via NIOSH/CDC. This article is general compliance information, not legal advice.