Safety Incidents OSHA Severe Injury Reports · 2015–2025
2,098,129Injury reports 132,232Establishments Most recent incident 2025-12-31

Sidney, NE —

OSHA Injury Report: Sidney Regional Medical Center

Injury · Other recordable case

At a glance

On , an injury at Sidney Regional Medical Center in 1000 Pole Creek Crossing, Sidney, NE 69162 resulted in other recordable case. Employee was surgical tech in hospitals, general medical and surgical.

Watch Sidney Regional Medical Center — free Get an email when a new federal OSHA severe-injury report for Sidney Regional Medical Center is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
Sidney Regional Medical Center
Parent company
Sidney Regional Medical Center
Street
1000 Pole Creek Crossing
City
Sidney
State
NE
ZIP
69162
On-site location
OR 3

What was the outcome?

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

Before the incident

working as tech on c-section

What happened

provider poked EE with suture while she was retracting incision

Injury or illness

Sharps injury exposure

Object or substance involved

Ct-1 vicryl suture

Summary line

provider poked EE with suture in right 1st digit

Employee and industry

Job description
Surgical tech
SOC code
29-2055 — Surgical Technologists
NAICS code
622110 — Hospitals, general medical and surgical
NAICS vintage
2012
Avg employees
353
Total hours worked
870518
EIN
470408242
Establishment ID
48683
Employer case #
22

When (timing detail)

Date of incident
Shift started
8:00
Time of incident
12:45
Filing year
2025
Submitted
27JAN26:22:06:00

More injuries at Sidney Regional Medical Center

View Sidney Regional Medical Center's full OSHA safety record →

More injuries in this industry (NAICS 622110)

More injuries in NE

BELLEVUE, NE—

WM 3154

FREMONT, NE—

WM 776

Scottsbluff, NE—

RWMC

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.