[ PERSONAL INJURY · LITIGATION ]
A chronology engine built for your firm. It reads the medical records you already hold, writes every visit, diagnosis and bill in date order with the source page cited, tracks what's still missing, and drafts the demand package. An attorney reviews it before anything leaves the firm, and the code, the data and the cloud account stay yours.
Show me on a closed case30 minutes with a co-founder. Bring a closed case; we'll walk through what the engine would produce.
15-80 hrs
to build one chronology by hand
Every entry
cites its source page
3
open-source connectors: Filevine, Clio, MyCase
100%
code, IP and data owned by the firm
[ HOW IT WORKS ]
The paralegal hours go into reading, sorting and typing. The engine does those three. The judgment stays with your team, and every entry can be checked against the page it came from.
Records in
PDFs, faxes and portal downloads, read in place from Filevine, Clio, MyCase or SharePoint.
Split and read
Scans are converted to text and split by provider, date of service and document type.
Entries with citations
Each visit, diagnosis, procedure, medication and bill becomes an entry tied to its source page.
Attorney review
Gaps, conflicts and entries without a source go to a review queue. A person approves the chronology.
Outputs
Chronology, treatment summary, medical specials and a demand package draft in your template.
[ WHAT YOUR TEAM GETS ]
CHRONOLOGY
Visits, diagnoses, procedures, imaging and medications by date, each tied to the page it came from. Pre-existing conditions and prior injuries pulled into their own section.
RECORDS TRACKING
Every provider in the chronology checked against the records on file. Missing date ranges and providers become a request list with follow-up dates, so a gap in the file doesn't become a gap in the demand.
SPECIALS
Charges totalled by provider from the bills and ledgers in the file, with billed, paid and adjusted amounts kept apart, ready for a paid-versus-incurred argument.
DEMAND PACKAGE
Treatment summary, specials table and injury narrative assembled in your firm's demand template, with exhibits linked. An attorney edits and signs. Nothing is sent to an adjuster by the software.
DEFENSE SIDE
For insurance and long-term care defense: gaps in treatment, prior conditions and billing that doesn't match the care, laid out for the deposition outline.
SEARCH
"When was the first mention of radiating pain?" answered with the page number, across every record in the matter.
[ THREE WAYS TO GET A CHRONOLOGY ]
All three work. They differ on who holds the records, how the cost grows with case volume, and what you keep if you stop paying.
If you run a handful of cases a year, a service is probably cheaper. The math changes with volume. Our Filevine pricing breakdown shows what's metered and gated inside one case system.
[ WORKS WHERE YOUR RECORDS ALREADY ARE ]
A good share of the time a paralegal spends on a chronology goes to finding the right PDFs, downloading them and uploading them somewhere else. We wrote the open-source connectors that let software read Filevine, Clio and MyCase directly, so the engine starts from the matter, not from a folder on someone's desktop.
[ RECORDS ARE PHI ]
The engine runs in your cloud account. Any AI model it calls runs on a plan covered by a BAA, with training off. We sign a BAA with you before we touch a record.
If the engine can't tie a fact to a page, it doesn't write it into the chronology. It goes to the review queue instead.
Chronologies and demand drafts are drafts until a person approves them. The approval is recorded with a name and a time.
Which documents were read for which matter, by which job, and who opened the result. Kept where staff can't edit it.
Running the AI part on Claude? Check which Claude plans Anthropic's BAA covers before any record goes in.
[ SAME ENGINE, OTHER MARKET ]
A home health agency receiving a hospital referral has the same problem as a PI paralegal: a pile of clinical documents and a few facts that decide what happens next. The engine reads the referral packet and fills the intake record, with each field tied to the page it came from.
Intake staff confirm every field before it reaches the EHR. For the agency side of this work, see healthcare AI automation and EHR integration.
FROM THE REFERRAL PACKET
Every field confirmed by intake staff before it's saved.
[ HOW WE BUILD IT WITH YOU ]
Fixed scope, a timeline in weeks, and a written plan before any build starts. We build this per firm; it isn't a subscription product.
1
We look at how records arrive, where they're stored and what your best chronology looks like today. You get a written scope and a fixed plan.
2
The engine runs on cases your team already finished by hand. Your paralegals compare its output to theirs, entry by entry, and we tune until they'd sign it.
3
Open matters, demand templates, training for the team, and a handover: repository, cloud accounts and documentation in the firm's name.
[ FAQ ]
Software that reads a client's medical records and lays out every visit, diagnosis, procedure, medication and bill in date order, so an attorney can see the treatment story without reading every page. Good chronology software cites the exact page each entry came from, flags gaps in treatment, and keeps the original records one click away.
Those are products you subscribe to, priced and run by the vendor, and your records go into their system. We build the chronology engine for your firm, it runs on records you already hold, in cloud accounts your firm controls, and the code and IP are yours. In Filevine, MedChron is part of the LOIS Expert package, per Filevine's own product terms. If a subscription fits your volume, use it. If you want the workflow, the data and the cost to stay under your control, that's what we build.
From wherever your firm keeps them today: Filevine, Clio, MyCase, SharePoint or a shared drive. We maintain open-source connectors for Filevine, Clio and MyCase, so the engine reads documents in place instead of making paralegals download and re-upload files.
Yes, as a draft. From the chronology and the bills it assembles the treatment summary, the medical specials and the injury narrative in your firm's template. An attorney edits and approves it. Nothing goes to an adjuster without that review.
Medical records are PHI, so the engine runs in your cloud account under a BAA, and any AI model it calls runs on a plan covered by a BAA with training off. Every document read and every draft is logged. Access follows your matter permissions. We never claim nothing leaves the firm when a hosted model is involved; we tell you exactly which vendor processes what, under which agreement.
Every entry carries the page it came from, so a reviewer checks it against the source in one click. Entries the engine can't tie to a page are not written at all; they go to a review queue. Attorney review is a required step in the workflow.
Yes. The same engine builds the plaintiff's chronology and rebuts it for the defense: insurance defense, nursing home and long-term care defense, and trucking defense firms use the same timeline to find gaps in treatment, pre-existing conditions and billed-versus-paid differences.
Yes. The code lives in your repository, the infrastructure is in your cloud account, the IP is assigned to your firm, and the documentation is written so another developer could take it over. You're not dependent on us to keep it running.
[ GET STARTED ]
30 minutes with a co-founder. We look at how your records arrive and what your chronologies look like today, and tell you honestly whether building one is worth it at your volume.
Show me on a closed case