One template per jurisdiction. Filled in automatically.
Custom medical report templates for every jurisdiction and line of business: build or upload the structure once, and the engine auto-fills it from the record. Each filled field carries a page-level citation, gaps are flagged rather than guessed, and finished reports deliver via DOCX or PDF export, API, or SFTP.
One template per jurisdiction, line, and letterhead.
Build or upload templates that match each jurisdiction’s required structure — section order, headings, attestation blocks — and each line of business’s language. Save it once, and every report on that line comes out the same shape.
Every field filled from the record, with the page attached.
Each template field maps to an extraction: claimant details, diagnoses, treatment dates, work status. The engine reads the file and fills the template — all 38 fields in the sample — and each filled field carries the citation it came from.
Edit in-platform. Deliver anywhere.
The draft opens in a rich-text studio with tracked changes and comments. Export DOCX or PDF on your letterhead, or deliver straight into your claims or case system over API or scheduled SFTP. IME Report Drafting and the litigation chart library run on this same engine.
Auto-filled never means unsourced.
Every filled field cites the page it came from, so a reviewer can verify the report line by line before it goes out — audit-grade and legally defensible. Fields the record can’t support arrive flagged for a human. The AI drafts the report; your expert reviews, edits, and signs.
See Medical Summary ReportsFrom template to delivered report.
Three steps, and the report lands in the format — and the system — your workflow already uses.
Jurisdiction and line of business set the structure; your letterhead and styles apply automatically.
Extractions map to template fields with citations attached. Anything unsupported is flagged, not guessed.
Edit in-platform with tracked changes, then export DOCX or PDF — or push via API or SFTP.
Who builds reports with it.
Anyone whose output has to match a required format, jurisdiction after jurisdiction.
Examiner templates per referral source and state, filled from the record before the exam packet lands.
For IME orgsOne template per client and line of business — consistent reports from every reviewer.
For TPAsJurisdiction-correct output at claims volume, delivered straight into your core system.
For carriersCustom report templates, answered.
Yes — that is the point. Each template is saved with its own section order, headings, required attestation blocks, and language, so a NY workers’ comp narrative and an auto-liability peer review come out in their own required shapes. You select the template at case setup.
Each template field maps to an extraction from the file — claimant details, diagnoses, treatment dates, work status, and more. In the sample template, all 38 fields fill from the record, and every filled field carries a page-level citation. Fields the record cannot support arrive flagged for review instead of guessed.
Yes. Reports export as DOCX or PDF with your letterhead, fonts, and formatting applied. You can edit in-platform first — the studio supports tracked changes and comments — or edit the DOCX downstream in Word.
Finished reports can be pushed to your claims or case-management system over API, or dropped to a scheduled SFTP location per office or client. Delivery is configured once and applies to every report on that template.
Yes. IME Report Drafting, the litigation chart library, and narrative summaries all run on this same template engine — the same field mapping, citation discipline, and delivery options, packaged per deliverable.
Related capabilities.
Same engine, same citation standard — deliverables that run on this template engine.
From record to attested, deposition-ready report — your template, your letterhead.
ExploreNine named litigation chart types, run as one template library on this engine.
ExploreThe examiner’s report drafted from exam findings and the case record, on this engine.
ExploreProse-form case narrative — SOAP or plain-language — drafted from the same extracted data.
ExploreSend us a template. Get it back filled in.
Upload a file — and your own template, if you like — and get back a cited, auto-filled draft. Handled under our BAA; never used to train a model.