Free account 2:33Deduplication
How repeated pages come out before anyone reads them, what each label means, and how to compare a removed page with the one that was kept.
The page-level method for medical malpractice teams
Match every page the defense produces against the records you got before suit, then classify each difference as missing, added, changed or reformatted.
They are different reports run on the same database, with different scope and templates; Medrecords AI compares them.
Reconciling a defense record production means matching every document the defense produces in discovery against the records you obtained before suit, then classifying each difference as missing, added, changed or reformatted. Most differences come from release scope, print dates and EHR print templates. Missing documents go in a deficiency letter. Changed content gets a side-by-side comparison and, when the timing is unexplained, a narrow audit trail request.
You got the chart before suit. Now the defense has produced it again: 435 pages longer, in a different order, under different headers, with an addendum you have never seen. Reconciliation is the work of proving which of those differences are print settings and which are evidence, and doing it early enough that the answer shapes discovery instead of arriving after the depositions.
For plaintiff medical malpractice attorneys, paralegals and legal nurse consultants holding 2 sets of the same chart. You walk away with the reasons the sets differ, a 4-step reconciliation method, a worked crosswalk, a reconciliation log, a deficiency letter and a narrow audit trail request.
An electronic health record has no pages. It is a database, and every copy of a chart is a report someone ran on a given day, with a given template, against a given scope. Your pre-suit set is 1 such report. The defense production is another, run a year later by different people for a different purpose. They will not match page for page.
That explains most of what you will find. The rest is why the work is worth doing: an addendum written after the chart was requested, a flowsheet row that was not there before, a discharge summary your set has and theirs lacks. Cases turn on those pages.
| Cause | What it looks like | Usually innocent? |
|---|---|---|
| Release scope | The authorization named a date range or "complete record"; the release desk printed what its policy calls the record. Your request for production asked for something broader or narrower | Yes |
| Legal health record vs designated record set | The release desk printed the legal health record. Discovery reaches source data, orders and device output | Yes |
| Print date | The pre-suit copy predates signed dictations, final results and late entries. Footers show different print dates | Yes, until the content says otherwise |
| EHR print template | A 2-page medication summary against a 27-page administration record; a flowsheet filtered to scheduled vitals | Yes |
| Later addenda and corrections | A dated addendum in 1 set only; a lab value flagged "corrected" | Depends on timing and label |
| Source systems outside the chart | Fetal monitor strips, anesthesia data, telemetry, pulse oximetry trends, pump logs. Often in neither set | Yes, but the gap still needs filling |
| Withheld or redacted material | Bates gaps, slip sheets, redactions, peer review material claimed as privileged | Depends on the claim and the log |
| Change to the record itself | Different text under the same signature time, with no label | No |
This distinction explains more mismatches than any other, and most litigators have never heard of it. HIPAA defines the designated record set broadly: it covers "the medical records and billing records about individuals maintained by or for a covered health care provider" and anything "used, in whole or in part, by or for the covered entity to make decisions about individuals" (45 CFR 164.501). The legal health record is a narrower set the facility defines for itself in policy. AHIMA, the health information management profession's body, puts it this way:
"The legal health record is a subset of the entire patient database. The elements that constitute an organization's legal health record vary depending on how the organization defines it."
The same brief says the legal health record "does not affect the discoverability of other information held by the organization", and that "audit trails, metadata, and psychotherapy notes are not included" in either record set. In plain terms: the release desk hands out the legal health record, discovery can reach more, and the audit trail sits outside both unless someone asks for it. AHIMA also lists electronic fetal monitoring strips, diagnostic images and video among the things a facility has to decide whether to include. Many decide not to print them on a routine release.
The notes barely changed. The flowsheets and medication administration record grew from 96 pages to 431. That is where the reconciliation work, and usually the case, lives.
The 2 sets arrive through different legal doors, and each door shapes what comes through it. Knowing which door your pre-suit set used tells you what it was ever going to contain.
The discovery door is the widest, and it is also the one you control. The pre-suit door is narrower but has 1 property nothing else has: it was opened before anyone at the facility was defending a claim. That is why the pre-suit set is the baseline for the whole reconciliation, even when it is the smaller set.
Most reconciliation pain is set up by the request for production, weeks before the documents arrive. If the request does not name a form, the rules pick one for you. The federal text:
"(i) A party must produce documents as they are kept in the usual course of business or must organize and label them to correspond to the categories in the request; (ii) If a request does not specify a form for producing electronically stored information, a party must produce it in a form or forms in which it is ordinarily maintained or in a reasonably usable form or forms; and (iii) A party need not produce the same electronically stored information in more than one form."
For a filing cabinet, "as kept" means in the folders, in order. An EHR keeps data in tables, and the document you receive is a report generated for the production, so "as kept in the usual course of business" tells you little. Our view: always ask in writing which report or print template generated the production, on what date, with what filters. That answer explains more differences than any other.
The 2006 committee note to Rule 34 limits what a producing party can do with the reasonably usable option:
"The option to produce in a reasonably usable form does not mean that a responding party is free to convert electronically stored information from the form in which it is ordinarily maintained to a different form that makes it more difficult or burdensome for the requesting party to use the information efficiently in the litigation."
The same note says information kept in a searchable form "should not be produced in a form that removes or significantly degrades this feature." An EHR is searchable, so image-only scans with no text layer and no index are a fair meet and confer topic under that note.
| Rule | What it says | Use in reconciliation |
|---|---|---|
| FRCP 34(b)(1)(C) | A request "may specify the form or forms in which electronically stored information is to be produced" | Ask for searchable PDF, 1 file per document, plus native or CSV for flowsheets, MAR and device data |
| FRCP 34(b)(2)(B) | Production of copies must be completed by the inspection time in the request or "another reasonable time specified in the response" | A rolling production needs an end date; the crosswalk is not final until then |
| FRCP 34(b)(2)(C) | "An objection must state whether any responsive materials are being withheld on the basis of that objection" | Check every missing row against the objections |
| FRCP 34(b)(2)(D) | A party objecting to the requested form, or answering a request that named none, must state the form it will use | A production in a form other than the one stated is a meet and confer item |
| FRCP 26(b)(5)(A) | A party withholding privileged material must "expressly make the claim" and describe what is withheld | Peer review and incident material pulled from the chart belongs on a log |
| FRCP 26(e)(1)(A) | Supplement "in a timely manner" when a response is "incomplete or incorrect" in a material respect | An addendum written after production raises a supplementation question |
| Cal. CCP 2031.280(a) | Documents "shall be identified with the specific request number to which the documents respond" | In California, labeling by request is required. Check your state's analog |
The 2015 committee note to Rule 34 draws the line on withholding: no detailed log of withheld documents is required, but the producing party must "alert other parties to the fact that documents have been withheld." Privilege claims are logged separately under Rule 26(b)(5)(A).
The biggest decision in a reconciliation is what you compare. Compare pages, and 2 print jobs generate hundreds of false differences: a note that ran 3 pages in 1 template runs 4 in another, and every later page shifts. Compare documents instead: 1 note, 1 report, 1 flowsheet for 1 date range, 1 order, 1 result. Match documents, then compare the pages inside each pair.
Every document in either set ends up with exactly 1 status. We use 5, plus a sixth for things neither side produced:
Most errors in reconciliation are classification errors: a reviewer calls a reformatted page "changed" and burns a meet and confer on a font. Hold this line firmly.
Log it, do not escalate it
Goes on the change list with both cites
1 edge case deserves a rule of its own. When a flowsheet in 1 set shows rows the other lacks, it can be a display filter (reformatted) or a row filed later (changed). You cannot tell from the page. Classify it as changed until someone proves it was a filter, because the opposite mistake can bury the one finding the case needs.
This is the method a paralegal or legal nurse consultant can run with 2 PDFs and a spreadsheet. It is slow on a 1,000-page chart, and it is still the method you want to be able to describe under oath. Before step 1, freeze both sets: keep untouched copies as received, with cover letters, certifications and receipt dates, stamp the pre-suit set with its own prefix (see what is Bates numbering), and record a hash of each file. Never merge or deduplicate the 2 sets before you compare them. A deduplication pass treats 2 versions of the same note as duplicates, and the version it drops may be the evidence.
Steps 1 and 2 take most of the hours. Step 3 is where judgment lives. Step 4 is what the attorney reads.
You will not read 1,000 matched pairs line by line. Our order: every document within 24 hours of the event, every document the defense expert cites, every addendum or corrected result in either set, and the flowsheets and MAR for the event window. Skim the rest for signature block and page count only, and write the scope you chose at the top of the log.
1 row per document. Paste into a spreadsheet; each line below is a column. Keep 1 log per matter and add rows with each supplemental production instead of starting over.
RECONCILIATION LOG Matter: [CASE NAME / FILE NO.] Set A (pre-suit): [SOURCE], received [DATE], [PAGES] pages, [PREFIX] [FIRST] to [LAST], print date [DATE], hash [VALUE] Set B (defense): [PRODUCING PARTY], received [DATE], [PAGES] pages, [PREFIX] [FIRST] to [LAST], response served [DATE], hash [VALUE] Scope of line-by-line comparison: [e.g. all documents 03/03 00:00 to 03/05 00:00; all cited by defense expert; all addenda] COLUMNS 1 Row # 2 Document type [H&P / progress note / flowsheet / MAR / order / result / report] 3 Date and time of service [MM/DD/YYYY HH:MM] 4 Author and role [NAME, ROLE] (cosigner if any) 5 Encounter / note / order ID [ID as printed, or "none shown"] 6 Set A pages [PL 000000 to PL 000000] or "none" 7 Set A print date / signed [DATE] / [DATE TIME] 8 Set B pages [DEF 000000 to DEF 000000] or "none" 9 Set B print date / signed [DATE] / [DATE TIME] 10 Status MATCH / REFORMATTED / CHANGED / ADDED / MISSING / ABSENT BOTH 11 What differs "[exact words in A]" vs "[exact words in B]" 12 Evidence it should exist [for MISSING and ABSENT BOTH: page that implies it] 13 Within request? [RFP no. X] / [not requested] 14 Objection or log entry [none / objection text / privilege log line] 15 Next step [none / add to chronology / deficiency letter / version comparison / audit trail request] 16 Owner and due date [NAME, DATE] 17 Closed [DATE, how resolved, Bates of any new production]
The order page is in the defense set only.
DEF 000298 to DEF 000299Defense flowsheet: respiratory rate 12, SpO2 94%, sedation score 2. The pre-suit flowsheet jumps from 00:00 to the event.
DEF 000405; PL 000143Respiratory rate 6, SpO2 72%, rapid response called. Same text in both sets.
PL 000152; DEF 000418Under a 04/10 authorization for the "complete medical record". 612 pages, stamped PL 000001 to PL 000612.
Page footers; intake logThe attending adds a dated addendum to the 03/04 surgery note, 2 months after the records request.
DEF 000432"As kept in the usual course of business". Objects to monitor data as not maintained. Silent on withholding.
Defendant's response1,047 pages, DEF 000001 to DEF 001047, 1 PDF, no index, no monitor data, no discharge summary.
Production cover letterAnything written after 05/19/2025 can only appear in the defense set. Print dates are the first thing you log.
The paralegal indexes 188 pre-suit documents and 241 defense documents. Matching pairs 171, leaving 17 pre-suit and 70 defense rows unpaired. The full log has 258 rows; 12 are shown.
3 of the 12 rows need action beyond logging: the changed flowsheet, the changed surgery note and the missing discharge summary. The monitor data needs a fight over "not maintained".
The surgery note is the easier of the 2 to read, because the change announces itself. Here are the 2 versions:
Proper in form: labeled, dated, signed, original intact. Notable in timing: written after the records request, and it relies on a flowsheet row the pre-suit print does not show.
The flowsheet is harder. The pre-suit page PL 000143 shows rows at 20:00 and 00:00, then the event. The defense page DEF 000405 shows the same 2 rows plus 02:00. Neither page shows a filed time. Either the pre-suit view showed scheduled vitals only and the 02:00 row was a PRN check all along, or the row was filed after 05/19/2025. The pages cannot settle it, and the addendum cites that row, so it needs settling.
Before any letter goes out, reconcile the page counts so nobody can say a range was skipped. Every page in each set has to land somewhere.
The status tells you what kind of difference you found. It does not tell you what it means. Most differences have an innocent explanation, and the job is to rule those out in order, cheapest first, before anyone uses the word "altered".
Most differences stop at step 1 or 3. That is the method working, not failing: every stopped row is one you will never have to defend.
| Finding | Rule out first | Worry when | Next step |
|---|---|---|---|
| Added pages in defense set | Detail print, broader request, orders, source data | An added document near the event that nothing else mentions | Add to chronology with DEF cite |
| Missing pages in defense set | Outside the request, filed under another encounter | Event-window document, requested, no objection covering it | Deficiency letter with the pre-suit cite |
| Absent from both | Kept in a device or departmental system, purged on schedule | An order for monitoring, no data, and a "not maintained" objection | Deficiency letter naming the system; preservation letter |
| Addendum in 1 version only | Written after the earlier print; template hid addenda | Written after the records request, about the disputed hours | Version comparison; narrow audit trail request |
| Flowsheet rows in 1 version only | Display filter hiding PRN rows | Event-window rows cited by a later addendum or the defense expert | Flowsheet with filed times; audit trail for those rows |
| Different text, same signature time, no label | Print shows only the current revision | Always | Audit trail and every saved revision; see the altered medical records guide |
In the chapter 6 case, the anesthesia graph, orders and full MAR are added pages the standard template left out: chronology, DEF cites. The discharge summary is missing, requested and unobjected: deficiency letter. The monitor data is absent from both: deficiency letter, citing the order at DEF 000298. The addendum passes the label test and fails the timing test, and the row it relies on cannot be dated from the page. Those 2 go to chapter 9.
The deficiency letter is where the crosswalk pays for itself. A letter that says "your production is incomplete, produce the complete chart" invites a reply that says "we produced the chart as kept". A letter that says "the discharge summary dated 03/28/2025, which we hold at PL 000590 to PL 000594, is not in DEF 000001 to DEF 001047 and is responsive to request no. 1" leaves no room for that reply.
In federal court you cannot move to compel without trying to resolve the dispute first:
"The motion must include a certification that the movant has in good faith conferred or attempted to confer with the person or party failing to make disclosure or discovery in an effort to obtain it without court action."
Rule 37(a)(4) adds that "an evasive or incomplete disclosure, answer, or response must be treated as a failure to disclose, answer, or respond," and Rule 37(a)(5)(A) makes expenses, including attorney's fees, the default when a motion to compel is granted or the discovery arrives after it is filed (FRCP 37).
State practice differs. In California, a motion to compel a further response to a demand for production must be accompanied by a meet and confer declaration under Code of Civil Procedure 2016.040, and notice of the motion must be given within 45 days of service of the verified response, or of a supplemental verified response, unless the parties agree in writing to a later date; otherwise the right to compel is waived (CCP 2031.310(b) and (c)). That clock runs from the response, not from the day you finish reconciling, so scope the work to fit it or get a written extension early.
The template below has 1 numbered item per crosswalk row that needs action, then the withholding, privilege and form questions, then dates. Changed documents stay out of it; they belong in the narrower request in chapter 9.
A starting draft for counsel to adapt to the court, the local rules and the facts. It assumes you have finished at least the event window of the reconciliation log.
[FIRM LETTERHEAD]
[DATE]
VIA EMAIL
[DEFENSE COUNSEL NAME]
[FIRM, ADDRESS]
Re: [CASE CAPTION], [CASE NO.]
Deficiencies in [DEFENDANT]'s production of [DATE], [PREFIX] [FIRST] to [LAST]
Dear [NAME]:
We have compared [DEFENDANT]'s production against the records of
[PATIENT] that we obtained before suit ([PREFIX] [FIRST] to [LAST],
printed by [FACILITY] on [PRINT DATE]). We write to meet and confer
about the items below, which are responsive to Plaintiff's [FIRST]
Request for Production served [DATE] and are not in the production.
A. Documents we hold that were not produced
1. [Document type], dated [DATE TIME], author [NAME/ROLE].
Responsive to Request No. [X]. We hold it at [PL RANGE].
No objection in your response of [DATE] covers it.
2. [...]
B. Records the chart shows exist, produced by neither side
3. [Data/system, e.g. continuous pulse oximetry data, DATE RANGE].
[DEF PAGE] shows [the order / the reference] for it.
Your response objects that it is "[QUOTE]". Please identify the
system that captured it, its retention setting, and whether it
still exists, and produce it in native or CSV form with any
legend needed to read it.
C. Withholding and privilege
4. For each objection in your response, please state whether any
responsive material is being withheld on the basis of that
objection (Fed. R. Civ. P. 34(b)(2)(C) [or STATE RULE]).
5. If anything was withheld as privileged, please provide the
description required by Rule 26(b)(5)(A) [or STATE RULE].
D. Form of production
6. Please confirm whether documents were produced as kept in the
usual course of business or organized and labeled to the
requests (Rule 34(b)(2)(E)(i)), and identify the report or print
template, the print date and any filters used.
7. Please produce [FLOWSHEET NAME] for [DATE TIME] to [DATE TIME]
showing, for each row, the value time, the filed time and the
user, and a production index listing Bates range, document type,
date, author and encounter for each document.
Please respond in writing by [DATE]. We are available to confer by
phone on [DATE/TIME], [DATE/TIME] or [DATE/TIME]. This letter does
not waive any other deficiency or any right to seek relief.
Sincerely,
[ATTORNEY NAME]
[BAR NO., CONTACT DETAILS]
Download this guide as a worksheet (CSV), with Done and Notes columns.
0 of 9 checked
A PDF shows that 2 versions of a note differ. It cannot show when the new text was typed, by whom, or whether a flowsheet row was filed at 02:00 or 2 months later. That lives in the audit trail and revision history, which AHIMA places outside both record sets. You get it only by asking for it, by name, in discovery.
Any 1 is enough
Log it or take it to deposition
Our view is that the request should be narrow and early. Ask for the audit trail and every saved revision of the specific note IDs and flowsheet rows your crosswalk flagged, for a date range running from admission to the latest production, in native or CSV form with the vendor's data dictionary. Narrow requests are harder to resist on proportionality under Rule 26(b)(1) and faster to read. How to read what comes back is covered in the EHR audit trail guide; how to tell a proper addendum from an alteration is in the altered medical records guide.
Request language for counsel to adapt. Name only the items the crosswalk flagged; add rows as later productions raise new ones.
REQUEST FOR PRODUCTION NO. [X]
For each of the following items in the electronic health record of
[PATIENT], encounter [NO.]:
(a) [Note type], dated [DATE TIME], author [ROLE], produced at
[DEF RANGE] and previously released at [PL RANGE];
(b) [Flowsheet name], rows timed [DATE TIME] to [DATE TIME],
produced at [DEF RANGE] and previously released at [PL RANGE];
produce, for the period [ADMISSION DATE] through the date of your
response:
1. The audit trail of every create, view, modify, sign, cosign,
addend, file, retract, print and release event for the item,
showing for each event the user, the user's role, the date and
time with time zone, the action, and the workstation or device.
2. The full text of every saved version or revision of the item,
including superseded and retracted versions, with the date and
time each version was saved.
3. For flowsheet rows, the value time and the filed time of each
row, and the user who filed it.
4. The release-of-information and print log for the chart,
including the release printed on or about [PRE-SUIT PRINT DATE].
5. A data dictionary or legend sufficient to read the event codes
and field names in items 1 to 4.
Produce items 1, 3 and 4 in native or CSV form, not as images.
Every citation now has to pick a set. An expert who cites PL 000161 while defense counsel holds DEF 000432 will spend 10 minutes at deposition establishing they are looking at the same note, and may find out mid-answer that they are not.
Our rule: the defense production is canonical. Cite the pre-suit set only where a document exists nowhere else, and cite both, with the difference stated, wherever a document changed. Keep 1 chronology, not 2 that drift apart, and attach the crosswalk to the expert's materials reviewed.
Rule 26(e)(1)(A) requires timely supplementation, and a deficiency letter usually produces a second set. Treat it as a third set: freeze, index, match against the log, add rows. Never renumber earlier sets. Record the new Bates range in the closed column of the row it answers, tell the expert which rows are still open, and if the defense expert cites a document your log shows as changed, say so with both cites in the expert report rebuttal.
Reconciliation has a mechanical half and a judgment half. The mechanical half is reading 1,600 pages, writing an index row for every document, and noticing that the note on page 432 has 4 more lines than the note on page 161. The judgment half is deciding whether a difference is format or content, and what it means. Legal AI tools are useful on a good part of the first half. They should not be trusted with the second.
Near-duplicate detection in AI ediscovery and technology assisted review platforms was built for email and office files. It can work on EHR prints with a good text layer and fails quietly on bad OCR. Check a sample of its "no difference" calls by hand.
A reconciliation finding you cannot trace to a page is worthless. A deficiency letter lands only if every gap it names points to a page in the production. Grounded, page-level citations give you that pointer, and human-in-the-loop review confirms the gap is real before the letter goes out. Courts have made the cost of skipping the check concrete. In Mata v. Avianca, Inc. (S.D.N.Y. 2023), lawyers were sanctioned under Rule 11 for filing a brief built on case citations a chatbot had fabricated. The same duty applies to a deficiency letter that cites a page, or an expert report that quotes a note. Open every cited page before it goes out.
For AI document review in reconciliation, including agentic AI that promises to run the whole workflow, rank the requirements in this order:
Every date, flag and quote opens its source page.
Signed before the first upload.
An independent security report and a written no-training commitment.
Each production stays its own file. 2 versions of 1 note are never merged silently.
Per-page OCR confidence, so a person reads the risky pages.
Who uploaded, viewed and edited what.
For how AI review compares to a person on accuracy, see is AI accurate enough for court and HIPAA-compliant AI medical record review.
Medrecords AI is medical record review software: you upload records, and it drafts a cited chronology, summaries and flags, every line linked to its source page. On this topic the limits come first.
Flags are signals, not verdicts. A near-duplicate that differs may be a pended note, a template difference or a real change, and the software cannot tell which. A human decides. The work runs under SOC 2 and HIPAA with a signed BAA (see security and HIPAA). The PHI access log records who accessed your uploaded file; it is not a hospital EHR audit trail. Self-Service bills 10 cents a deduplicated page, down to 5 cents at volume, duplicates free; Enterprise On-Prem is an annual license.
Book a demo on a matter where you hold a pre-suit set and a defense production, then run your first case free on us. Every line comes back cited to its source page. You review, you revise, you sign.
Scheduling only. No records move from a public page.
3 short guides from our help center, recorded on a demo case. They play inside the app: sign in or create a free account, and the video opens at the chapter you picked. First case is free on us.
Free account 2:33How repeated pages come out before anyone reads them, what each label means, and how to compare a removed page with the one that was kept.
Free account 2:35Every medical event on its date, in order, tied to the page it came from. Filter it, search it and export it as PDF or Word.
Free account 2:30Every record the case documents mention that the file does not contain, grouped by provider, with the page that mentions it.
Rules, regulations and statutes were checked against primary sources in September 2026, and quoted text is verbatim. The AHIMA brief is quoted in 3 short passages and otherwise paraphrased. The case in chapters 6 and 7, including every date, page number, page count and clinician, is hypothetical. Product facts come from this site's product pages. Nothing here is legal or medical advice, and state rules differ from the federal rules described here.
Related guides: what is Bates numbering, altered medical records, EHR audit trails in medical malpractice, how to get medical records for a lawsuit, and medical malpractice record review.