Tutorial ID | T-29 |
Section | Reporting & Billing |
Title | Creating a High-Quality Chronology Section in the Report |
Subtitle | Build a chronology that's relevant, accurate, complete, consistently formatted, and clearly sourced from every record. |
Before You Begin
You have a chronology generated from AI workflows, with back-reference links to the source documents.
You know the date of the incident, so you can separate pre-event from post-event history.
What You Will Accomplish
By the end of this tutorial, every entry in your chronology will be relevant to the legal argument, accurate against its source document, complete, consistently formatted, and clearly marked as either an objective finding or a subjective complaint. You will also know how to catch entries drawn from handwritten or low-quality records that need extra scrutiny.
Why Does this Tutorial Matter
A chronology exists to give the reader a clear, reliable account of the events that matter to the case. That only works when every entry is relevant, accurate, complete, and consistently presented — so the reader can trust the timeline without re-verifying it against the underlying records themselves.
Get any of that wrong, and irrelevant entries bury the findings that matter, a misread date can reorder the entire sequence of treatment, a missing event leaves the medical history looking incomplete, and a chronology that blurs pre-event from post-event history — or objective findings from subjective complaints — weakens the causation argument the report is meant to support.
What to Do if Something Goes Wrong
The list below covers the most common problems when building a chronology section. Each entry follows the same pattern: what you'll notice, why it likely happened, a real example, and how to fix it.
Problem: The chronology includes entries that don't matter to the case, or entries that don't accurately reflect what the source document says.
Likely cause: Entries were added directly from AI extraction without checking each one for relevance to the legal argument or for accuracy against its source document.
Example: A chronology entry records a routine check-up unrelated to the accident, while a nearby entry gives the wrong date for a surgical procedure because of a misread record.
Fix:
Open the chronology section and read through every entry, flagging any that are irrelevant, such as routine check-ups or interactions unrelated to the accident.
Use AI Chat or Search to check an entry's relevance when it isn't immediately clear.
Open each source document through its back-reference link and verify the date, provider, facility, diagnosis, and procedure details exactly as they appear in the record.
Where source documents conflict, use AI Chat or Search to determine the more reliable record, correct the entry to match it, and note the discrepancy in a comment.
Remove the entries you flagged as irrelevant.
Read through the chronology as a whole to confirm it tells a clear, focused story with no gap introduced by the entries you removed.
Problem: The chronology skips a significant medical event, such as an initial emergency visit, a surgical intervention, or a documented change in condition.
Likely cause: The AI-generated chronology wasn't compared against the full set of case documents, so an event that a document supports never made it into the timeline.
Example: A specialist referral tied directly to the accident is never added to the chronology, even though the referral letter is part of the case file.
Fix:
Open the chronology section and read through every entry.
Open the Chronology tool and the full set of case documents, noting every significant medical event, including diagnoses, procedures, consultations, hospitalizations, and documented changes in condition.
Cross-reference each significant event against the chronology to confirm it appears and is placed at the correct point in the timeline.
For each missing event, locate the source document and add the entry manually, including the date, provider name, a concise description, and a back-reference link.
Read through the full chronology to confirm the timeline is complete with no gap suggesting an overlooked event.
Problem: A reader can't tell where the claimant's baseline medical history ends and the injury-related treatment begins.
Likely cause: Pre-event and post-event entries were left mixed together in a single list instead of being separated at the date of the incident.
Example: A pre-existing condition and a post-accident treatment appear side by side with no boundary, making it unclear which conditions existed before the incident.
Fix:
Open the Chronology tool and identify the date at which pre-event entries end and post-event entries begin.
If entries are mixed together, separate them into two distinct, clearly labeled sections, such as “Pre-accident events and conditions” and “Post-accident events and conditions.”
Confirm that every entry is placed in the correct section based on whether it occurred before or after the incident.
Read through both sections to confirm the transition is clear and the date of the incident is explicitly identified.
Review the chronology as a whole to confirm it presents a clear before-and-after picture that supports the causation argument.
Problem: Some chronology entries read as detailed clinical notes, others as brief informal notes, with no consistent structure between them.
Likely cause: Entries were written or extracted without a standard format defined for the chronology before it was reviewed.
Example: One entry reads “Patient seen 3/2, doing okay” while another follows a full date-provider-facility-description structure, making the chronology look unfinished.
Fix:
Before reviewing the chronology, define a standard entry format, such as date, provider name, facility, event description, and back-reference link.
Confirm the format with your team.
Open the chronology and read through every entry, flagging any that deviates from the standard format using Validating mode.
Rewrite each flagged entry using Editing mode to match the standard format without changing its factual content.
Confirm the level of clinical detail is consistent across entries, choosing one register rather than mixing formal and informal language.
Read through the full chronology as a continuous document to confirm every entry reads as part of the same document.
Problem: A chronology entry drawn from a handwritten or low-quality document is missing detail, or contains a date or number that looks off.
Likely cause: AI extraction works best against clean, machine-readable text, and a handwritten note or a poorly scanned page can be misread, skipped, or only partially captured.
Example: A transposed digit in a handwritten date shifts a procedure by a full year, reordering its place in the chronology.
Fix:
Before running AI workflows, quickly review the source documents and identify any that are handwritten, scanned at low resolution, or otherwise hard to read.
Run the AI workflows.
Treat every date and numeric value in the output as a mandatory verification point, checking each one character by character against the source through its back-reference link.
Apply extra scrutiny to any statement or number drawn from a low-quality or handwritten document.
Add a comment to any statement that's ambiguous or difficult to confirm — never let an uncertain number or date appear without one.
For a record that's partially illegible, record what can be confirmed, mark uncertain fields explicitly, such as “[date unclear — approximately March 2021],” and note in a comment that the source needs further clarification.
Once verification is complete, read through the entries drawn from low-quality records and evaluate their consistency.
Read through the complete chronology, including standard-quality entries, to confirm the full sequence is coherent and ready for review.
Problem: A subjective complaint, such as a pain rating, reads with the same authority as an objective clinical finding, such as an imaging result.
Likely cause: Entries weren't reviewed to identify whether each one records something a medical professional observed and documented, or something the claimant reported.
Example: An entry states “Herniated disc at L4-L5” with no indication of whether that's a confirmed imaging finding or the claimant's own description of their pain.
Fix:
Open the chronology and read through every entry, using back-reference links to determine whether it records an objective finding or a subjective complaint.
Add a comment to any entry where the distinction isn't clear.
Rewrite entries to reflect the correct distinction — clinical language for objective findings, and language that attributes the statement to the claimant for subjective complaints.
Confirm that objective findings and subjective complaints are each labeled correctly and not confused with one another.
Read through the full chronology to confirm the distinction is clear and consistent throughout.
Problem: The same medical event appears more than once in the chronology, worded slightly differently each time.
Likely cause: Different source documents referenced the same event, and the AI created a separate entry for each document instead of recognizing them as one occurrence.
Example: A hospital discharge summary and a specialist's notes both describe the same surgery, and the chronology lists it as two separate events.
Fix:
Read through the full chronology and flag any event that appears more than once, paying attention to entries that share a date, provider, or clinical event but are worded differently.
For each pair, open the source documents through their back-reference links, using Search or AI Chat to confirm whether both entries refer to the same event.
Consolidate duplicate entries into a single entry capturing the most complete and accurate version, with back-reference links to all source documents.
Remove the duplicate entries once the consolidated version is confirmed accurate and complete.
Read through the full chronology to confirm each event appears only once and no back-reference links were lost.
Tip Treat every date and number pulled from a handwritten or low-quality record as unverified until you've checked it character by character against the source — this is the single highest-risk step in building an accurate chronology. |
Summary
Every entry in the chronology is now relevant, accurate against its source, complete, consistently formatted, clearly separated into pre- and post-event history, labeled as objective or subjective, and free of duplicates — so the timeline the reader gets is one they can trust without re-verifying it themselves.