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

Emmetsburg, IA —

OSHA Injury Report: Palo Alto County Health System

Injury · Other recordable case

At a glance

On , an injury at Palo Alto County Health System in 3201 1st Street, Emmetsburg, IA 50536 resulted in other recordable case. Employee was cook in health Care.

Where did this happen?

Establishment
Palo Alto County Health System
Parent company
Palo Alto County Health System
Street
3201 1st Street
City
Emmetsburg
State
IA
ZIP
50536
On-site location
Kitchen

What was the outcome?

Outcome
Other recordable case (code 4)
Type
Injury (code 1)

Before the incident

Employee was preparing breakfast and had used the last of the aluminum foil.

What happened

Employee was moving a new box of aluminum foil to the back counter. The new role slid out of the employee 's hand causing a laceration to the right fifth finger.

Injury or illness

1.5 cm Finger Laceration repaired in the ER with 2 sutures.

Object or substance involved

The sharp edge on the aluminum foil box

Summary line

Laceration of the right 5th finger. The sharp edge of the aluminum foil box caused the laceration.

Employee and industry

Job description
Cook
SOC code
35-2012 — Cooks, Institution and Cafeteria
NAICS code
622110 — Health Care
NAICS vintage
2012
Avg employees
270
Total hours worked
493833
EIN
420455510
Establishment ID
561751
Employer case #
R2025000

When (timing detail)

Date of incident
Shift started
5:30
Time of incident
7:00
Filing year
2025
Submitted
15JAN26:21:05:00

More injuries at Palo Alto County Health System

View Palo Alto County Health System's full OSHA safety record →

More injuries in this industry (NAICS 622110)

More injuries in IA

WEST BURLINGTON, IA—

WM 797

DES MOINES, IA—

WM 1723

DES MOINES, IA—

WM 1723

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.