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

St. Johnsbury, VT —

OSHA Injury Report: Northeastern Vermont Regional Hospital

Injury · Days away from work

At a glance

On , an injury at Northeastern Vermont Regional Hospital in 1315 Hospital Drive, St. Johnsbury, VT 5819 resulted in days away from work. Employee was cook in hospitals, general pediatric.

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

Where did this happen?

Establishment
Northeastern Vermont Regional Hospital
Parent company
Northeastern Vermont Regional Hospital
Street
1315 Hospital Drive
City
St. Johnsbury
State
VT
ZIP
5819
On-site location
Food service

What was the outcome?

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

Before the incident

Cutting cooked chicken

What happened

cutting cooked chicken knife slipped and cut left thumb

Injury or illness

Cut to left thumb from a Dexter knife

Object or substance involved

Dexter knife

Summary line

cutting cooked chicken knife slipped and cut left thumb

Employee and industry

Job description
Cook
SOC code
35-2012 — Cooks, Institution and Cafeteria
NAICS code
622110 — Hospitals, general pediatric
NAICS vintage
2022
Avg employees
657
Total hours worked
1025363
EIN
36013761
Establishment ID
1420500
Employer case #
4

When (timing detail)

Date of incident
Shift started
4:15
Time of incident
8:30
Filing year
2024
Submitted
15OCT2025:19:24:00

More injuries at Northeastern Vermont Regional Hospital

View Northeastern Vermont Regional Hospital's full OSHA safety record →

More injuries in this industry (NAICS 622110)

More injuries in VT

Source

Data from OSHA ITA Form 300/301 electronic submissions, filing year 2024. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.