Overland Park, KS —
OSHA Injury Report: Overland Park Regional Medical Center
Injury · Other recordable case
At a glance
On , an injury at Overland Park Regional Medical Center in Overland Park, KS 66215 resulted in other recordable case. Employee was rN Neonatal Charge Tm Leader in hospital.
Where did this happen?
- Establishment
- Overland Park Regional Medical Center
- Parent company
- HCA
- Street
- 10500 Quivira
- City
- Overland Park
- State
- KS
- ZIP
- 66215
- On-site location
- Obstetrics incl. L D Postpartum
What was the outcome?
- Outcome
- Other recordable case (code 4)
- Type
- Injury (code 1)
Before the incident
assisting to move patient bed into OR
What happened
We were rapidly moving equipment to a c section room to prepare for a micropreemie emergency delivery. A nurse was helping me move the bed and my foot got pinned between the bed and the wall. She didnt realize thats what it was stuck on so pushed hard to get it unstuck. My foot was instantly sore and throbbing on the lateral side. House sup notified. After completion of my shift I went to er for work up.
Injury or illness
Bruise Contusion Foot - Left
Object or substance involved
patient bed wheel
Summary line
rapidly moving equipmentforemergency delivery. A nurse was helping me move the bed and my foot got pinned between the bed and the wall. Shedidntrealize so pushed hard to get it unstuck. My foot was instantly sore and throbbing on the lateral side.
Employee and industry
- Job description
- RN Neonatal Charge Tm Leader
- SOC code
- 29-1141 — Registered Nurses
- NAICS code
- 622110 — Hospital
- NAICS vintage
- 2022
- Avg employees
- 1600
- Total hours worked
- 2239650
- EIN
- 450503116
- Establishment ID
- 1373839
- Employer case #
- 83
When (timing detail)
- Date of incident
- Shift started
- 6:15
- Time of incident
- 17:45
- Filing year
- 2025
- Submitted
- 27FEB26:18:15: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.