2,042,423Injury reports 130,778Establishments Most recent incident 2025-12-31
Safety Incidents OSHA Severe Injury Reports · 2015–2025

Enid, OK —

OSHA Injury Report: 315 INTEGRIS Health Enid Hospital

Injury · Other recordable case

At a glance

On , an injury at 315 INTEGRIS Health Enid Hospital in 600 S Monroe St, Enid, OK 73701 resulted in other recordable case. Employee was surgical Technologist Cert in hospital.

Watch 315 Integris Health Enid Hospital — free Get an email when a new federal OSHA severe-injury report for 315 Integris Health Enid Hospital is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
315 INTEGRIS Health Enid Hospital
Parent company
INTEGRIS Health
Street
600 S Monroe St
City
Enid
State
OK
ZIP
73701
On-site location
315 INTEGRIS Health Enid Hospital, Surgical Procedural, Surgery

What was the outcome?

Outcome
Other recordable case (code 4)
Type
Injury (code 1)

Before the incident

Putting K wire in sharp box

What happened

Putting away sharps in the red bin and got poked by the shark end of a kwire.

Injury or illness

Laceration Cut Tear Right 3rd Finger

Object or substance involved

dirty k wire

Summary line

Laceration Cut Tear Right 3rd Finger dirty k wire

Employee and industry

Job description
Surgical Technologist Cert
SOC code
29-2055 — Surgical Technologists
NAICS code
622110 — Hospital
NAICS vintage
2012
Avg employees
358
Total hours worked
744948
EIN
730612674
Establishment ID
221196
Employer case #
884431

When (timing detail)

Date of incident
Shift started
5:52
Time of incident
11:45
Filing year
2025
Submitted
05FEB26:21:20:00

More injuries at 315 INTEGRIS Health Enid Hospital

View 315 INTEGRIS Health Enid Hospital's full OSHA safety record →

More injuries in this industry (NAICS 622110)

More injuries in OK

TULSA, OK—

WM 576

LAWTON, OK—

WM 269

Source

Data from OSHA ITA Form 300/301 electronic submissions, filing year 2025. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.