
From thousands of pages to strategic clarity in hours.

The short answer: A medical chronology example is a completed, date-ordered timeline that shows how language from the medical record becomes a cited row. This page is also a medical chronology sample you can study, with a flagged gap and a discrepancy left visible for the team to check. Litegy's AI can build a chronology like this in hours; the legal team still verifies each entry against the cited page. Below is a fully fictional premises-liability medical chronology example, read from the defense and claims side, with the source excerpt behind a key row so you can see each decision, not just the finished table.
Download the template used in this example: Google Sheet (see the "Example 2 - Defense (Fictional)" tab) · Word (.docx) · CSV
Many published examples share the same shape: a car accident, a neat finished table, and little view of the pages behind it. That shows you what a finished chronology looks like. It does not show you how to get there. This example does three things differently. It starts from a fictional record excerpt and walks it into a row. It includes pre-incident records, which defense counsel and claims teams care about. And it keeps a conflict between two providers visible instead of smoothing it over.
The structure follows our medical chronology template: Date, Provider, Facility, Visit Type, Summary, and Source Page Citation. The template is the empty table; this page is the worked example. A sister post, our med chron sample, compares common sample formats.
| Uncited narrative summary | Blank chronology template | Source-cited worked example | |
|---|---|---|---|
| What you get | A short story of the care | An empty table and column rules | A filled-in case, plus the record language behind a key row |
| Can you check a fact? | Only by searching the file again | Only after you fill it in | Yes. Every row cites a source page |
| Gaps and discrepancies | Easy to smooth over | You have to remember to add those rows | They stay visible as their own rows |
| Best use | A later narrative | Building your own chronology | Learning how a finished row is written |
If you're new to the format, start with what a medical record chronology is.
FICTIONAL CASE. Every name, facility, date, and citation in this post is invented. No real records were used.
Avery Stone (fictional), 54, reports slipping on a wet floor in a grocery store on 01/12/2026 and landing on her right knee. The production includes urgent care, orthopedic, imaging, and physical therapy records after the fall, plus two 2019 records from a sports medicine practice and a surgery center.
Here is the fictional orthopedic note that became the 01/20/2026 row.
Fictional Ortho Clinic, p. 14 (fictional excerpt) S: 54 y/o F seen for R knee pain since slip on wet floor 1/12/26. Pt reports R knee scope in 2019, "fine since then." O: Mild effusion R knee. McMurray + medially. ROM 5-110. A: R knee pain, r/o medial meniscus tear. P: MRI R knee ordered. F/u 2 wks. — H. Invented, MD
And here is how a weak row compares with the row we wrote.
| Weak row | Strong row | |
|---|---|---|
| Date | Jan 2026 | 01/20/2026 |
| Provider | Ortho | H. Invented, MD |
| Facility | (blank) | Fictional Ortho Clinic |
| Visit Type | Visit | Specialist consult |
| Summary | Knee injured in fall, needs MRI. | Right knee pain since fall 01/12/2026. Patient reports knee arthroscopy in 2019. Exam: mild effusion, positive McMurray medially. Plan: MRI right knee (ordered). |
| Source Page Citation | Ortho records | Fictional Ortho Clinic, p. 14 |
| Problem / fix | States a conclusion ("injured in fall"), drops the prior surgery, and cannot be checked. | Uses the record's terms, keeps the reported history, marks the MRI as ordered, and cites the page. |
The production had six sources. Two predate the incident. They go in the chronology because they involve the same knee. They are labeled "pre-incident" in Visit Type so nobody mistakes them for post-fall care.
Every row cites a source name plus page, such as "Fictional Ortho Clinic, p. 14." One convention, used for the whole file.
The urgent care file is two pages. It produces one row because it records one encounter. The orthopedic file produces two rows from two visits.
The claim says the fall caused a meniscus tear. The 01/20/2026 record says "r/o," meaning the tear had not been confirmed. The Summary keeps that wording until the MRI row confirms it.
The urgent care note says the patient denied prior knee injury. The orthopedic note says she reported a 2019 arthroscopy. Both are histories the patient gave, so both Summaries say "patient reports" or "patient denies."
Rather than choose a version, we added a Conflict row that cites both pages. The analysis of why the histories differ belongs in case strategy, not in the chronology.
The physical therapy no-show on 02/10/2026 gets a row with its citation. Then the table is sorted by date and each citation is opened once to confirm the page.
FICTIONAL EXAMPLE. Patient, providers, facilities, dates, and citations are invented.
| Date | Provider | Facility | Visit Type | Summary | Source Page Citation |
|---|---|---|---|---|---|
| 08/14/2019 | F. Notareal, MD | Fictional Sports Medicine | Office visit (pre-incident) | PRE: Right knee pain after recreational tennis. MRI ordered. Arthroscopic partial medial meniscectomy discussed and later scheduled. | Fictional Sports Medicine, p. 3 |
| 09/20/2019 | F. Notareal, MD | Fictional Surgery Center | Procedure (pre-incident) | PRE: Right knee arthroscopy with partial medial meniscectomy. | Fictional Surgery Center, p. 2 |
| 01/12/2026 | G. Pretend, PA-C | Fictional Urgent Care | Urgent care visit | Patient reports slipping on a wet floor and landing on right knee. Patient denies prior knee injury. X-ray right knee: no fracture; mild joint-space narrowing. Knee sleeve, ibuprofen. | Fictional Urgent Care, pp. 1-2 |
| 01/20/2026 | H. Invented, MD | Fictional Ortho Clinic | Specialist consult | Right knee pain since fall 01/12/2026. Patient reports knee arthroscopy in 2019. Exam: mild effusion, positive McMurray medially. Plan: MRI right knee (ordered). Follow up 2 weeks. | Fictional Ortho Clinic, p. 14 |
| 01/20/2026 | Flag | N/A | Conflict | CONFLICT: Urgent care note records denial of prior knee injury; ortho note records 2019 arthroscopy. Both are patient-reported histories. | Fictional Urgent Care, p. 1; Fictional Ortho Clinic, p. 14 |
| 01/29/2026 | J. Fakename, MD (radiology) | Fictional Imaging Center | Imaging | MRI right knee: complex tear posterior horn medial meniscus; postsurgical changes; moderate chondromalacia medial compartment. | Fictional Imaging Center, p. 2 |
| 02/10/2026 | K. Unreal, PT | Fictional Physical Therapy Group | Missed appointment | GAP: Initial PT evaluation scheduled; patient no-show documented. Rescheduled visit 03/02/2026. | Fictional Physical Therapy Group, p. 1 |
| 02/24/2026 | H. Invented, MD | Fictional Ortho Clinic | Office visit | Persistent pain and catching. Repeat arthroscopy discussed as an option; patient to consider. Work status: modified duty. | Fictional Ortho Clinic, p. 17 |
Pre-incident records change how the imaging reads. The 01/29/2026 MRI notes postsurgical changes and chondromalacia. Without the 2019 rows, a reader could take the MRI as showing only new injury. With them, both sides can see what was already there and argue from the same facts.
The conflict is a fact, not a conclusion. The Conflict row does not say the patient was untruthful. It shows two records that disagree and where to find them.
Gaps are rows, not blanks. The no-show is easy to miss in a stack of records and easy to find in a filtered spreadsheet.
The same discipline applies on the plaintiff side. The pillar guide has a fictional personal-injury example, and our med chron sample post includes a fictional medical malpractice case with clock times.
Condensed into a narrative, this chronology becomes a medical record summary.
Use this on every row before the chronology leaves your desk:
Building this example meant reading every page, including the ones that produced no row. On a real file, that reading is most of the work. Litegy is a pure-AI medical-record case analysis platform for personal-injury, medical-malpractice, and insurance-defense firms and claims teams. It accepts all file types, uses AI to sort records, and produces medical chronologies and reviews in hours. Learn more about Litegy or see the med chron software.
Want to see a full analysis? Get a free sample Litegy AI medical record analysis.
Organizing your own records for an injury or disability claim? See how to organize your medical records.
It is a completed chronology for one case, showing how entries are dated, summarized, and cited. The example on this page is fictional. Use it to study row-level decisions, then build your own with the template.
Detailed enough that a reader understands the encounter without opening the record, and short enough to scan. Include the complaint, key findings, assessment, and plan, plus values or times when they matter.
Yes, when they involve the same body part or condition. Label them as pre-incident so readers can separate prior history from post-incident care. Both plaintiff and defense teams need that distinction.
Give the conflict its own row or label, summarize each version, and cite both pages. Do not pick a winner in the Summary column; leave that judgment to your case analysis.
No. A template is a blank table. A medical chronology sample or example is a filled-in case you can study. This page is the worked example. A sister post compares common sample formats.
Yes. Record the scheduled date, the documented no-show, and the page that shows it, without guessing why it happened. Missed appointments are easy to lose in a stack of records.


Copyright © 2026