# Custom Medical Report Templates & Builder > Custom medical report templates by jurisdiction and line of business — auto-filled from the record with citations, exported to DOCX or PDF, or via API. Canonical page: https://medrecords.ai/product/custom-report-builder/ --- NewWe now read the actual MRI and CT imaging — not just the radiologist's 1-page report. [See how →](https://medrecords.ai/product/imaging/) [Home](https://medrecords.ai/) ›[Product](https://medrecords.ai/product/) › — Custom Report Builder CUSTOM MEDICAL REPORT TEMPLATES ## 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. [Test a file ](https://medrecords.ai/test-a-file/?src=product-custom-report-builder) [Book a demo](https://medrecords.ai/demo/) Adams, T. · Case #IME-4812 38 template fields NY Workers' Comp — IME Narrative DOCX — LETTERHEAD Field — Filled from record — Source Claimant Adams, Timothy p.14 Body part Right knee p.38 Course to date 7 visits, improving since 4/02 p.140 Prior imaging Not found in record REVIEW **38 template fields** auto-filled from the record One flagged for review 38 fields Auto-filled in the sample template DOCX · PDF Export on your letterhead API · SFTP Delivery into your systems ### 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. Jurisdiction- and line-specific structures, saved once Your letterhead, styles, and section order preserved Template library NY WC — IME narrative — DOCX NJ PIP — medical review — DOCX Auto liability — peer review — PDF Group health — APS summary — DOCX Each template keeps its **own structure, headings, and attestation blocks** . Field mapping · Case #IME-4812 Diagnoses — extracted — p.38 Treatment dates — 7 visits — p.140 Work status — extracted — p.14 Prior imaging — NOT FOUND — REVIEW Every filled field **carries its citation** ; gaps arrive flagged. ### 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. Filled fields carry page-level citations Fields the record can't support are flagged, not guessed ### 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. Tracked changes and in-platform review before sign-off Scheduled SFTP drops or API push, per office or client Delivery adams_ime_narrative.docx — DOCX — LETTERHEAD adams_ime_narrative.pdf — PDF SFTP · claims intake drop — SCHEDULED API · case-system push — CONNECTED Reviewer view · before sign-off Course to date — 7 visits, improving p.140 Body part — right knee p.38 Prior imaging — not found, needs a human REVIEW AI drafts · your expert reviews and signs The standard ### 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 Reports ](https://medrecords.ai/product/summaries/) ### From template to delivered report. 3 steps, and the report lands in the format — and the system — your workflow already uses. 01 Pick the template Jurisdiction and line of business set the structure; your letterhead and styles apply automatically. 02 The record fills the fields Extractions map to template fields with citations attached. Anything unsupported is flagged, not guessed. 03 Review, edit, deliver 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. [ IME organizations Examiner templates per referral source and state, filled from the record before the exam packet lands. For IME orgs ](https://medrecords.ai/solutions/medical-evaluators/) [ TPAs & case management One template per client and line of business — consistent reports from every reviewer. For TPAs ](https://medrecords.ai/solutions/tpas/) [ Insurance carriers Jurisdiction-correct output at claims volume, delivered straight into your core system. For carriers ](https://medrecords.ai/solutions/insurance-carriers/) FAQ ### Custom 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. [ Medical Summary Reports From record to attested, deposition-ready report — your template, your letterhead. Explore ](https://medrecords.ai/product/summaries/) [ Litigation Chart Packages 9 named litigation chart types, run as one template library on this engine. Explore ](https://medrecords.ai/product/litigation-chart-packages/) [ IME Report Drafting The examiner's report drafted from exam findings and the case record, on this engine. Explore ](https://medrecords.ai/product/ime-report-drafting/) [ Narrative Summary Prose-form case narrative — SOAP or plain-language — drafted from the same extracted data. Explore ](https://medrecords.ai/product/narrative-summary/) ### Send 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. [Test a file ](https://medrecords.ai/test-a-file/?src=product-custom-report-builder) [Book a demo](https://medrecords.ai/demo/) [All capabilities ](https://medrecords.ai/product/)