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

Danbury, NC —

OSHA Injury Report: LifeBrite Community Hospital of Stokes

Injury · Other recordable case

At a glance

On , an injury at LifeBrite Community Hospital of Stokes in 1570 NC 8 & 89 HWY N, Danbury, NC 27016 resulted in other recordable case. Employee was cNA in general medical and surgical hospitals.

Watch LifeBrite Community Hospital of Stokes — free Get an email when a new federal OSHA severe-injury report for LifeBrite Community Hospital of Stokes is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
LifeBrite Community Hospital of Stokes
Parent company
LifeBrite Hospital Group of Stokes
Street
1570 NC 8 & 89 HWY N
City
Danbury
State
NC
ZIP
27016
On-site location
Nursing Home

What was the outcome?

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

Before the incident

Walking down Nursing Home hallway

What happened

Employee scraped fingers on the edge of the dirty linen cart

Injury or illness

Cuts to middle and ring fingers

Object or substance involved

Edge of linen cart

Summary line

Cut fingers on edge of linen cart

Employee and industry

Job description
CNA
SOC code
31-1131 — Nursing Assistants
NAICS code
622110 — General medical and surgical hospitals
NAICS vintage
2012
Avg employees
137
Total hours worked
186228
EIN
814216501
Establishment ID
497465
Employer case #
3

When (timing detail)

Date of incident
Shift started
6:54
Time of incident
14:20
Filing year
2024
Submitted
31JAN2025:18:56:00

More injuries at LifeBrite Community Hospital of Stokes

View LifeBrite Community Hospital of Stokes's full OSHA safety record →

More injuries in this industry (NAICS 622110)

More injuries in NC

FAYETTEVILLE, NC—

WM 8218

GREENSBORO, NC—

WM 6402

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.