Medical timeline formats: 6 ways to draw a patient's history
Short version: pick the format by the question. Order of events: an event line. What happened in parallel: swimlanes. How long a drug or work restriction lasted: duration bars. Where the file is thin: a density strip. Whether treatment worked: a trend panel. For a full review file, combine lanes, bars and a key date on 1 axis, and keep the cited table beside it.
Limits: Tool facts come from each vendor's own website, read 2026-11-12; we have not used those products. The case on this site is synthetic, with no real patient.
Which format answers which question
| Format | Answers | Use it for | Main trap |
|---|---|---|---|
| Event line | What came first, and how far apart? | Under about 30 events, or 1 admission | Labels collide; dense days hide marks |
| Swimlanes | What ran in parallel? | Multi-provider files, 6 to 24 months | Too many lanes; empty lanes waste space |
| Duration bars | How long, and did spans overlap? | Medications, admissions, work status, therapy courses | Missing end dates drawn as "still going" |
| Density strip | Where is the file thick or empty? | Triage of a large file before reading | Counts pages or events, not care |
| Trend panels | Did a value change after treatment? | Labs, pain scores, range of motion, weight | Uneven sampling looks like a smooth line |
| Combined view | The whole case on 1 page | Review files, report exhibits | Clutter; color carrying meaning alone |
Diagrams on this page are original and drawn from the synthetic case on the interactive timeline page. No real patient.
Event line: order and spacing
An event line puts every event as a mark on 1 axis. It answers "what came first" and "how far apart" faster than any other format. It works for 1 admission or the first weeks after an injury.
It fails past about 30 events. Labels collide, so tools either hide them (you hover to read) or stagger them (the eye loses the axis). Several events on 1 day stack into 1 mark. When you read an event line from a tool, ask how it shows same-day events, and count them against the table.
Swimlanes: what ran in parallel
Swimlanes give each category its own row on a shared time axis: visits, imaging, procedures, medications, work status, or 1 lane per provider. They answer "what was going on at the same time," which is most of what a reviewer asks about a multi-provider file.
Keep lanes to 4 to 7. Past that, the eye stops comparing across rows. Choose lanes by the question: by category for treatment course, by provider for "who saw the patient when," by facility for transfers. A tool that offers only 1 fixed lane set limits the questions you can ask.
Duration bars: how long, and what overlapped
Duration bars turn spans into length: medications, admissions, work restrictions, therapy courses, splints and casts. They answer "how long" and "what overlapped" at a glance, which is the task the JAMIA medication timeline study found tables handle worst (see timeline vs table).
The trap is the end date. Records often show a start (a prescription) and never a clear stop. A tool that draws the bar to today, or to the next visit, invents a fact. Ask how the tool marks an unknown end, and whether a dose change splits the bar or vanishes inside it.
Density strip: where the file is thick or empty
A density strip counts events or pages per week or month. It's a triage tool: before you read 2,000 pages, it shows where they cluster. Medrecords AI shows a version of this as a month strip above its timeline, with a pin on the case's key date.
The trap is reading it as a measure of care. A thick month can be 1 admission with 300 nursing pages. A thin month can be 1 visit that matters more than all of them. Use it to plan your reading, then check the rows.
Trend panels: did a value change after treatment?
A trend panel plots a value over time (a lab, a pain score, range of motion, weight, A1c) and stacks it under the treatment marks on the same axis. It answers "did it work," which no event list can.
The trap is the line between points. If readings are 4 months apart, a smooth line suggests data you don't have. Draw points, break or dash the line across long gaps, and keep the y-axis honest (start at 0 for scores, use the reference range for labs).
Combined view: the whole case on 1 page
The combined view is swimlanes plus duration bars plus a key date, on 1 true-date axis, sometimes with a density strip above and a trend panel below. It's the format the home page figure and the interactive timeline use, and the one most worth having for a review file.
It's also the easiest to clutter. 4 rules keep it readable:
- 1 axis, true dates. Never space events evenly. Break the axis only with a visible break mark.
- Shape plus color. Circles, squares and diamonds survive grayscale printing and colorblind readers; color alone doesn't.
- Labels on demand. Show labels on bars wide enough to hold them; put the rest in a hover or a side panel with the page cite.
- A tray for the undated. List undated records under the chart so the reader knows they exist.
Then check the output against the 12-point checklist. If you need to draw one yourself, start from the template.