OSHA Compliance
Prepare for a Federal WVP Standard Without Betting Your Program
How to position your healthcare workplace violence program for a future federal OSHA standard without delaying compliance on a rulemaking date you cannot control.
You should not wait for a federal OSHA workplace violence rule before building your program — and you do not need to gamble that one arrives on schedule. The smarter posture is to build to the convergent core that today's obligations and any plausible future standard share, so a published rule becomes an addition to your binder rather than a reason to start over.
#The timing trap
OSHA's healthcare workplace violence rulemaking is active, not shelved: the SBREFA small-business review panel concluded in March 2023, and the agency's regulatory agenda has listed a proposed rule anticipated in April 2026 addressing Type II violence in healthcare and social assistance (Source: OSHA Workplace Violence). But an agenda date is a target, not a promulgated standard, and federal rulemakings routinely slip by years.
Two failure modes follow from treating the date as decisive. Facilities that wait leave themselves exposed to the obligations that already exist. Facilities that over-build to a guess about the rule's contents risk reworking a program when the final text differs. The way out of both is to build to what is already required and already convergent, because that core is what any future rule will be built on top of.
#What is already binding — today
A federal standard is not the floor; it would be a ceiling raised on top of duties that already apply:
- The General Duty Clause §5(a)(1) already makes workplace violence a citable recognized hazard for hospitals, enforced through CPL 02-01-058 and evaluated against Publication 3148.
- Texas HSC Chapter 331 (the SB 240 mandate, effective September 1, 2024) already requires covered Texas facilities to have a written workplace violence prevention plan, a committee, training, and an annual plan evaluation.
- The Joint Commission workplace violence requirements (EC, HR, and LD chapters, effective January 1, 2022 for hospitals) already require a program, worksite analysis, training, and incident tracking.
A facility waiting on the federal rule is already non-compliant with three regimes. The rule is not the reason to act; it is one more reason among several that already exist.
#The convergent core every regime shares
Strip the federal proposal, Chapter 331, the Joint Commission standards, and existing state rules down to their common elements and the same six-part structure appears every time:
| Convergent element | Already required by |
|---|---|
| A written WVP program / plan | Chapter 331; Joint Commission; OSHA 3148 |
| A dated worksite analysis | Chapter 331; Joint Commission; OSHA 3148 |
| A hazard-control log tying controls to hazards | OSHA 3148; General Duty Clause abatement |
| Training at defined intervals | Chapter 331; Joint Commission; OSHA 3148 |
| Recordkeeping reconciled to injury logs | 29 CFR 1904; OSHA 3148 |
| An annual program evaluation | Chapter 331; Joint Commission; OSHA 3148 |
This is the structure of the five Publication 3148 components, and it is almost certainly the spine of any federal rule, because OSHA's own framework and the existing state standards already use it. Build to this core and you are not betting on the rule's contents — you are building the part that cannot reasonably change.
#Design the documentation to absorb new requirements
Future-proofing is as much about structure as content. A program built as a single monolithic document is expensive to amend; a modular program of record absorbs a new requirement as a new section.
Three design choices make the difference:
- Map to a stable framework. Organize the binder under the Publication 3148 headings. When a new requirement appears, it slots under an existing component instead of forcing a reorganization.
- Keep a crosswalk. Maintain a requirements crosswalk that shows which document satisfies which regime. When a federal rule lands, you add a column rather than re-reading every page.
- Version everything. Dated version control and sign-offs let you demonstrate when each element was added — the evidence that the program evolved deliberately rather than scrambling after the fact.
#Watch the rulemaking without anchoring to it
Preparation is not passivity. Assign someone to track the rulemaking on OSHA's regulatory agenda and read the proposed text if and when it publishes, because the comment period is the moment to understand scope, applicability, and timelines. But decouple that monitoring from your build schedule. The program ships on the cadence the current obligations demand; the rulemaking informs refinements, not the decision to start.
If the rule does publish, a facility already built to the convergent core runs a gap analysis against the final text, adds the deltas as tracked corrective actions, and updates its crosswalk — a matter of weeks, not a rebuild.
#The one bet worth making
The only defensible bet is that the direction of regulation is settled even though the date is not. Every signal — the General Duty Clause enforcement posture, the state standards already on the books, Texas Chapter 331, and the contents of OSHA's own guidance — points the same way: written program, worksite analysis, controls, training, recordkeeping, evaluation. Building to that today satisfies what already binds you and positions you for what is coming, with no wasted motion either way.
If you want to know how close your current program already is to that convergent core, a flat-fee survey-readiness audit scores it against Publication 3148, Chapter 331, and the Joint Commission in one report, and an annual program review keeps it current as the regulatory picture moves.
This article provides general compliance information, not legal advice or a guarantee of any safety or survey outcome; consult qualified counsel for your facility. Primary sources: OSHA Workplace Violence rulemaking agenda; OSH Act §5(a)(1); OSHA Publication 3148; Texas HSC Chapter 331; The Joint Commission EC/HR/LD standards.