# Live Record Updates Software > Live Record Updates re-sorts and regenerates the chronology, index, and reports automatically when new records land mid-case — no manual trigger, no re-run. Canonical page: https://medrecords.ai/product/live-record-updates/ --- NewWe now read the actual MRI and CT imaging — not just the radiologist's 1-page report. [See how →](https://medrecords.ai/product/imaging/) [Home](https://medrecords.ai/) ›[Product](https://medrecords.ai/product/) › — Live Record Updates Live Record Updates ## 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. [Book a demo](https://medrecords.ai/demo/) [Test a file ](https://medrecords.ai/test-a-file/?src=product-live-record-updates) Adams, T. · Case #IME-4812 Live Activity 14 new pages uploaded — Supplemental records, today Chronology re-sorted — Automatic · no trigger needed Index & draft report regenerated — Automatic · no trigger needed Exported report — unchanged — Attested 4/02 — not re-opened Built on medical-record intelligence The same engine that reads the file once **reads it again automatically** every time the file grows. ### 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. New uploads are detected and processed automatically, any time No manual trigger, no re-running the case from scratch Upload timeline — 3 batches, 1 case Initial upload — 320 pages Case opened Supplemental — 14 pages Auto re-sorted Missing chart, received — 8 pages Auto re-sorted Same case, same URL, no re-run — **342 pages** total to date. What re-sorts automatically vs. what stays put Chronology & index Re-sorts automatically Draft reports Regenerates automatically Exported / attested reports Stays exactly as exported ### 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. Chronology, index, and draft reports stay current with every upload An exported or attested report is never silently rewritten Two approaches Generic tools · New file, new case — · Manually re-run the whole packet — · Old outputs orphaned or overwritten Live Record Updates Same case, records added in place Exported reports untouched, always The differentiator ### 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 Builder ](https://medrecords.ai/product/custom-report-builder/) ### From new upload to updated case, automatically. 4 steps, and only one of them is something you do. Case stays open Review starts on what's uploaded today, before every record is in hand. New records arrive Uploaded to the same case whenever they land — no need to close or reopen anything. Everything re-sorts automatically Chronology, index, and draft reports regenerate around the new material, no trigger required. Exported reports stay put Anything already exported or attested stays exactly as it was — nothing is silently altered. ### Who keeps a case open longer. Different reasons records trickle in, same benefit: the case doesn't have to restart to absorb them. [ Personal injury A late subpoena response joins the file instead of starting a second one. For PI firms ](https://medrecords.ai/solutions/personal-injury-plaintiff/) [ Workers comp Ongoing treatment keeps adding visits; the claim file keeps pace automatically. For workers comp ](https://medrecords.ai/solutions/workers-comp/) [ Legal nurse consultants No re-indexing a file by hand every time a new batch of records shows up. For LNCs ](https://medrecords.ai/solutions/legal-nurse-consultants/) [ IME organizations A supplemental record request updates the file the evaluator already has open. For IME orgs ](https://medrecords.ai/solutions/ime/) ### Related features. [ Medical Chronology The timeline that re-sorts itself every time a new record lands. See the chronology ](https://medrecords.ai/product/chronology/) [ Undated Document Flagging A confirmed date on a flagged document triggers the same automatic re-sort. See the feature ](https://medrecords.ai/product/undated-document-flagging/) [ Custom Report Builder Draft reports regenerate with the case; exported ones stay exactly as sent. See the feature ](https://medrecords.ai/product/custom-report-builder/) [ Narrative Summary The narrative that stays current as the underlying record grows. See the feature ](https://medrecords.ai/product/narrative-summary/) FAQ ### Live 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. [Book a demo](https://medrecords.ai/demo/) [Test a file ](https://medrecords.ai/test-a-file/?src=product-live-record-updates)