Guides30 Jul 2026 7 min read

Medical Records Summary vs. Medical Chronology

A medical records summary and a medical chronology look similar but do different jobs. Here's how they differ, and when each is the right document to use.

A doctor and nurse discussing a patient's medical file, illustrating the difference between a records summary and a full chronology
Photo by RDNE Stock project on Pexels

A medical records summary and a medical chronology get used almost interchangeably in personal-injury practice, and that's a problem, because they aren't the same document. Ask for one and get the other, and a demand letter can end up missing the detail an adjuster needed, or a full chronology can turn up three days before a deposition when a two-paragraph overview would have done the job in an hour. The short version: a summary is a compressed narrative of a case. A chronology is the complete, page-cited event list every fact in that narrative should trace back to. Which one you need depends entirely on what you're about to do with it.

TL;DR: a medical records summary is a short narrative overview, usually one to a few pages, written for someone who needs the gist fast. A medical chronology is the full dated event list behind that narrative, with a page citation for every entry. The safest workflow is to build the chronology first and distil the summary from it, not the other way round.

What a medical records summary actually is

A medical records summary reads like a paralegal's cover memo on a case: a page or three of prose that walks through the injury, the treatment course, and the current status, in plain language, for someone who doesn't have time to open the underlying file. It might note that the claimant was seen in the emergency department the day of the incident, followed up with an orthopaedic specialist within the week, had an MRI showing a disc herniation, and has been in physical therapy since. That's genuinely useful, and for a lot of tasks it's all anyone needs.

What a summary usually doesn't have is a citation trail. It tells you an MRI happened; it doesn't necessarily tell you which page, in which of four providers' records, that finding sits on. It compresses a hundred pages of notes into a handful of sentences, which is exactly the point, but it also means some detail is always left out. A good records summary is honest about that trade-off rather than pretending to be exhaustive.

Where a medical chronology differs

A medical chronology is built the opposite way round. Instead of compressing the file into a narrative, it extracts every clinically significant event, visits, imaging, procedures, medication changes, work-status notes, and lays them out in date order, each one tied to the exact page it came from. Nothing gets left out because it didn't fit the story; the chronology is the raw material a story gets built from.

That page citation is the entire difference in practice. A summary asks you to trust that its author read the file correctly. A chronology lets you check. When opposing counsel disputes a fact, or a witness's memory doesn't match what's on paper, a chronology gets you to the source page in seconds. A summary sends you back to square one: reading the file again.

Records summary vs. medical chronology, side by side

Records summaryMedical chronology
StructureNarrative prose, written like a memoDated, itemised event list, one row per event
Page citationsRarely includedEvery entry cited to its source page
Typical lengthOne to a few pagesScales with the file, often tens of pages for a complex case
Best used forFast orientation, intake notes, quick status checksDemand letters, deposition prep, expert review, anything checked against the record

Medical records summary vs. medical chronology

When a summary alone isn't enough

A summary is fine right up until someone needs to verify a claim in it, and litigation is built out of moments like that. Drafting a demand letter around a disputed causation argument means an adjuster's own medical reviewer will want to see exactly where each finding came from, not take a paralegal's word for it, and demand letters that lean on specific, verifiable detail rather than a general narrative tend to land better with adjusters, who are trained to look past the story for the supporting record. Preparing a witness for a deposition means knowing precisely what a treating provider wrote, and when, so a question can be answered from the page rather than from memory. In both cases, a summary that says 'the claimant continued treatment through the spring' isn't enough. Someone is going to ask which visits, on which dates, at which providers, and a summary usually can't answer without the file being reopened.

The same is true whenever a case involves more than one or two providers. A summary of a fifty-page single-provider file is manageable to double-check by re-reading it. A summary of an eight-hundred-page file spanning an ER, two specialists, and a physical therapy practice isn't something anyone can spot-check without a chronology sitting behind it.

Picture a shoulder-injury claim with records from an urgent care clinic, an orthopaedic surgeon, and eleven physical therapy sessions. A summary might say the claimant 'attended physical therapy through the autumn with steady improvement.' A chronology says the claimant attended sessions on eleven specific dates, missed two consecutive appointments in October, and was discharged with a specific range-of-motion measurement on a specific date, cited to page 34 of the physical therapy file. If opposing counsel asks about the missed appointments, only one of those two documents has an answer ready without someone going back to the file.

