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

Gadsden, AL —

OSHA Injury Report: Riverview Regional Medical Center

Injury · Other recordable case

At a glance

On , an injury at Riverview Regional Medical Center in 600 S 3rd Street, Gadsden, AL 35901 resulted in other recordable case. Employee was eVS Tech in general medical and surgical hospitals.

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

Where did this happen?

Establishment
Riverview Regional Medical Center
Parent company
Riverview Regional Medical Center
Street
600 S 3rd Street
City
Gadsden
State
AL
ZIP
35901
On-site location
5T clean utility room

What was the outcome?

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

Before the incident

cleaning the clean utility room

What happened

IW saw needle and cap laying on the floor. IW tried to recap the needle and the needle stuck the IW right thumb

Injury or illness

needle stick

Object or substance involved

needle

Summary line

[REDACTED] stick to right thumb

Employee and industry

Job description
EVS Tech
SOC code
37-2019 — Building Cleaning Workers, All Other
NAICS code
622110 — General medical and surgical hospitals
NAICS vintage
2012
Avg employees
790
Total hours worked
1643200
EIN
472228529
Establishment ID
408820
Employer case #
15

When (timing detail)

Date of incident
Shift started
7:00
Time of incident
10:00
Filing year
2024
Submitted
17MAR2025:16:38:00

More injuries at Riverview Regional Medical Center

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

More injuries in this industry (NAICS 622110)

More injuries in AL

GREENVILLE, AL—

WM 1462

Source

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