An AI chronology workflow for legal nurse consultants
Quick answer
Let the tool sort, remove duplicates and draft entries with a page cite each. Then you check the entries the case turns on against the page, build the missing-records list, write the clinical analysis yourself, and deliver with production page numbers and a short method note.
Limits: Rules are cited as read on 2026-11-19 and tool facts as read on 2026-11-16. Nothing here is legal advice; the retaining attorney decides how HIPAA and bar rules apply to a matter.
Step 1: intake without losing the production's page numbers
Upload the production exactly as counsel sent it. Do not merge, split or reorder the PDFs first. Many tools build their own shorter file once duplicates are removed, and their page numbers follow that shorter file. If the original pages carry Bates numbers, you need a way back to them.
- Record the Bates range received, the page count and the date.
- Keep the tool's deduplication log: each removed page, and the page kept in its place.
- Keep amended or corrected versions of a note. They are not duplicates, even when most of the text matches.
- List the pages the tool could not read. Poor scans and handwriting go on this list, not into a summary.
Step 2: first-pass chronology with a cite on every entry
Ask for 1 entry per clinical event, with date, charted time of day where the page shows one, provider, what happened and the page cite. Reject output that summarizes without cites. An entry you cannot trace to a page is an entry you cannot defend. Medrecords AI builds this first pass with a source page on every line and drops duplicate pages at upload, without billing them.
Watch 3 things in the first pass:
- Time of day. Some tools keep the charted time. Others only keep the date. In a fall, a sepsis or a post-op bleed, the hours matter.
- Copied-forward text. A note that repeats yesterday's assessment can read as a new finding.
- Flowsheets. Vitals and neuro checks often live in grids. Check that the tool read the grid, not only the narrative notes.
Step 3: what to check by hand
Check by risk, not by habit. 3 groups cover most files:
- The window. Every entry inside a set period around the index event, such as the 24 hours before and 48 after a fall.
- A sample of the rest. Pick entries at random outside the window. Agree the share with the attorney before you start.
- Everything you rely on. Every entry your summary, your timeline exhibit or any opinion leans on, wherever it sits.
Log each check in a verification log: entry, page opened, result, correction. If the sample turns up errors, widen the check for that provider or page type. The scope checklist guide works through the arithmetic on an example file.
Verification log columns
Entry number | Date and time | Cited page (production number) | Opened? | Matches page? | Correction made | Initials
Step 4: the missing-records list
The chart often names records the production lacks: an outside imaging report, a transfer summary, a pharmacy log. Medrecords AI flags these references by checking the treatment history against the file. Either way, you build the list and send it to counsel early, because records requests take time.
A nurse consulting firm in the search results names the gap AI has here: it lacks the insight to see what is not in the chart but should be. A tool can list a CT report that a progress note mentions. It cannot tell you that a neuro check should have been charted after a fall and was not. That second list is yours.
Step 5: clinical analysis, set apart
Write the standard of care and causation discussion in your own words, in its own section, after the chronology. Do not let the tool draft it. Keep it visibly separate, so a reader can tell the record facts from your opinion.
Step 6: the deliverable
Convert every cite to the production page number before the chronology leaves your desk. A physician expert or opposing counsel can check a Bates cite in seconds. A tool page number means nothing without the tool.
| Cite format | Who can check it | Use it? |
|---|---|---|
| Tool page index ("p. 1,312") | Only someone with the tool open | No |
| Production page (DEF-001640) | Anyone with the production | Yes |
| Production range, hyperlinked to the PDF | Anyone, in 1 click | Yes, when the client accepts linked PDFs |
The examples in the table are made up to show the format. Add a method statement of 1 paragraph: which tool, what it did, what you checked and how. ABA Opinion 512 (US model guidance, read 2026-11-19) suggests that lawyers mark material produced by generative AI, so expect attorneys to ask for this.