New records land mid-case. The chronology already knows.
Live Record Updates means uploading new documents to an open case never requires a manual re-run: the chronology, the index, and every report tied to the case re-sort and regenerate automatically around the new material the moment it lands, so review picks up right where new records left off — no re-queuing, no starting over.
By Ahmed Jemaa, Co-Founder & CEO of Medrecords AI · Published 25 Aug 2026 · Updated 30 Aug 2026
Upload without stopping the case.
Records rarely all arrive at once — a subpoena response lands weeks later, a supplemental exam gets scheduled, a provider finally sends the missing chart. Live Record Updates treats a new upload to an open case exactly like the first one: the new pages are read in and processed the moment they land, with nothing to close, reopen, or re-queue.
Every downstream output re-sorts with it.
A new upload doesn't just add pages to a pile — the chronology and index realign around the new material, and any report still in draft regenerates to reflect it. What has already gone out the door stays exactly as it went out, so review keeps moving without second-guessing what's already been sent.
A case doesn't need to be finished to be open.
Litigation and claims files grow in bursts, not all at once. Treating every new batch as a fresh case means re-doing work and risking drift between versions. Medrecords AI treats the case as one living file: it re-sorts around what's new, and it never touches what's already been exported or attested.
See Custom Report BuilderFrom new upload to updated case, automatically.
4 steps, and only one of them is something you do.
Review starts on what's uploaded today, before every record is in hand.
Uploaded to the same case whenever they land — no need to close or reopen anything.
Chronology, index, and draft reports regenerate around the new material, no trigger required.
Anything already exported or attested stays exactly as it was — nothing is silently altered.
Watch a finished case take in new records
The clip opens on a completed demo case. Upload Additional Files takes 2 new PDFs: an orthopedic follow-up from Maple Ridge Orthopedics dated 06/12/2025 and a PT discharge summary from Cedar Creek Physical Therapy dated 06/20/2025. After the upload, the case is queued for processing. When the confirmation panel reopens, it keeps the earlier answers and marks what the new records added: lumbar spine as a new body part and 06/12/2025 as a new date. Back on the case, a banner reads 2 new documents since the report. Analyze new records produces a briefing in sections: 1 change to the prior report, work capacity from off work to light duty, and 2 net-new facts, each tagged with the record it came from. Every name, provider and date in the demo is invented.
Transcript
- Add new records to a finished case with Upload Additional Files.
- Once processed, the confirmation panel marks what is new.
- A banner counts the new documents. Run the analysis.
- The briefing cites what the new records change or add.
Who keeps a case open longer.
Different reasons records trickle in, same benefit: the case doesn't have to restart to absorb them.
A late subpoena response joins the file instead of starting a second one.
For PI firmsOngoing treatment keeps adding visits; the claim file keeps pace automatically.
For workers compNo re-indexing a file by hand every time a new batch of records shows up.
For LNCsA supplemental record request updates the file the evaluator already has open.
For IME orgsRelated features.
The timeline that re-sorts itself every time a new record lands.
See the chronologyA confirmed date on a flagged document triggers the same automatic re-sort.
See the featureDraft reports regenerate with the case; exported ones stay exactly as sent.
See the featureThe narrative that stays current as the underlying record grows.
See the featureLive Record Updates, answered.
The new documents are read in immediately, and the chronology, index, and any reports tied to the case re-sort and regenerate around them — no need to start the case over.
No. There's no manual re-run step and no re-queuing the case — uploading the new records is the only action required.
The chronology and index re-sort to place the new material where it belongs, and any report still in draft regenerates to reflect it.
No. Regeneration updates the working outputs automatically, but any report already exported or attested stays exactly as it was exported — it's not silently altered by a later upload.
No set limit — records can be added mid-case as many times as the file requires, each time triggering the same automatic re-sort.
The new documents go through the same processing as the original upload, so timing scales with what was added rather than the size of the whole case.
Yes — whether it's one supplemental record or a large new batch, the same automatic re-sort and regenerate behavior applies.
Add a record mid-case and watch it land.
Book a quick demo, or upload a single file and see the re-sort happen in real time. No commitment. Handled under our BAA; never used to train a model.