Extract data from OSHA 300 injury logs
An OSHA 300 log is the running record every covered US employer keeps of work-related injuries and illnesses across a calendar year. Each recordable case gets a row: who was hurt, what happened, which body part, how many days they were away from work or on restricted duty, and how the case is classified. Its year-end totals feed the OSHA 300A summary posted in the workplace and, for larger establishments, submitted electronically, with aggregate figures flowing to the US Bureau of Labor Statistics annual injury survey. Safety managers, workers-compensation coordinators, and EHS auditors all read the log. Kellerman Fabrication Plant 3, at 1400 Industrial Parkway in Toledo, Ohio, under EIN 34-2891746, logged its 2026 cases from 2026-01-01 through 2026-12-31. Case 2026-014 records that Marcus Ellison, a machine operator in the Press department, sustained a laceration to the left hand on 2026-04-09, reported the same day, was treated beyond first aid, spent 6 days away from work and 4 on restricted duty, and returned on 2026-04-19. The case is flagged work-related and recordable, with no fatality and a permanence of temporary total. Case 2026-015 logs a repetitive-strain wrist disorder for Priya Nathan, an assembler, with 0 days away but 12 on restricted duty. Talonic reads the log and returns the establishment identity, the reporting year, and the log period as fields, and the injury and illness entries as a table keyed by case_number, each carrying the incident date, body part, type of injury, days away from work, and the recordable and work-related flags. Days away and restricted days are typed as numbers so the annual totals foot rather than being re-added by hand. It captures the cases as recorded and makes no determination about recordability or workers-compensation entitlement; those calls stay with the employer and its counsel.
What gets extracted from OSHA 300 injury logs
How extraction works for OSHA 300 injury logs
OSHA 300 logs are kept in spreadsheets, in EHS platforms such as VelocityEHS, or on the printed form, and the same columns appear in different orders across establishments. Talonic classifies the log and aligns it to the injury-record schema in the Field Registry, so the establishment_name, the employer EIN, the year, and each case row resolve to stable fields. The injury_illness_entries table loads per case, days_away_from_work and restricted-duty days are typed as numbers, the type_of_injury and permanence_of_injury enums are preserved, and dates such as the 2026-04-09 incident and the 2026-04-19 return parse to ISO 8601. Every value carries a confidence score and a source-region pointer under DIN SPEC 91491, so a safety manager can trace an extracted day count back to the exact row. Talonic reports the log as written and makes no recordability or entitlement judgment.
Sample extraction
An annual OSHA 300 injury and illness log for one establishment
{
"document_number": "OSHA300-KEL3-2026",
"establishment_name": "Kellerman Fabrication Plant 3",
"establishment_address": "1400 Industrial Parkway, Toledo, OH 43604",
"employer_id": "34-2891746",
"year": 2026,
"effective_date": "2026-01-01",
"expiration_date": "2026-12-31",
"injury_illness_entries": [
{
"case_number": "2026-014",
"employee_name": "Marcus Ellison",
"incident_date": "2026-04-09",
"date_reported": "2026-04-09",
"injury_description": "Laceration to the left hand while clearing a press die",
"body_part_affected": "Left hand",
"type_of_injury": "laceration",
"work_related": true,
"days_away_from_work": 6,
"job_title": "Machine Operator",
"department": "Press",
"osha_recordable": true,
"treatment_provided": "Sutures, beyond first aid",
"date_of_return_to_work": "2026-04-19",
"restricted_work": true,
"death_occurred": false,
"permanence_of_injury": "temporary total",
"witness_name": "Dana Reyes"
},
{
"case_number": "2026-015",
"employee_name": "Priya Nathan",
"incident_date": "2026-05-02",
"date_reported": "2026-05-05",
"injury_description": "Repetitive-strain wrist disorder",
"body_part_affected": "Right wrist",
"type_of_injury": "occupational disease",
"work_related": true,
"days_away_from_work": 0,
"job_title": "Assembler",
"department": "Assembly",
"osha_recordable": true,
"treatment_provided": "Ergonomic restriction and physical therapy",
"date_of_return_to_work": null,
"restricted_work": true,
"death_occurred": false,
"permanence_of_injury": "other occupational disease",
"witness_name": null
}
]
}Frequently asked
What is the difference between the OSHA 300 log and the 300A summary?
The 300 log is the case-by-case record, one row per recordable injury or illness. The 300A is the annual summary that totals those cases for posting. Talonic reads the 300 log rows; the 300A totals follow from footing them.
Does it total the days away from work?
Days away and restricted-duty days are typed as numbers per case, so the 6 days on case 2026-014 and 12 restricted days on case 2026-015 foot into the annual totals rather than being re-counted by hand.
Does Talonic decide whether a case is recordable?
No. It captures the osha_recordable flag as the log states it. Whether a given injury meets the recording criteria is a determination for the employer, not the extraction.
Are employee names extracted from the log?
Yes, as recorded, since the 300 log names each injured employee. Personally identifiable data is handled under your workspace access controls, and privacy-restricted versions of the log can be processed the same way.
Ready to extract from your own OSHA 300 injury logs?
Author note
Reviewed by Talonic engineering, EHS schema review · last reviewed 2026-07-08