Medical record chronologies, self-serve
Minutes, not weeks. Cited to the page.
Upload the records, get back a page-cited chronology with gaps flagged and a narrative drafted. Minutes, not weeks. A fraction of per-page service pricing.
Free for 50 pages/month, no card. Every event links back to the exact page it came from.
How it works
From a stack of records to a filed chronology
No template to configure, no manual page-by-page transcription, upload and get a cited, ordered timeline.
- 1
Upload the records
Drop in the case medical records as a PDF, one file or a stack from multiple providers, scanned or digital.
- 2
Extract & cite
Every clinically significant event is pulled out with a date, provider, facility, plain-English summary and a citation to the exact page it came from.
- 3
Review & export
Review the timeline, gap flags and narrative draft, then export to Word for filing, CSV for your own analysis, or call it from your own code or agent.
A real result
What you actually get back
Not a mockup, every row below is the same shape the engine returns for a real upload, run on bundled synthetic records.
Synthetic sample records, not a real patient.
Jordan Avery
14 Feb 2026 – 6 Jun 2026 · 4 providers · 4 facilities
| Date | Event | Provider / facility | Page |
|---|---|---|---|
| 14 Feb 2026 | ED visit for neck/back pain after MVCEmergency | Elena Cho, MD · Riverbend Regional Medical Center Emergency Department | p. 1 |
| 14 Feb 2026 | Cyclobenzaprine and ibuprofen prescribedMedication | Elena Cho, MD · Riverbend Regional Medical Center Emergency Department | p. 2 |
| 14 Feb 2026 | Off work pending orthopedic follow-upWork status | Elena Cho, MD · Riverbend Regional Medical Center Emergency Department | p. 2 |
| 16 Feb 2026 | MRI cervical and lumbar spineImaging | Marcus Feldman, MD · Riverbend Regional Medical Center Department of Radiology | p. 3 |
| 24 Feb 2026 | Orthopedic consultationConsult | Aisha Patel, MD · Crestview Orthopedic & Spine Associates | p. 4 |
| 24 Feb 2026 | Work status remains off workWork status | Aisha Patel, MD · Crestview Orthopedic & Spine Associates | p. 4 |
| 3 Mar 2026 | Initial physical therapy sessionTherapy | Sam Whitfield, PT · Meridian Physical Therapy Group | p. 5 |
| 24 Mar 2026 | Physical therapy reassessmentTherapy | Sam Whitfield, PT · Meridian Physical Therapy Group | p. 6 |
| 28 Mar 2026 | Cleared to modified dutyWork status | Aisha Patel, MD · Crestview Orthopedic & Spine Associates | p. 7 |
| Treatment gap flagged. 70 days (28 Mar 2026 to 6 Jun 2026) | |||
| 6 Jun 2026 | Orthopedic follow-up visitVisit | Aisha Patel, MD · Crestview Orthopedic & Spine Associates | p. 8 |
| 6 Jun 2026 | Discharged from treatment, full duty clearedWork status | Aisha Patel, MD · Crestview Orthopedic & Spine Associates | p. 9 |
Narrative draft
Jordan Avery was seen in the Riverbend Regional Medical Center Emergency Department on 02/14/2026 for neck and low back pain after a motor vehicle collision, and was discharged with medication, a cervical collar, and off-work status. Follow-up MRI on 02/16/2026 showed a mild C5-C6 disc bulge and small L4-L5 disc protrusion without fracture. She was seen in orthopedic consultation at Crestview Orthopedic & Spine Associates on 02/24/2026 and referred to physical therapy at Meridian Physical Therapy Group, attending sessions on 03/03/2026 and 03/24/2026 with documented improvement. On 03/28/2026 she was released to modified duty with lifting and positional restrictions, and by the final orthopedic follow-up on 06/06/2026 her cervical strain had resolved and she was discharged from active treatment and cleared to return to full duty without restrictions.
11 events · 9 pages · 1 gap flagged
What's inside
Built for people who read medical records for a living
Every event cited to its page
Date, provider, facility and a plain-English summary for every event, with a citation back to the exact source page, so review takes minutes, not a re-read of the file.
Treatment gaps flagged automatically
Any gap of 45+ days between dated events is flagged with its exact length, before opposing counsel finds it first.
Narrative draft included
A plain-language summary of the course of care, ready to drop into a demand letter or case review, built from the same cited events.
Word, CSV and JSON export
Export a filing-ready Word chronology, a spreadsheet for your own analysis, or structured JSON for your case-management system.
API and MCP for agents
The same engine as a REST API and a hosted MCP server, so a legal-AI agent can build a chronology mid-task, not just a person on the web app.
Records never stored
Your uploaded records are processed in memory to build the chronology, then not retained. The chronology itself is yours to keep or delete.
Agents welcome
Callable by your code, or your AI agent
Legal-AI agents drafting a demand letter or prepping a deposition need the same thing a paralegal needs: a trustworthy, page-cited read of the file. Chartely ships the exact engine behind the site as a public REST API and a hosted MCP server, with a sandbox key so an agent can try it before anyone sets up an account.
- Single-key REST API + MCP server over the same chronology engine
- Batch endpoints and webhooks for unattended agent workflows
chartely api
$ curl https://chartely.com/api/v1/chronology \
-F "file=@records.pdf"
{
"eventCount": 11,
"gaps": [ ...1 flagged ],
"confidence": 1,
"narrative": "...",
"engine": "claude-cli"
}Case types
Built for how you actually use a chronology
Records are processed in memory and never stored, the chronology is yours.
Every event links to its source page, so review takes minutes, not a re-read of the file.
Treatment gaps flagged automatically, a confidence score on every event, never a silent guess.
Pricing
Free to start. Metered when a real matter shows up.
A real free tier for a genuine small record set, paid plans meter per page for firms running matters every week.
Free
Run a real record set and see a page-cited chronology. No card.
$0forever
- 50 record pages / month
- Page-cited events + treatment-gap flags
- Narrative summary draft
- CSV & JSON export
+2 more
Start freePro
Most popularFor firms and builders running real matters every week.
$49/mo
- 1,000 pages/mo included, then $0.06/page
- Word export for filing + no footer credit
- Chronology API + API keys (120/min)
- MCP server for AI legal agents
+3 more
Get ProScale
For high-volume firms, record-retrieval shops and agent products.
$199/mo
- Everything in Pro
- 7,500 pages/mo included, then $0.04/page
- 600 req/min burst · batch up to 200
- Hosted MCP at production quota
+2 more
Get ScaleFAQ
Common questions
What is a medical chronology?
A dated, page-cited list of every clinically significant event in a set of medical records, visits, imaging, procedures, medications and work-status notes, arranged on one timeline instead of scattered across a stack of PDFs.
How accurate is the extraction?
Every event carries a confidence score, and treatment gaps are flagged automatically. Low-confidence pages (poor scans, unusual formatting) are surfaced for review rather than silently guessed at.
Is my data stored?
Chartely organizes the medical records you provide. It is not legal or medical advice, and automated extraction can misread poor-quality scans. Review the chronology before you rely on it. Every event links to its source page, so review takes minutes, not days.
How is this different from an outsourced chronology service?
Outsourced services typically charge $1.50-$4.00 a page and take 5-10 business days. Chartely returns a chronology in minutes, with your included pages then a flat $0.06/page on Pro. See /vs-outsourced-services for the full comparison.
Can AI legal agents use Chartely?
Yes, that's a first-class use case, not an afterthought. The same engine is available as a REST API and a hosted MCP server, so an agent drafting a demand letter or prepping a deposition can call it as a tool. See /developers.
Build your first chronology free
No card required. 50 pages/month free. Page-cited, gap-flagged, and never stored after processing.