There's a procedural reason cited detail matters too. Under Rule 26 of the Federal Rules of Civil Procedure, a party must disclose the documents it intends to rely on to support a damages claim, not just a narrative account of them. A chronology, with every entry pointing to a specific page, is built to survive that kind of scrutiny in a way a stand-alone summary was never designed to.

How the two work well together

The two documents aren't competitors, they're stages. Build the chronology first, the complete, cited event list, then distil the summary from it for whoever needs the short version. Written this way, every sentence in the summary traces straight back to a specific entry and page in the chronology behind it, so if a fact in the summary gets challenged, there's already a citation waiting rather than a scramble to find one.

That's the order we built Chartely around. Upload a file and the chronology comes first, the full dated list with page citations and gap flags, because that's the layer everything else should be checked against. A short narrative summary is genuinely easy to write once that structure exists; it's building it backwards, summary first with no cited event list underneath, that leaves a firm exposed the moment someone asks a follow-up question. You can see what a finished, cited chronology looks like before deciding whether a summary needs building from it.

What people mean by "summarize medical records"

When an attorney searches for how to summarize medical records, they're usually describing an outcome, a shorter, readable version of a large file, rather than naming a specific document type. That instinct maps onto either deliverable, depending on what happens next. If the goal is a quick internal status check or an intake note, a straightforward medical case summary, built directly off the raw file, is the right amount of work. If the output is going into a demand package, a deposition binder, or anything a reviewing physician or opposing counsel might pick apart, the safer path is medical record summarization built from a chronology, not instead of one.

Firms that handle a high volume of files sometimes build a records summary template to keep the narrative consistent across paralegals and cases: headings for mechanism of injury, treatment course, current status, and outstanding gaps. A template like that works best precisely because it's filled in from a chronology rather than from a fresh read of the file each time; the structure stays consistent, and the source material behind each line stays checkable.

A summary tells a reader what happened. A chronology lets them check it. Litigation tends to reward the document that can be checked.

Who prepares each, and can software do it

Both documents are traditionally built by paralegals and legal nurse consultants. The professional body for the latter, the American Association of Legal Nurse Consultants, maintains separate template libraries for chronologies and for narrative case summaries, treating them as two distinct deliverables rather than one document with two names. Outsourced record-review services do the same work for a fee. And software increasingly produces a first-pass chronology automatically: a 2023 systematic review of natural language processing in electronic health records, covering 127 studies, lists text summarisation among the established NLP applications in clinical settings, which is part of why automated extraction from medical files has become reliable enough to trust as a starting point, with a human reviewing rather than transcribing from scratch.

None of this removes the review step, and it shouldn't. What automation changes is where the hours go: instead of a paralegal spending days typing dates and page numbers out of a four-hundred-page file, they're checking a machine-generated draft against the source, which is a faster and arguably more careful use of their time.

Build the chronology first, then let a summary write itself. Upload a file and get a cited event list in minutes.

Build a chronology

Frequently asked questions

What is a medical records summary?

A medical records summary is a short narrative overview of a patient's treatment, usually one to a few pages, that describes the injury and course of care in plain language without a full itemised, page-cited event list.

Is a medical records summary the same as a medical chronology?

No. A summary is a compressed narrative; a chronology is the complete dated event list behind it, with every entry cited to its source page. Many cases need both, built in that order.

Who prepares a medical records summary?

Paralegals, legal nurse consultants, and outsourced record-review services traditionally prepare them by hand, and software can now generate a first-pass draft that a person reviews rather than builds from scratch.

Can software summarize medical records automatically?

Yes. Extracting and summarising structured events from clinical text is one of the more established uses of natural language processing in healthcare, though a human review step is still standard practice before anything is filed or sent to opposing counsel.

Which one do I need for a demand letter?

Usually both. The demand letter itself reads like a summary, but it should be built from a full chronology so every factual claim in it can be traced back to a specific page if the adjuster or opposing counsel pushes back.

This guide is general reference, not legal or medical advice. To try it on a real record set, use the medical chronology builder, or see how the same engine works from your own code or an AI agent.

More guides

Build a chronology, then build on it

Build a chronology free, then get an API key for your software or your AI agent, no card to start.

Build a chronology