The current offer is anonymous web reporting for K–12 schools, companies, and hospitals. See the price and file a sample.
Workplace violence & employee safety for hospitals
NOW IMS connects protected reporting to human-led triage, investigation, post-incident follow-up, and program oversight—without losing ownership between departments or facilities.
Requirement sources reviewed August 18, 2026 · Operational information, not legal advice
01 / Operational response
Replace disconnected hotlines, inboxes, spreadsheets, and handoffs with a controlled response record that shows what was reported, who owns the next action, and what changed because of it.
Explore the platformProtected employee channel · Emergency department
Risk signals can be surfaced. People decide and act.
02 / Current requirement landscape
The exact obligations depend on facility type, location, accreditation, workforce, and facts. These are the current anchors we would map with your hospital team.
Texas Health and Safety Code Chapter 331 requires covered facilities to establish or authorize a committee and maintain a written workplace violence prevention policy and practice-setting plan. The plan addresses training, response and investigation, security, employee input, reporting, annual review, and governing-body reporting.
Read Chapter 331The HHSC rule applies Chapter 331 within hospital licensing and specifies committee membership, written policy and plan elements, annual evaluation, post-incident services, access to the plan, and protections for good-faith reporting. It transferred from 25 TAC §133.55 in 2025.
For hospitals and critical access hospitals, the NPG chapter became effective January 1, 2026. NPG #2a addresses multidisciplinary program ownership, incident reporting and trend analysis, support for victims and witnesses, governing-body reporting, worksite analysis, and training.
OSHA says there is no specific federal workplace violence standard. Its General Duty Clause can apply to recognized serious hazards with feasible abatement, while injury recordkeeping and severe-event reporting obligations remain separate. OSHA recommends accurate incident and close-call records for program evaluation.
Important: This page summarizes operational requirements for planning purposes and is not legal, regulatory, accreditation, or clinical advice. Confirm applicability and implementation with qualified counsel, regulators, accreditors, and your hospital’s responsible leaders.
03 / Requirement-to-workflow map
Offer protected web, SMS, voice, and staff-assisted channels; preserve reporter preferences; allow controlled follow-up.
Assign human owners, record acknowledgement, coordinate actions, retain evidence, and escalate using hospital-defined rules.
Track whether immediate services, workforce support, law-enforcement rights, communications, and corrective actions were addressed.
Keep plans, incidents, trends, actions, and review evidence distinctly identifiable while giving authorized leaders a system-level view.
04 / Trust by design
Anonymous and confidential paths can be configured with secure follow-up and conflict-aware routing.
Role and facility boundaries help limit sensitive information to the people responsible for the work.
Assignments, changes, actions, approvals, and closure remain connected to the incident record.
NOW Neo can organize information and surface signals. People own emergency, employment, clinical, and disclosure decisions.
05 / Clear boundaries
NOW IMS coordinates organizational reporting and response. It is not emergency dispatch, a panic alarm, a hospital code system, clinical care, an EHR, or an automatic compliance determination.
06 / Questions
Covered facilities must establish or authorize a workplace violence prevention committee and adopt, implement, and enforce a written policy and practice-setting plan. The plan includes annual training for direct-patient-care personnel, a system for response and investigation, physical security and safety, worker input, reporting through occurrence systems, annual review, and governing-body reporting. Hospitals should confirm the requirements that apply to their facility with counsel and regulators.
No software makes an organization compliant by itself. NOW IMS can support reporting, assignment, investigation, documentation, follow-up, and governance evidence. Hospital leaders, committees, legal counsel, and clinical and security teams remain responsible for the program, safeguards, decisions, training, and required reporting.
Hospitals can configure protected web, SMS, and voice channels, including anonymous reporting and secure follow-up. Access, routing, and escalation can be limited by role and facility. The hospital determines the reporting design and notices appropriate to its workforce and jurisdiction.
No. NOW IMS is not 911, a panic alarm, a hospital code system, an electronic health record, or a substitute for immediate clinical care or security response. Emergencies must use the hospital’s designated emergency channels.
Yes. NOW IMS can support system-level oversight while preserving facility-specific routing, plans, incidents, actions, and reporting. That distinction matters in Texas, where a system committee may serve multiple facilities only if it develops a plan for each facility and keeps violence-prevention data distinctly identifiable by facility.
The hospital must define what information belongs in the system and complete the appropriate privacy, security, contracting, and data-flow review. If NOW IMS would create, receive, maintain, or transmit electronic protected health information on behalf of a covered entity, HIPAA business-associate requirements may apply. Do not put patient names, PHI, or incident details in this marketing form.
07 / Private working session
Bring the facilities, reporting paths, teams, review cycle, and governance evidence you need to connect. We’ll focus the walkthrough on your operating model.