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

Whitefish, MT —

OSHA Injury Report: Logan Health Whitefish

Other illness · Job transfer or restriction

At a glance

On , an other illness at Logan Health Whitefish in 1600 Hospital Way, Whitefish, MT 59937 resulted in job transfer or restriction. Employee was sterile processing tech in general medical and surgical hospitals.

Watch Logan Health Whitefish — free Get an email when a new federal OSHA severe-injury report for Logan Health Whitefish is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
Logan Health Whitefish
Parent company
Logan Health Whitefish
Street
1600 Hospital Way
City
Whitefish
State
MT
ZIP
59937
On-site location
sterile processing room

What was the outcome?

Outcome
Job transfer or restriction (code 3)
Type
Other illness (code 6)
Days restricted or transferred
5

Before the incident

working in sterile processing room

What happened

complaint of headaches and nausea after working in room employee has history of crohns disease

Injury or illness

exposure to cleaning chemicals in decontamination rooms

Object or substance involved

isopropyl alcohol spray

Summary line

systemic exposure to chemicals

Employee and industry

Job description
sterile processing tech
SOC code
31-9093 — Medical Equipment Preparers
NAICS code
622110 — General medical and surgical hospitals
NAICS vintage
2022
Avg employees
467
Total hours worked
633981
Establishment ID
1082662
Employer case #
24

When (timing detail)

Date of incident
Time of incident
11:30
Filing year
2025
Submitted
22JAN26:17:36:00

More injuries at Logan Health Whitefish

View Logan Health Whitefish's full OSHA safety record →

More injuries in this industry (NAICS 622110)

More injuries in MT

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.