
Imagine a client sees an orthopedist on October 2, and the physician orders an MRI. The visit note is signed October 4. Imaging takes place October 9, the radiologist issues the report October 10, and the client returns October 16 to discuss the results.
That is one treatment sequence, but each date tells the legal team something different.
A useful medical chronology for personal injury should answer two questions: What happened in the treatment sequence, and does the firm’s current record set still reflect it?
For PI operations, the strongest chronologies also function as exception detectors. They make missing reports, later documentation, and unresolved retrieval work easier to identify before those issues get buried in the file.
The seven dates below are record dates tied to treatment and documentation. The incident date still anchors the case, while the date a provider fulfilled a records request serves as a separate retrieval benchmark.

A medical chronology is a chronological summary of a client’s relevant medical history. It connects treatment events to providers, important clinical developments, and the source records supporting each entry.
For personal injury teams, a medical record chronology turns a large record set into a clearer treatment sequence. History before the incident may also provide context when it affects later treatment. The attorney determines its legal significance.
A practical chronology commonly captures:
| Field | What It Answers |
| Date | When did the event occur? |
| Provider or facility | Who provided the care? |
| Encounter or record type | What happened? |
| Diagnosis, finding, treatment, or plan | What clinically changed or happened next? |
| Source page or Bates reference | Where can the team verify the entry? |
Billing records can provide another signal. A bill may corroborate a service date or identify an encounter missing from the clinical packet, but it does not replace the underlying treatment documentation.
Comparing the returned packet against the treatment history is also part of a broader medical record review process for personal injury cases.
A medical chronology organizes relevant events in time order and connects them to source records. A medical summary turns those records into a broader narrative.
Many firms use both. The chronology establishes the sequence and where supporting documentation appears. The summary explains the larger treatment history.
One treatment sequence can include separate dates for the encounter, an order, a procedure, a report, a signature, and a later correction.
The HL7 FHIR R5 ServiceRequest specification distinguishes when a request was signed from when the requested service should occur. The HL7 DiagnosticReport specification separately distinguishes the clinically relevant time of a diagnostic event from when a report version was issued.
For a case manager, the operational lesson is simpler: the service date shows when care happened. Other dates may show what should happen next and whether the firm’s records still reflect that sequence.
| Record Date | What It Tells the Legal Team |
| 1. Date of service or encounter | When care occurred |
| 2. Order or referral date | When another service or next step was requested |
| 3. Procedure, test, or imaging date | When a separately ordered service occurred |
| 4. Report or result issued date | When that report version was issued |
| 5. Note signature or authentication date | When documentation was signed or authenticated |
| 6. Addendum or correction date | When earlier documentation changed |
| 7. Discharge or treatment end date | When a defined episode of care ended |
Do not add seven columns to every chronology. Preserve another date when it changes what the team understands about the record.

