Published April 1, 2026

By NexLaw Research Team

How to Build a Medical Chronology for a PI Case (2026)

How to Build a Medical Chronology for a PI Case (2026)

The Short Answer: A medical chronology is a date-ordered timeline of every medically relevant event in a personal injury case, from the ER visit to the final evaluation. Each entry cites the page in the record it came from, so the attorney can verify it quickly. A strong chronology also flags treatment gaps and pre-existing conditions early, so defense arguments are addressed before deposition rather than during it.

Why Medical Chronologies Matter in PI Cases

Every personal injury case depends on the medical record. Causation, damages, pain and suffering and future care costs are all documented somewhere across hundreds or thousands of pages of physician notes, radiology reports, specialist referrals and pharmacy histories.

For solo PI attorneys and small firms with heavy caseloads, building those chronologies by hand is one of the largest non-billable time commitments in the practice. It is slow, easy to miss entries in, and hard to update when new records arrive mid-case. This guide covers what a strong PI medical chronology contains, how to structure it, where manual review breaks down, and how AI tools can support the process.

What a Medical Chronology Contains

A medical chronology is not a summary. A summary says what happened at a high level. A chronology records when each event happened, in what order, with a source citation so any fact can be checked. That matters because the sequence of events is what establishes causation, shows continuity of care and supports the damages argument.

What Each Entry Should Include

Field What to capture Why it matters
Date Exact date Establishes the sequence and the causation chain
Provider and facility Full name and specialty Shows continuity and an appropriate referral pattern
Encounter type ER visit, follow-up, imaging, PT, surgery Shows treatment necessity and progression
Chief complaint What the patient reported Links ongoing symptoms to the original injury
Findings and diagnosis Objective findings, ICD codes where available Anchors damages to documented medical evidence
Treatment ordered Medications, procedures, referrals, restrictions Shows intensity of care and future cost exposure
Source page Page or Bates number in the original record Required for verification, deposition and trial

What a Strong Chronology Also Flags

  • Treatment gaps: periods where the client stopped seeking care. The defense will find these. Your chronology should explain them first.
  • Inconsistencies between providers: where a treating physician’s notes contradict a specialist’s findings.
  • Pre-existing conditions: and the documented baseline that rebuts alternative causation arguments.
  • Objective injury markers: such as MRI findings, surgical reports and EMG results.
  • Future care recommendations: any provider note referring to ongoing or likely future treatment.

The 7 Record Types Every PI Chronology Should Include

Cases with strong damages arguments are usually built on a complete record set, not just hospital and physician notes.

  1. Emergency room records. The first documented account of the injury mechanism and initial findings. The ER note is often the most important single document in the file.
  2. Primary care records, before and after the injury. Pre-injury records establish the baseline needed to rebut arguments about prior conditions.
  3. Specialist records, such as orthopedics, neurology, pain management and surgery, which usually hold the strongest objective documentation.
  4. Imaging and diagnostic studies: X-ray, MRI, CT and EMG/NCV reports. These are objective anchors that defense experts find harder to dispute.
  5. Physical therapy and rehabilitation records, documenting functional limits, recovery and ongoing impairment.
  6. Pharmacy records. Medication history shows pain management patterns and duration of treatment, and feeds the cost calculation.
  7. Mental health records where relevant, including documentation of emotional distress or PTSD after a traumatic injury.
Practice note: Request records going back several years before the incident, not just after it. The defense will order them regardless. Finding a prior condition in your own review, and addressing it in your chronology, is a stronger position than meeting it for the first time at deposition.

Sample Medical Chronology: Auto Accident Case

The sample below is fictional and for illustration only.

