Extract data from employee injury reports
Unstract reads first reports of injury, OSHA logs and incident reports, typed or filled in by hand on the shop floor, and sends checked workers' compensation claim data to your claims system.
TO: LAKESHORE MUTUAL · WC CLAIMS · FAX 612-555-0190
stitches x6 — back on light duty Mon
EMPLOYER'S FIRST REPORT · KEEP A COPY FOR YOUR OSHA 300 LOG
{ "report_type": "first report of injury", "employer": "Northgate Fabrication Inc", "employee": "Halvorsen, Marcus J", "ssn": "***-**-4418", "date_of_injury": "10/27/2026", "body_part": "left hand", "nature_of_injury": "laceration", "days_away": 4, "osha_recordable": true, "confidence": 0.95}
Trusted by insurance teams around the globe
Injury reports are filled in on the floor, not at a desk
A supervisor writes up the incident at the end of a shift, and the report reaches the insurer days later. This is what lands in the claims inbox.
Faxed from the plant office, with the fine print gone grey
Each state and each employer prints its own first report
The account of the accident, written by hand and corrected in pen
First report, witness statement, clinic note and wages in one PDF
A year of OSHA 300 log lines, and incident forms in every layout
An adjuster keys every report before the claim exists, and each day spent keying is a day the injured worker waits for a first check.
Unstract reads the report, pulls the employee, injury and wage fields, checks them against the policy and the employer's earlier claims, and opens the claim for the adjuster.
Read, structure and route workplace injury claims on one platform
Three products that work alone or together: read the report, turn it into fields, run the claim intake around it. Begin with the layer your team is short of.
Employee injury report OCR that keeps the handwriting beside its box
Get the full text of a first report of injury, an OSHA 301 or an employer's own incident form, with each box where the employer filled it in. The supervisor's handwritten account stays under "how it happened", and the recordable checkbox comes through marked or blank, so nobody has to guess which answer was ticked.
Hand the text to your own LLM, or make parsing the first stage of a workers' comp intake.
Learn more about LLMWhispererTurn employee injury reports into one checked claim record
Name the employer, employee, injury and wage fields you want, and every report returns the same JSON, from a state first report to an OSHA 300 log line or an independent medical examination request. Each value is checked on the way out: an injury date outside the policy period, or days away that don't match the return-to-work note, comes back flagged with the reason.
Call it as an API from your claims intake, run it as an ETL pipeline from a fax folder, or place it inside an orchestrated claims process.
Learn more about Document StudioRun injury report intake from the fax line to an open claim
Describe your employee injury report intake in plain English, and Flow's agents build the workflow: reports collected from the fax line, the employer portal and the claims inbox, each page of the file named, every report read and checked against the policy, the employer's claim history and the OSHA recordable answer, then routed. Medical-only claims move fast; lost-time claims go to an adjuster. You approve the workflow once, and it handles every report the same way.
Choose where a person takes over: coverage in doubt, a fraud flag, a reserve above an adjuster's authority, a handwritten line the read isn't sure of. Only those reports pause, and the adjuster sees the reason.
Learn more about FlowExtract the reports first. Add the intake when you're ready.
Start for free covers parsing and extracting your injury reports today. Automating workers' comp intake starts with a consultation.
First reports, OSHA records and the paperwork behind a comp claim
Documents
- Employer's first reports of injury (FROI)
- Employee's reports of injury
- OSHA 300 logs of work-related injuries and illnesses
- OSHA 301 injury and illness incident reports
- OSHA 300A annual summaries
- Workplace incident reports
- Employee incident reports
- Witness statements
- Requests for independent medical examination
- Physician's first reports and work status notes
- Wage statements
- An employer's own incident form, in its own layout
Fields captured
For everyone who handles a workplace injury on paper
First reports opened as claims the day they arrive, so the first indemnity check isn't late because the report sat in a keying queue.
Reports from hundreds of client employers read into one record, each in whatever layout that employer prints.
OSHA 300 logs and 301 forms kept in step with the claims, so the year-end 300A summary isn't rebuilt from paper.
Every site's incident reports in one place, with lost-time cases and IME requests tracked against the reserves you carry yourself.
Claims open sooner, and adjusters stop keying
Handled as health and wage data, because it is
An injury report pairs a worker's Social Security number with a diagnosis, the treating doctor and what they earn each week. A leak exposes one person's identity, health and income at once, so it gets the protection HIPAA asks for medical records.
- Encrypted end to end, in transit and at rest.
- Injury reports you send are never used to train models.
- Access by role, employer account and claim type, and every change is logged against the claim it touched.
- Retention is yours to set: reports and images are deleted when your schedule says so.
- Self-hosted deployment for carriers, TPAs and self-insured employers that keep claim files on their own servers.
What comp carriers, TPAs and employers ask first
It turns a scanned or faxed injury report into text a claims system can use. LLMWhisperer reads the employer's first report, the OSHA 301 and the employer's own forms with their boxes in place, including the handwritten account of the accident and the checkboxes.
Upload the report or call the API. Document Studio returns the employer, employee, injury and wage fields you defined as JSON, and the same schema works on a state form, a carrier form and an employer's in-house version.
Yes. Supervisors often write the account by hand, sometimes across the margin. LLMWhisperer reads handwriting next to printed text, and a line it can't read with certainty goes to an adjuster with the image, not into the claim as a guess.
Yes. An OSHA 300 log comes back one case per row, with the case number, job title, injury type and days away kept on the right line. That makes OSHA 300 log data extraction a way to compare an employer's recorded cases with the claims you actually received.
The 301 is the incident report behind each line on the 300 log. Its fields, what the employee was doing, what happened, the injury and the object that caused it, are extracted into the same record as the first report, so one injury doesn't become two files.
Faxes and phone photos are the normal case. LLMWhisperer corrects rotation, skew and noise before reading, and Document Studio checks each value against the rest of the report, so a body part that conflicts with the nature of injury is flagged.
It can pull the facts the request is built on: the claimant, the injury, the specialty asked for, the questions for the examiner and the exam date. Document Studio extracts those fields from the request, and the examiner's own medical opinion stays with the physician.
No. Document Studio needs no templates, so first report of injury OCR works on a form from a state it hasn't seen before. You describe the fields once, and each state's layout comes back in the same schema.
Through your claims system's API or a file drop, in the format it already takes. Flow opens the claim, attaches the original report and records every reviewer's decision against it.
It stops in a review queue. The adjuster sees the missing or doubtful field, the box it came from and why it stopped, fixes it, and the claim moves on with that decision on record.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Reports are encrypted in transit and at rest, never used for training, and kept only as long as you choose. Teams that must keep claim files in-house can self-host.
In a consultation we fit the intake to your report types, checks and claims system, and most teams see a first live run within days. To try the extraction now, start for free and upload a first report.
Bring a month of injury reports to the consultation
First reports, OSHA 301s, incident forms and IME requests, faxed and handwritten ones included. We run them live and show each field, each check and every report that stops for an adjuster.