NewMissing Records Detection: flags every visit, provider, and date missing from the file. See how →
Home›Help›Personal injury›Work through a fictional rear-end crash case
MEDRECORDS AI HELP

Work through a fictional rear-end crash case

This made-up case shows a rear-end crash run through Medrecords AI from start to finish. A nurse consultant sets up the case, checks the crash details, finds earlier neck care and a 6-week break in therapy, and writes the reports. Every person, clinic and date here is invented. The steps match the real app.

Last checked 2026-10-24·Written by Ahmed Jemaa
Help center contents26 articles

The case

Maria is a nurse consultant. She works for Tom, a lawyer. Their client is Dana.

On March 3, 2024, Dana was stopped at a light. A van hit the back of her car. She drove home. 2 days later she went to Lakeview Urgent Care with neck and low back pain.

Tom sends Maria the files he has. They hold the crash report, the urgent care chart, notes from Northgate Physical Therapy, an MRI report from Maple Imaging Center, and bills. Dana also tells Maria she saw a chiropractor once before the crash. Maria requests those records too.

Step 1: set up the case

  1. Maria picks Motor Vehicle Accident (MVA). It is a crash, so MVA fits better than Personal Injury.
  2. She uploads the files with Remove duplicate pages on. The urgent care chart came twice, once from the clinic and once from the insurer. The copies are removed, and their credits come back.

See set up a personal injury case, and when to pick MVA.

Step 2: confirm the crash details

The case says Needs confirming. Maria checks the Confirm case details window.

FieldWhat Maria picksWhy
Claimant's roleDriverThe crash report says so
Manner of collisionRear-end (front to rear)All records agree
Restraint useBeltedThe urgent care note says "belted driver"
Air bagNot deployedThe crash report says so
Transport from the scene / first careFirst care on a later dayFirst visit was March 5, 2024
Property damageModerateThe crash report's wording

She reads The collision as documented. It shows what the crash report and the first visit say, and who paid. It matches her picks. She checks the date of injury is March 3, 2024. She keeps the neck and low back as body parts. Then she presses Confirm and continue.

Step 3: read the timeline

Maria opens the Timeline tab and reads the days around March 3, 2024. She clicks each entry to see its source page.

  • March 5, 2024: urgent care. X-rays of the neck read "no acute finding".
  • March 12, 2024: therapy starts at Northgate, 2 visits a week.
  • May 10, 2024: last therapy visit before a break.
  • June 21, 2024: Dana sees an orthopedic doctor at Riverbend Orthopedics.
  • July 2, 2024: the MRI notes "mild degenerative disc changes" in the neck.

Step 4: find the gap and the reason

The month strip shows few events in late May and early June. Maria filters to Northgate and sees no visits from May 10 to June 21, 2024. That is about 6 weeks.

She checks the missing records list first. Nothing from Northgate is outstanding. So the break is real. She searches for "out of town". A note from June 21, 2024 says Dana was away caring for a sick parent. Maria adds a note to that entry. See find gaps in treatment.

Step 5: find the earlier neck care

The chiropractor records arrive. Maria adds them to the same case. They show 1 visit on January 8, 2024 for "neck stiffness".

She opens the Q&A pane and types in the box "Ask about this case": "List all care to the neck before March 3, 2024, with dates and page cites." The answer names the January visit and cites its page. She puts a "Pre-existing" flag on it.

Step 6: write the reports

Maria creates 3 reports in Report Studio:

  1. Pre-existing Condition Analysis. It lists the January visit under Documented Pre-incident Treatment. It quotes the MRI's "degenerative" wording under Degenerative and Age-related Findings.
  2. Mechanism-of-Injury Consistency Analysis. It shows each account of the crash and the 2-day wait before first care, with both dates.
  3. MVA Demand Package. Tom uses it as his starting draft.

She runs Run Verification and Cross-Examination on each. 1 claim shows as Unsupported. She fixes it from the source page. Each new report costs 100 credits.

What the app did not do

It did not say the crash caused the neck pain. It did not say whether the January visit matters. It did not put a value on the claim. Tom and his expert make those calls. See prepare a damages summary and a demand narrative.

For more on liens in a case like this, read our guide on medical liens and letters of protection.

Medrecords AI organizes and cites the records. Its output is not a medical or legal opinion and does not replace your expert.

Related help

Facts checked against the Medrecords AI app code on 2026-10-24.

Try it on a real file

Upload a case and see the page count and cost before you confirm.

Book a demo