Washington, DC —
OSHA Injury Report: Sibley Memorial Hospital
Injury · Days away from work
At a glance
On , an injury at Sibley Memorial Hospital in Washington, DC 20016 resulted in days away from work. Employee was regular in general medical and surgical hospitals.
Where did this happen?
- Establishment
- Sibley Memorial Hospital
- Parent company
- Johns Hopkins Medicine
- Street
- 5255 Loughboro Road NW
- City
- Washington
- State
- DC
- ZIP
- 20016
- On-site location
- Sibley Memorial Hospital
What was the outcome?
- Outcome
- Days away from work (code 2)
- Type
- Injury (code 1)
- Days away from work
- 20
Before the incident
Employee was doing bed side care on a overweight patient. While rolling the patient over the patient grab employee 's shoulders pulling her and employee felt sharp pain in her lower back
What happened
Employee was doing bed side care on a overweight patient. While rolling the patient over the patient grab employee 's shoulders pulling her and employee felt sharp pain in her lower back
Injury or illness
Employee was doing bed side care on a overweight patient. While rolling the patient over the patient grab employee 's shoulders pulling her and employee felt sharp pain in her lower back
Object or substance involved
Employee was doing bed side care on a overweight patient. While rolling the patient over the patient grab employee 's shoulders pulling her and employee felt sharp pain in her lower back
Summary line
Strain or Tear Back Spine (nonspecific)
Employee and industry
- Job description
- Regular
- SOC code
- 29-1141 — Registered Nurses
- NAICS code
- 622110 — General medical and surgical hospitals
- NAICS vintage
- 2012
- Avg employees
- 3531
- Total hours worked
- 3692696
- Establishment ID
- 323248
- Employer case #
- W20250402
When (timing detail)
- Date of incident
- Filing year
- 2025
- Submitted
- 18FEB26:16:57:00
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.