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

Fargo, ND —

OSHA Injury Report: ND,Fargo-South University Hospital-General Medical And Surgical Hospitals

Injury · Other recordable case

At a glance

On , an injury at ND,Fargo-South University Hospital-General Medical And Surgical Hospitals in 1720 University Dr S, Fargo, ND 58103 resulted in other recordable case. Employee was associate Sterile Processing Technician in general medical and surgical hospitals.

Where did this happen?

Establishment
ND,Fargo-South University Hospital-General Medical And Surgical Hospitals
Parent company
Sanford Health
Street
1720 University Dr S
City
Fargo
State
ND
ZIP
58103
On-site location
Home Department

What was the outcome?

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

Before the incident

I was opening a dirty enzyme container with dirty instruments in it

What happened

I grabbed a sharp instrument inside a biohazard baggie

Injury or illness

left thumb

Object or substance involved

The instrument

Summary line

Sharp [REDACTED] Exp-Sharp Instrument

Employee and industry

Job description
Associate Sterile Processing Technician
SOC code
31-9093 — Medical Equipment Preparers
NAICS code
622110 — General medical and surgical hospitals
NAICS vintage
2012
Avg employees
1076
Total hours worked
1672157
Establishment ID
1010955
Employer case #
25-4057

When (timing detail)

Date of incident
Shift started
9:00
Time of incident
14:40
Filing year
2025
Submitted
01MAR26:23:12:00

More injuries at ND,Fargo-South University Hospital-General Medical And Surgical Hospitals

View ND,Fargo-South University Hospital-General Medical And Surgical Hospitals's full OSHA safety record →

More injuries in this industry (NAICS 622110)

More injuries in ND

DICKINSON, ND—

WM 1567

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.