Start with when care occurred.
That may be an emergency department visit, therapy session, specialist appointment, procedure, or hospital stay. In the opening example, the orthopedic encounter occurred October 2 even though the provider signed the note two days later.
A service date can also expose an omission. If a later note references an intervening visit but no corresponding record appears in the packet, the team has something specific to investigate. A gap in treatment can reflect several different record or care scenarios, so the missing event should be verified rather than assumed.
An order shows what the provider expected to happen next.
If the October 2 orthopedic note orders an MRI, that event becomes a checkpoint later in the medical chronology for personal injury review.
The order does not establish that the service occurred. If no study follows, the team may need to determine whether the imaging record is missing, the plan changed, or the service never took place.
This date matters when an ordered service occurs separately from the encounter that generated the order.
The October 2 MRI order becomes a completed event when the imaging center performs the study October 9. The file can still contain only part of that sequence. A firm may have the order without the study or the report without the underlying images.
A broader review for incomplete medical records may also need to account for billing records, specialist documentation, and other components of the case file.
The study date and report date can differ.
Consider the opening example:
| Event | Date |
| MRI performed | October 9 |
| Provider fulfilled the firm’s request | October 9 |
| Radiologist issued the report | October 10 |
The study and fulfillment occurred on the same date. The radiology report was issued the next day.
That does not establish that the October 9 production was deficient. It tells the case manager that a relevant report entered the documentation sequence after the firm’s current production and may need to be reconciled.
A treatment event and the signing of its documentation can happen on different dates.
The client received care October 2, while the provider signed the note October 4. Keep October 2 as the treatment event and preserve October 4 when that distinction matters.
The CMS Medicare Program Integrity Manual treats signature dating separately from determining when a service was performed or ordered in Medicare medical review.
For a PI chronology, the practical point is that a signature date should not automatically replace the date of service.
A later version of a note is not always an ordinary duplicate.
CMS Medicare medical review guidance also addresses amendments, corrections, and delayed entries. If an October 2 orthopedic note later contains an October 20 addendum, keep October 2 as the treatment date and record the October 20 change separately.
The case manager makes the newer documentation visible. The attorney determines whether the change matters legally.
A defined treatment endpoint gives the chronology another checkpoint.
Suppose a PT file stops after 18 visits, but a later orthopedic note says the client completed therapy. If the packet contains no PT discharge note, the team now has a specific record to verify rather than assuming treatment ended when the notes stopped.
The same MRI sequence can appear in a medical chronology like this. The Bates references are illustrative.
| Date | Provider | Event | Key Detail | Source |
| Oct. 2 | Example Orthopedics | Follow-up visit | Lumbar MRI ordered | Bates 451-453 |
| Oct. 4 | Example Orthopedics | Signature | Provider signed Oct. 2 note | Bates 451-453 |
| Oct. 9 | Example Imaging | Lumbar MRI | Imaging center completed study | Bates 512-514 |
| Oct. 10 | Example Imaging | Radiology report | Radiologist issued report | Bates 515-517 |
| Oct. 16 | Example Orthopedics | Follow-up visit | Provider reviewed MRI | Bates 540-542 |
Now compare that sequence with the retrieval timeline. The provider fulfilled the firm’s existing request October 9.
Because the October 10 report entered the documentation sequence after fulfillment, it becomes the item to reconcile. From there, the team can check whether the report already exists elsewhere in the file and decide whether another retrieval request is needed.
An exception does not automatically require another request. First determine what the firm already has.
That is where the chronology becomes operationally useful. It helps keep unresolved retrieval work from disappearing inside the review process.
Start with the core entry: date of service, provider, event, key clinical information, and source. Add another record date only when it changes what the file tells you.
For each important event, ask:
The goal is a medical chronology for personal injury that helps the team identify exceptions and act on them.
Update the chronology when treatment progresses or relevant documentation changes.
The provider fulfillment date is useful even though it is not one of the seven medical record dates. It tells the team when the provider produced the firm’s current record set.
For example, a request may cover records through October 15 and be fulfilled that day. An MRI performed October 14 could still have a report issued October 16.
That later report does not establish that the October 15 production was incomplete. It shows why a record set can become outdated without another treatment encounter.
Compare treatment and documentation dates with the fulfillment date and ask: What existed when the provider produced the current record set, and what has changed since?

A medical chronology may reveal a report issued after the last pull, a later addendum, or a completed service without its supporting records. Your team should not have to move that exception into another spreadsheet and begin another round of provider calls.
With CaseBinder, your team can submit retrieval requests through a centralized workflow and track their status online. Our retrieval experts handle provider follow-up and escalation so unresolved requests keep moving without putting the chase back on your case managers.
The chronology tells your team what changed. CaseBinder gives you a place to turn that exception into a tracked retrieval request and follow it through delivery.
Schedule a CaseBinder workflow review
A medical chronology is a chronological summary of relevant treatment events tied to the provider and supporting source record. It helps the legal team follow the treatment sequence and identify missing events, later documentation, and other exceptions.
Include the service date, provider, event type, key clinical information, and source reference. Add order, procedure, report, signature, correction, or treatment end dates when they change how the team understands the sequence.
Not necessarily. The service date shows when care occurred. The signature date records a separate documentation action. Preserve both when that distinction affects the chronology.
There is no single schedule for every case. Update a medical chronology for personal injury when treatment progresses or new documentation changes what the firm’s current record set shows.