BRADENTON, FL —
OSHA Injury Report: 338 MANATEE MEMORIAL HOSPITAL, L.P.-LAKEWOOD RANCH
Injury · Other recordable case
At a glance
On , an injury at 338 MANATEE MEMORIAL HOSPITAL, L.P.-LAKEWOOD RANCH in BRADENTON, FL 34202 resulted in other recordable case. Employee was uNIT CLERK CERT in general Medical and Surgical Hospitals.
Where did this happen?
- Establishment
- 338 MANATEE MEMORIAL HOSPITAL, L.P.-LAKEWOOD RANCH
- Parent company
- Universal Health Services, Inc MANATEE MEMORIAL HOSPITAL, L.P.-LAKEWOOD RANCH
- Street
- 8330 LAKEWOOD RANCH BLVD.
- City
- BRADENTON
- State
- FL
- ZIP
- 34202
- On-site location
- 2 MAIN
What was the outcome?
- Outcome
- Other recordable case (code 4)
- Type
- Injury (code 1)
Before the incident
TAKING PATIENT OUTSIDE OF FACILITY
What happened
EE was in the doorway of the elevator backing up with a patient when the doors closed on EE 's shoulders and squeezed EE. EE reported neck and shoulder blades are hurting. EE was referred to provider. EE rated pain 4 10 at rest 10 10 with activity.
Injury or illness
Strained Upper back Caught in under or between ELEVATOR DOORS
Object or substance involved
ELEVATOR DOORS
Summary line
EE was in the doorway of the elevator backing up with a patient when the doors closed on EE 's shoulders and squeezed EE. EE reported neck and shoulder blades are hurting. EE was referred to provider. EE rated pain 4 10 at rest 10 10 with activity.
Employee and industry
- Job description
- UNIT CLERK CERT
- SOC code
- 43-9061 — Office Clerks, General
- NAICS code
- 622110 — General Medical and Surgical Hospitals
- NAICS vintage
- 2022
- Avg employees
- 683
- Total hours worked
- 1844710
- EIN
- 232798290
- Establishment ID
- 1128243
- Employer case #
- 81122
When (timing detail)
- Date of incident
- Shift started
- 7:00:00.000
- Time of incident
- 15:00:00.000
- Submitted
- 15FEB24:16:28:00
Source
Data from OSHA ITA Form 300/301 electronic submissions, filing year unspecified. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.