A Workers Compensation claim lives or dies on coding. The same injury described three different ways — “hurt his back,” “lumbar strain lifting,” “L4-L5 sprain” — has to resolve to one body part, one nature, one cause, or the reserve, the OSHA log and the loss triangle all go wrong. Here is an actual First-Report-of-Injury packet — a lifting injury at Cedar Valley Manufacturing — run into one coded claim record with the medical roll-up computed exactly.

The packet

  • broker_claim_email.pdf — the producer’s notice: insured, policy, employee, what happened.
  • first_report_of_injury.pdf — the FROI: employee, employer, injury detail, treatment, return-to-work.
  • medical_bill.pdf — the treating provider’s statement of charges, line by line.

Step 1 — Classification

Document
Classified type · role
Conf.
broker_claim_email.pdf producer notice
broker_claim_email
0.98
first_report_of_injury.pdf FROI
first_report_injury
0.99
medical_bill.pdf provider statement
medical_bill
0.98

Step 2 — Extraction, with citations

First Report of Injuryrole: first_report_injury
claim_numberWC-2026-11902FROI p.1
employee_nameRobert Nguyen · Machine Operator IIFROI p.1
date_of_loss2026-06-18 · 14:30FROI p.1
wc_class_code3632FROI p.1
treating_physicianDr. Susan Park, Columbus OrthoFROI p.1
return_to_work_date2026-07-05FROI p.1

Step 3 — NCCI coding

The narrative — “sharp lower-back pain while manually lifting a 70-lb carton onto a conveyor” — is coded against the injury glossaries. This is the difference between a claim that reserves and reports correctly and one that doesn’t.

FieldAs writtenCoded (NCCI-aligned)
body_part“lower back”Back - Lumbar
nature_of_injury“sharp pain / pulled”Strain / Sprain
injury_cause“lifting a 70-lb carton”Overexertion / Lifting
line_of_business“workers comp”Workers Compensation - Indemnity

Body part × nature × cause is the reserving key for lost-time claims, the input to the OSHA 300 log, and the axis every WC loss triangle is built on. Coding it at intake — not weeks later in an audit — is where the value is.

Step 4 — The medical bill

Statement of charges — Columbus Orthopedic medical bill p.1

Service dateProcedureBilled
2026-06-18Initial evaluation & exam$1,850
2026-06-20MRI lumbar spine w/o contrast$2,400
2026-06-24Physical therapy (6 visits)$1,320
2026-07-01Office follow-up$260
Total billed$5,830

Step 5 — Deterministic roll-ups

1
Injuries reported
count(injuries)
12
Days lost
∑ injuries.days_lost
$5,830
Total medical billed
∑ medical_bills.billed_amount

The claim record

# unified claim record (excerpt)
{ "claim_number": "WC-2026-11902", "line_of_business": "Workers Compensation - Indemnity",
  "body_part": "Back - Lumbar", "nature_of_injury": "Strain / Sprain", "injury_cause": "Overexertion / Lifting",
  "osha_recordable": "Yes", "litigation_flag": "No", "return_to_work_date": "2026-07-05",
  "injury_count": 1, "total_days_lost": 12, "total_medical_billed": 5830 }

Why it holds up

  • Coded at intake — body part, nature and cause resolve to NCCI-aligned values the day the claim opens, so the reserve, the OSHA log and the loss triangle are right from the first touch.
  • OSHA & lost-time flags — recordability and lost-time vs medical-only are captured as fields, not inferred later, and a return-to-work date drives the indemnity exposure.
  • Exact medical roll-up — total billed is summed over the extracted line items by rule, so it always ties to the bill — no model arithmetic, no truncation on a long statement.
  • Cited & versioned — every value traces to a document and page, and the coding rules are pinned to a published version for reproducibility.