From a claim file to a structured summary
A modelled scenario: a workers' compensation claim file becomes structured fields, a claim-level summary and a medical chronology, with a person approving each stage.
The manual process
- Claim files arrive as many separate PDFs and scans: forms, medical records, bills and correspondence.
- An adjuster opens each document, copies key facts into the claims system and writes a narrative by hand.
- Dates and amounts are cross-checked from memory or in a spreadsheet, so the story of the claim is rebuilt every time someone picks the file up.
The pipeline
-
Ingest and classify
Files are uploaded in the portal or sent via API and webhooks. Each document is read and classified by type.
-
Extract fields
Fields from the matching schema are extracted, each with a confidence score.
-
Human review
Where human-in-the-loop review is switched on, a reviewer checks the text and fields and approves each stage before the pipeline advances.
-
Link documents
Documents belonging to the same claim are linked so they can be read together.
-
Summarise and build a chronology
A claim-level summary, including a dated medical chronology, is drafted from the claim's documents and reviewed before use. This claim summary is built for workers' compensation claims today.
The result
- Structured fields sit alongside the source pages they came from.
- One claim-level summary and one chronology replace a pile of separate files.
- Every AI-generated statement has a reviewer step before anyone relies on it.
What the reviewer sees
The reviewer works from a queue of documents that need attention, with extracted values shown next to the original page. Low-confidence values stand out, and corrections are recorded. Once a stage is approved, the claim moves on to the next one.
What this scenario does not claim
This is a modelled workflow, not a customer case study. It does not describe a real company, and it states no volumes, time savings or accuracy figures. AI output can be wrong, which is why review is part of the flow. Summaries and chronologies are drafts for a qualified person to confirm, not decisions.