2,042,423Injury reports 130,778Establishments Most recent incident 2025-12-31
Safety Incidents OSHA Severe Injury Reports · 2015–2025

Baltimore, MD —

OSHA Injury Report: University of Maryland Rehabilitation Orthopaedic Institute

Injury · Days away from work

At a glance

On , an injury at University of Maryland Rehabilitation Orthopaedic Institute in 2200 Kernan Drive, Baltimore, MD 21207 resulted in days away from work. Employee was kH Clinical Nurse II in hospital.

Where did this happen?

Establishment
University of Maryland Rehabilitation Orthopaedic Institute
Parent company
James Lawrence Kernan Hospital Inc.
Street
2200 Kernan Drive
City
Baltimore
State
MD
ZIP
21207
On-site location
Hallway

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
9

Before the incident

pt started running towards worker

What happened

[REDACTED] started running towards worker tried to get away from same and both fell to the ground.

Injury or illness

Contusion

Object or substance involved

combative patient

Summary line

[REDACTED] started running towards worker tried to get away from same and both fell to the ground.

Employee and industry

Job description
KH Clinical Nurse II
SOC code
29-1141 — Registered Nurses
NAICS code
622310 — Hospital
NAICS vintage
2012
Avg employees
666
Total hours worked
1173595
EIN
520591639
Establishment ID
860243
Employer case #
WC2025037

When (timing detail)

Date of incident
Shift started
7:00
Time of incident
19:00
Filing year
2025
Submitted
28FEB26:00:17:00

More injuries at University of Maryland Rehabilitation Orthopaedic Institute

View University of Maryland Rehabilitation Orthopaedic Institute's full OSHA safety record →

More injuries in this industry (NAICS 622310)

More injuries in MD

COLUMBIA, MD—

WM 5228

RANDALLSTOWN, MD—

WM 3804

CATONSVILLE, MD—

WM 2248

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.