Date Provider and specialty Encounter type Key findings Treatment and orders Source
03/12/2025 Memorial Regional ER, Emergency Medicine Initial ER visit Cervical tenderness, limited ROM, GCS 15. Neck and lower back pain reported at 7/10. Cervical collar. X-ray ordered. Flexeril 10mg, Ibuprofen 800mg. Discharged with follow-up instructions. pp. 1-8
03/12/2025 Dr. R. Chen, Radiology X-ray interpretation Cervical: loss of lordosis, no fracture. Lumbar: mild disc space narrowing at L4-L5. MRI recommended if symptoms persist beyond two weeks. pp. 9-12
03/26/2025 Dr. A. Martinez, Orthopedic Surgery First specialist consult (14-day gap, consistent with ER discharge instructions) Cervical pain 7/10, lumbar pain 6/10. Positive straight leg raise on left. Reduced lumbar flexion. Lumbar MRI ordered. Meloxicam 15mg. PT referral 3x per week. pp. 13-18
04/02/2025 Regional Imaging, Radiology Lumbar MRI Broad-based disc herniation at L4-L5 with mild left foraminal narrowing. No cord compression. Results forwarded to Dr. Martinez. pp. 19-22
04/09 to 06/18/2025 Peak Performance PT, Physical Therapy 22 sessions over 10 weeks Initial cervical flexion 30 degrees (normal 50), 42 degrees by session 18. Pain from 7/10 to 4/10. Therapeutic exercises, manual therapy, modalities. pp. 27-72
06/25/2025 Dr. A. Martinez, Orthopedic Surgery Re-evaluation Cervical 40% improved. Lumbar pain persistent at 5/10. Left leg numbness continues. Referred to pain management for epidural evaluation. pp. 73-76
07/22/2025 Dr. K. Patel, Pain Management Epidural steroid injection Pre-procedure VAS 6/10. Positive femoral nerve stretch test. L4-L5 transforaminal ESI under fluoroscopy. Follow-up in two weeks. pp. 81-85
08/05/2025 Dr. K. Patel, Pain Management Post-injection follow-up 50% pain reduction reported. VAS 3/10. Left leg numbness resolved. Second injection if symptoms return. Continue Gabapentin. pp. 86-88
09/15/2025 Dr. A. Martinez, Orthopedic Surgery Final evaluation and MMI Cervical near baseline. Lumbar pain 2/10 at rest, 4/10 with prolonged sitting. Possible repeat injection annually. Released to full duty with ergonomic accommodations. pp. 89-94
Best practice: Each gap annotation should give the reason for the gap and a source reference, not just a blank date range. In the sample, the 14-day gap between the ER visit and the orthopedic consult is annotated as consistent with the ER discharge instructions, which reduces deposition exposure on that point.

Pre-Existing Conditions, Causation and Treatment Gaps

These three areas are where PI chronologies most often fail to support the case theory, and where defense counsel looks first. All three are better handled with documentation up front than with explanations at deposition.

Causation Documentation

Consideration What to look for in the record Where it usually appears
Temporal relationship Injury appearing after the incident with reasonable timing ER visit date vs. incident date; close timing generally supports causation
Biological plausibility Injury type consistent with the incident mechanism ER mechanism notes and treating physicians’ biomechanical notes
Clinical consistency Symptom pattern consistent with the injury over time Complaints across providers, without unexplained symptom changes
Diagnostic confirmation Objective findings supporting the clinical picture MRI, CT, X-ray, EMG/NCV results rather than pain reports alone
Alternative causes addressed Prior conditions or other events noted and distinguished Pre-injury baseline entries and provider statements tying symptoms to the incident

Pre-Existing Conditions: A Three-Phase Approach

A well-structured chronology handles pre-existing conditions by showing what existed before the incident, what changed after, and how those changes link to the defendant’s conduct.

  1. Pre-Accident Baseline

    The last medical visit before the incident, stable or negative findings, functional abilities and low treatment frequency. This shows what normal looked like before the injury.

  2. Post-Accident Change

    Objective findings that separate the current condition from the baseline, the timing connection to the incident, and causation language from treating physicians.

  3. Permanency and Ongoing Impact

    MMI assessments, expert opinions separating accident-related changes from natural progression, and future care projections that support the damages calculation.

Documenting Treatment Gaps

Each treatment gap annotation should include three things: the length of the gap, with source records on both sides; the reason for the gap, supported by documents such as an insurance denial or scheduling records rather than assumption; and any clinical context showing whether symptoms were reported elsewhere during that period.

A ten-week gap with no explanation gives the defense an opening. The same gap with a documented insurance authorization denial and a primary care visit showing continuing symptoms closes it.

Where Manual Chronology Building Breaks Down

Four problems come up again and again in practices that build chronologies by hand:

  • Volume and attention. Manual review is sequential, and attention fades across large files. Notes about prior injuries buried late in a record set are the entries most likely to be missed and to surface later at deposition.
  • Different provider formats. Providers document differently, from free-form dictation to checkboxes to coded entries. Pulling consistent information from all of them by hand takes time and introduces inconsistency.
  • Late gap discovery. Manual review tends to surface treatment gaps during deposition preparation rather than at case setup, which leaves little time to investigate the reason.
  • Updating as records arrive. Fitting new records into an existing manual chronology, checking them against existing entries and updating the damages total takes time with every new batch.

How AI Tools Support the Chronology Workflow

AI medical chronology tools handle the extraction, organization and formatting, so the legal team can focus on verification, legal context and case strategy. They do not replace attorney review.

  • Processing the full record set with the same level of attention throughout.
  • Flagging periods with no documented treatment, so gaps are visible from case setup.
  • Linking each entry to its source page, so facts can be checked in seconds.
  • Adding new records to the existing timeline when more batches arrive, without starting over.

