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

GREENSBORO, NC —

OSHA Injury Report: 1155 CONE HEALTH CANCER CENTER

Injury · Other recordable case

At a glance

On , an injury at 1155 CONE HEALTH CANCER CENTER in 2400 W FRIENDLY AVE, GREENSBORO, NC 27403 resulted in other recordable case. Employee was clinical Resear.

Where did this happen?

Establishment
1155 CONE HEALTH CANCER CENTER
Parent company
Cone Health CONE HEALTH CANCER CENTER
Street
2400 W FRIENDLY AVE
City
GREENSBORO
State
NC
ZIP
27403
On-site location
POD 3 ACROSS FROM AUDIT ROOM G 099

What was the outcome?

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

Before the incident

SEATED AT COMPUTER WORKING ON HLC TRAINING

What happened

I was bit on my right forearm by a dark red flat back bug sitting at my desk working on the computer around end of shift Once I noticed the bug on my arm and that it was biting and sucking my blood I then knocked the bug off my arm and onto my de

Injury or illness

Inflamed Right Forearm Struck by animal or insect Bug

Object or substance involved

Bug

Summary line

I was bit on my right forearm by a dark red flat back bug sitting at my desk working on the computer

Employee and industry

Job description
Clinical Resear
SOC code
29-1141 — Registered Nurses
NAICS code
622110
NAICS vintage
2022
Avg employees
307
Total hours worked
509387
EIN
560532302
Establishment ID
1472993
Employer case #
628

When (timing detail)

Date of incident
Shift started
8:00
Time of incident
16:00
Filing year
2025
Submitted
16FEB26:16:44:00

More injuries at 1155 CONE HEALTH CANCER CENTER

View 1155 CONE HEALTH CANCER CENTER's full OSHA safety record →

More injuries in this industry (NAICS 622110)

More injuries in NC

FAYETTEVILLE, NC—

WM 8218

GREENSBORO, NC—

WM 6402

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.