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

Saint Peters, MO —

OSHA Injury Report: Barnes-Jewish St. Peters Hospital

Injury · Other recordable case

At a glance

On , an injury at Barnes-Jewish St. Peters Hospital in 10 Hospital Drive, Saint Peters, MO 63376 resulted in other recordable case. Employee was tECHNOLOGIST SURGICAL in general medical and surgical hospitals.

Where did this happen?

Establishment
Barnes-Jewish St. Peters Hospital
Parent company
Barnes-Jewish St. Peters Hospital
Street
10 Hospital Drive
City
Saint Peters
State
MO
ZIP
63376
On-site location
outpatient surgery center bjsp 63376

What was the outcome?

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

Before the incident

assisting with surgery

What happened

assistant passing a blade back to the mayo stand poked EE in the left ring finger

Injury or illness

Laceration to left ring finger by dirty blade

Object or substance involved

knife blade

Summary line

assistant passing a blade back to the mayo stand poked EE in the left ring finger Laceration to left ring finger by dirty blade

Employee and industry

Job description
TECHNOLOGIST SURGICAL
SOC code
29-2055 — Surgical Technologists
NAICS code
622110 — General medical and surgical hospitals
NAICS vintage
2012
Avg employees
717
Total hours worked
1142779
EIN
431452426
Establishment ID
59117
Employer case #
94691

When (timing detail)

Date of incident
Shift started
6:00
Time of incident
9:00
Filing year
2025
Submitted
17JAN26:03:59:00

More injuries at Barnes-Jewish St. Peters Hospital

View Barnes-Jewish St. Peters Hospital's full OSHA safety record →

More injuries in this industry (NAICS 622110)

More injuries in MO

LEES SUMMIT, MO—

WM 573

SAINT JOSEPH, MO—

WM 2994

KIRKWOOD, MO—

WM 2694

DESLOGE, MO—

WM 95

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.