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

SACRAMENTO, CA —

OSHA Injury Report: 64030164-016401 MERCY GENERAL HOSPITAL

Injury · Other recordable case

At a glance

On , an injury at 64030164-016401 MERCY GENERAL HOSPITAL in 4001 J STREET, SACRAMENTO, CA 958193626 resulted in other recordable case. Employee was phys Asst CVOR in general Medical and Surgical Hospitals.

Watch 64030164-016401 Mercy General Hospital — free Get an email when a new federal OSHA severe-injury report for 64030164-016401 Mercy General Hospital is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
64030164-016401 MERCY GENERAL HOSPITAL
Parent company
CommonSpirit Health MERCY GENERAL HOSPITAL
Street
4001 J STREET
City
SACRAMENTO
State
CA
ZIP
958193626
On-site location
CVOR

What was the outcome?

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

Before the incident

SUTURING

What happened

Needle stick to left 2nd fingertip

Injury or illness

Puncture Left Finger s Needle stick needle

Object or substance involved

needle

Summary line

Needle stick to left 2nd fingertip

Employee and industry

Job description
Phys Asst CVOR
SOC code
29-2034 — Radiologic Technologists and Technicians
NAICS code
622110 — General Medical and Surgical Hospitals
NAICS vintage
2012
Avg employees
2036
Total hours worked
3192653
EIN
470617373
Establishment ID
1015953
Employer case #
5001102

When (timing detail)

Date of incident
Shift started
6:30
Time of incident
19:00
Filing year
2025
Submitted
27FEB26:22:17:00

More injuries at 64030164-016401 MERCY GENERAL HOSPITAL

View 64030164-016401 MERCY GENERAL HOSPITAL's full OSHA safety record →

More injuries in this industry (NAICS 622110)

More injuries in CA

Rancho Cucamonga, CA—

087-RCDC

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.