NewMissing Records Detection: flags every visit, provider, and date missing from the file. See how →
Home›Product›Narrative Summary
NARRATIVE SUMMARY SOFTWARE

The record, told as a narrative — the case as prose, every line cited.

Narrative summary software turns the record into prose — a summary of the case drafted from the same structured record as Medical Summary Reports, for the reader who wants the story, not just the entries. Every sentence is cited to its page and source, so the narrative stays checkable against the file.

Adams, Timothy — right knee · Case #IME-4812 Narrative draft
Format Plain language SOAP

Mr. Adams first sought care for the right knee after the workplace incident, presenting with pain and limited range of motion p.14. Imaging of the right knee confirmed the working diagnosis p.140, and a course of physical therapy followed.

Across 7 documented visits since 4/02, the treating notes describe steady improvement p.38, with the most recent progress note recording continued gains in function p.129.

Every sentence — cited inline 342 pages read
One engine
Same data as your summary reports
2 registers
SOAP or plain language
Every sentence
Cited to page and source

The story of the case, in prose that cites.

A chronology gives you the entries; the AI medical narrative summary gives you the through-line. Injury, first presentation, the arc of treatment, and where things stand now — written as connected paragraphs a reader can absorb in 1 pass, with each factual sentence carrying its page-level citation inline.

Connected prose, not a stitched list of entries
Inline page citations on every factual sentence
Timeline entry → narrative sentence
Ortho consult — 4/02 p.14

"Mr. Adams was evaluated by orthopedics on April 2, where the right-knee complaint was documented and a treatment plan initiated."

Same fact, same citation — new form CITED
The narrative reads like a story. It verifies like a table.
1 record · 2 registers
SOAP
S: Right-knee pain reported O: Exam and imaging findings A: Working diagnosis P: Therapy course, follow-up
PLAIN LANGUAGE

"He reported knee pain; the exam and imaging supported the diagnosis, and a therapy plan was started."

Same facts, same citations — the register fits the reader.

SOAP or plain language — the reader picks the register.

A SOAP note summary generator for the clinical reader; plain-language prose for the adjuster, the client, or the jury. The drafting is also injury-type-aware: an orthopedic knee case reads in orthopedic terms, a brain-injury case leads with cognitive findings. The facts come from the record either way; nothing is invented for style.

SOAP structure per encounter, or one flowing account
Injury-type-aware phrasing, never invented facts

Built on the same engine as your reports — honestly.

No secret second pipeline: the narrative medical record summary is built on the same engine as Medical Summary Reports and the Custom Report Builder. The record is read and structured once; the narrative is a template variant — one more way to write down what the engine found, with the same citation discipline underneath.

One extraction, many output forms — no re-processing
Report, chronology, and narrative always agree
One structured record · 3 outputs
Medical Summary Report — templated, attested38 FIELDS
Custom Report — your template, your letterheadTEMPLATED
Narrative Summary — the story, in proseTHIS PAGE
Same extraction, same citations — the outputs can't disagree.
Inside the prose · every claim carries its source
"…presenting with pain and limited range of motion…" p.14
"…improving across 7 documented visits since 4/02…" p.38
Statement the record can't support — not written FLAGGED
Prose that survives cross-examination
The citation standard

Citations don't stop where the paragraphs start.

Narrative is where most AI summaries get loose: smooth prose, no receipts. Here, every factual sentence keeps its page-level citation inside the paragraph, and anything the record doesn't support is flagged rather than written. Audit-grade and legally defensible — the story reads well and still traces to its source.

See Verifiable AI Citations

From records dump to cited narrative.

3 steps between the packet and prose you can hand to any reader.

01
Upload the file

Records, imaging, bills, and legal documents — the same file that feeds your reports and chronology.

02
Pick the register

SOAP for the clinical reader, plain language for everyone else — drafted from the structured record, cited sentence by sentence.

03
Review and export

Your reviewer checks the flagged gaps, clicks any citation to its page, and exports on your template.

See it run

Watch a narrative edit wait for your review

It opens on the Document Index of the demo case Rivera v. Coastline Freight. A click on the MRI cervical spine record from Harbor Point Imaging opens its popup: a descriptive summary first, then cards for the providers named (the author is marked), the treatment rendered, the diagnostic codes as written and the body parts affected. Next, "Providers in this case" lists 5 people found in 41 mentions. Laura Brennan, MD opens to 3 spellings and the reason each was merged, such as "initial matches one person". The confirmation panel then suggests body parts with record counts, and a date of injury of 03/14/2025 stated in 5 records with quoted citations, next to a 1-record outlier you can flag. Last, a steer instruction adds the MRI impression to the narrative, and the change waits in a word diff for review. Every name, provider and date in the demo is invented.

Transcript
  1. Open a record for its summary, providers, codes and body parts.
  2. See each provider once, with every spelling and mention count.
  3. Confirm the injury date and body parts the records state.
  4. Steer the narrative, then review the changes before you accept.

Download the video (MP4, 20 seconds)

Who reads the record as a story.

Different desks, same need: the whole case in prose, before the table of entries.

FAQ

Narrative summaries, answered.

Both. Same content, 2 registers: SOAP organizes the narrative into Subjective, Objective, Assessment, and Plan per encounter for a clinical reader; plain language tells the same story for a reader without clinical training. Pick per case, or generate both from the same file.

A chronology is a date-ordered table of events, 1 line per event, built to scan. A narrative is prose: it connects those events into the story of the injury and the care that followed. Both are built from the same structured extraction, and both cite to the source page.

No, and we say so plainly: the narrative is a template variant on the same engine as Medical Summary Reports and the Custom Report Builder, not a new extraction pipeline. The record is read once; the narrative is one more way to write down what it found.

Yes. The drafting adapts to the injury profile in the record: an orthopedic knee case reads in orthopedic terms, a brain-injury case leads with cognitive findings. The facts and citations come from the record either way; nothing is invented for style.

Every factual sentence carries a page-level citation, inline in the paragraph. Where the record does not support a statement, the narrative does not make it: gaps are flagged for your reviewer, never papered over with prose.

Related capabilities.

The same structured record and citation standard, in other output forms.

Related features.

The narrative draws from the same extraction as these — sharpen the input, and the story sharpens with it.

Hear one of your own files told as a story.

Upload a file and get back a sample narrative — SOAP or plain language, every sentence cited. Handled under our BAA; never used to train a model.