AI output can be more consistent than fully manual review on large record sets, but human review remains essential. Clinical nuance, causation language and the legal significance of specific entries need attorney judgment. The right approach treats AI output as a structured first draft that the case team reviews and annotates.

How ChronoVault Supports PI Medical Chronology Work

ChronoVault is NexLaw’s case timeline tool, built for litigators. The workflow runs from the first record upload to demand preparation and trial.

  1. Upload Records

    Upload the medical records to a Matter, from any provider.

  2. AI Extracts and Organizes

    ChronoVault reads the full record set and identifies dates, providers, encounters, diagnoses, treatments, medications, imaging and referrals. It places events in date order and shows, for each fact, what corroborates it, what contradicts it and what is missing.

  3. Review Flagged Entries

    The attorney reviews flagged items, adds legal context and annotates entries that matter most to the case theory.

  4. Export

    The finished chronology is exported with source page references on every entry, ready for demand preparation, deposition outlines, expert review or trial.

NexLaw also covers legal research through NeXa and case strategy through TrialPrep, keeping the PI workflow in one platform. See how NexLaw builds AI medical chronologies, medical billing summaries and demand packages for personal injury firms.

Frequently Asked Questions

What should be included in a medical chronology for a personal injury case?

Each entry should include the date, provider name and specialty, encounter type, the patient’s chief complaint, objective findings, treatment ordered and the source page in the original record. The ABA Law Technology Today guide on AI prompts for PI lawyers covers how attorneys use AI to structure and review these entries.

How long does it take to build a medical chronology?

It depends on the number of pages and providers. A moderately complex PI case can take days of manual work. With AI handling the first extraction and organization, the legal team’s time goes to reviewing and annotating the output instead, though the exact time depends on case complexity and the team’s review standard.

Can AI miss important medical information in a chronology?

Yes. AI extraction reduces but does not remove the risk of missing information, and clinical nuance sometimes needs human interpretation. Treat AI output as a structured first draft: review flagged entries, check source pages and add legal context. Attorney review is essential whichever tool you use.

Is AI medical chronology software HIPAA compliant?

It depends on the tool. HIPAA compliance requires a signed Business Associate Agreement from the vendor, documented data handling policies and security controls that protect PHI. The HIPAA Journal compliance checklist is a useful reference for evaluating vendor claims. Always confirm with the vendor before uploading client medical records.

What are treatment gaps and why do they matter?

A treatment gap is any period after the injury when the client did not seek or receive care. Defense counsel will find these gaps and may argue the injury was not serious, or that something else caused the condition. Finding gaps when the chronology is first built, rather than at deposition preparation, gives the case team time to investigate and document the reason, such as an insurance issue, a scheduling delay or a financial barrier.

What is the difference between a medical chronology and a medical summary?

A medical summary is a high-level narrative of the client’s medical history. A medical chronology is a structured, date-ordered timeline with a source citation for each entry. Chronologies are used for case evaluation, demands, deposition outlines and trial. Summaries are for readers who need an overview rather than a citable record.

What to Verify Before Using an AI Tool for Medical Records

Medical records contain confidential client health information. Before using any AI tool for chronology work, check the following:

Criteria What to check Why it matters
HIPAA compliance Signed BAA, documented data handling policy Medical records are PHI. Non-compliant tools create liability.
SOC 2 Type II certification Independent third-party audit, renewed annually Confirms security controls are in place and working.
Model training policy Whether client documents are used to train AI models Protects work product and attorney-client privilege.
Source citations Whether each entry links to a specific page in the original record Required for verification at deposition and trial.
Export formats The formats your team uses Needs to fit your existing case workflow.
NexLaw holds SOC 2 Type II and ISO 27001 certification and is HIPAA and GDPR compliant. Check current certification status on the NexLaw security page before uploading client data.
Book a Demo Call
Book a Demo Call5 Days Complimentary Trial
Request Trial Access
Request Trial Access

Enjoying this post?

Subscribe to our newsletter to get the latest updates and insights.

© 2026 NEXLAW INC.

AI Legal Assistant | All Rights Reserved.

GDPR compliant data protection and privacy standardsGDPR Compliant
HIPAA compliant security for sensitive legal and health dataHIPAA Compliant
SOC 2 Type II certified security and compliance controlsSOC 2 Type II Certified

NexLaw encrypts client data at rest with AES-256. See our Security page and Trust Center for how NexLaw protects client data.

NEXLAW AI