NewMissing Records Detection: flags every visit, provider, and date missing from the file. See how →
Home›Product›Medical Record Deduplication

Medical record deduplication

3 copies of the same visit. One canonical record.

Medical record deduplication collapses 3 copies of the same visit into one canonical record. Merged provider files carry duplicate entries by default: duplicates are found, confidence-scored, and collapsed by you, without losing a single citation. Collapsed is not destroyed: the duplicates remain reviewable, and every citation survives the collapse back to its source page.

From 10 cents a page, down to 5 cents with volume. Billed per page, not per case.

Adams, T. right knee · Case #IME-4812 342 pages · 2 packets
11 duplicate pages found across 2 packets
Operative report: 3 copies exact match · collapsed
Progress note: 2 copies exact match · collapsed
Referral letter: 2 versions near-duplicate · review
Lab panel: refax, lower quality exact match · collapsed
One canonical record · provenance kept for every collapsed page
Medrecords AI deduplication review: removed duplicate pages beside the kept original, with the reason for each removal
Duplicate review: the kept page, the removed copy and why it was removed. Sample case.
11 duplicates
Found in one 342-page, 2-packet production
1 click
To collapse a confirmed duplicate set
Nothing deleted
Collapsed pages are hidden and logged, never destroyed

What about near-duplicates: 2 versions of the same page?

Medrecords AI never auto-merges them. A near-duplicate gets flagged with the differing content shown side by side, because a changed word between 2 copies can be an amended record. Suspected alterations route to Record Version & Alteration Detection for a closer look.

Merged files duplicate by default.

A production assembled from the provider, the payer, and prior counsel carries the same visit several times over. Reviewers pay for those pages twice: once in cost, once in attention. Deduplication finds the repeats before anyone reads them.

Exact duplicates matched across packets and sources
Page-for-page copies caught even at different scan quality
Matching runs on extracted content, not the file itself: a native PDF export in one packet and a rescanned copy in another still resolve to the same page
Same visit, 3 sources
Packet 1
Operative report
Packet 2
Operative report
Canonical
One kept copy
matched across packets scan quality ignored
Match review
Lab panel: refaxexact · collapse
Progress note: second copyexact · collapse
Referral letter: 1 line differsnear-duplicate · hold
The differing line is shown side by side before anything collapses.

Confidence-scored, then collapsed, by you.

Exact matches collapse in 1 click. Near-duplicates (a re-fax, an amended note, a different scan of the same page) are flagged with a score and held for a human decision. A changed word between 2 "copies" is exactly what should never disappear silently.

Near-duplicates flagged for review, never auto-merged
Suspected alterations route to Record Version & Alteration Detection

Citations survive the collapse.

The canonical page inherits the provenance of every copy: which packet it arrived in, where it sat, and its Bates range. Any citation that pointed at a duplicate resolves to the canonical page, so nothing in a chronology or report breaks.

Full provenance recorded for every collapsed page
Collapsed pages recoverable at any time
Provenance
Canonical: Operative report
packet 1 · p.44 packet 2 · p.230 Bates range kept
Citations to any copy resolve here: chronology, chat, and reports keep working.
Dedup log · Case #IME-4812
Operative report set collapsed logged · reviewer
Referral letter held near-duplicate
Collapse reversed restored · logged
Every event attributable · every page recoverable.

Collapsed is not destroyed.

Every collapse is a logged event: who confirmed it, when, and exactly what was hidden. The duplicate pages stay in the file, recoverable, with the audit trail to prove the record wasn't altered. Source-linked and legally defensible, even after cleanup.

See Record Version & Alteration Detection

From merged mess to canonical file.

Deduplication runs at intake, so everything downstream reads the clean record.

01
Upload the merged production

Provider files, payer files, and prior productions go in together: duplication expected.

02
Duplicates matched and scored

Exact copies are grouped automatically; near-duplicates get a confidence score and wait for a human.

03
Confirm and collapse

1 click per set. The canonical page keeps every copy's provenance, and the collapse is logged.

Watch duplicate pages removed, each with its reason

The demo starts on the Create New Case form of a demo case, where Strip cover pages, Strip custodian certifications and Remove duplicate pages are all on by default. The cover page tooltip notes that stripped pages stay in the stored records and keep their page and Bates numbers. After processing, the Uploaded Files panel shows a banner for each kind of page set aside: 42 duplicate pages removed, 7 images set aside as non-clinical, 9 cover pages stripped and 4 blank pages removed. View on the duplicates banner lists each kept page next to the copies removed from it, with a match type of Exact, Subset or AI and a short reason. Compare opens both pages side by side, highlights the shared lines and states why the copy was removed. Every name, provider and date in the demo is invented.

Transcript
  1. Covers, certifications and duplicates are stripped at upload by default.
  2. The case page counts what was set aside, and why.
  3. Each removed page sits next to the page that was kept.
  4. Compare any pair side by side, with the reason it was removed.

Watch it as a video page · Download the video (MP4, 20 seconds)

Who dedupes with it.

Anyone who pays for pages twice, in review cost or reviewer attention.

Where it stops

  • It collapses exact copies on your say-so; it never auto-merges near-duplicates, which wait for a human decision.
  • It reads only the files you upload. It does not request or retrieve records for you.
  • It drafts and cites. It does not diagnose, give a medical opinion or sign anything; a qualified reviewer checks the output.
  • Each finding cites its source page, so the reviewer can check it against the record.

More questions, answered

How are wrong-patient pages detected?

Every page is checked against the case patient on 2 axes: identity signals (name, date of birth, record identifiers) and clinical continuity, meaning whether the page's content is consistent with the rest of the file. A left-shoulder operative note inside a right-knee case gets flagged even if no name appears on the page.

What happens when a page is quarantined?

It is pulled out of the analysis pipeline immediately: excluded from the chronology, search, chat, reports, and any export or production. Reviewers see that a page was quarantined and the stated reason, but the content is held back so the other patient's PHI stops spreading.

How does this prevent a PHI incident?

A co-mingled page that reaches a report, a production, or opposing counsel is a disclosure, with the notification duties that follow. Detection at intake means the page never reaches a downstream output, so what would have been an incident becomes a documented catch.

Can a quarantined page ever reach analysis?

Only by an explicit human decision. If a reviewer determines the page does belong to the case patient (a maiden name, a transcription error), they can release it, and the release is logged with the reviewer and reason. Nothing is released automatically.

What audit trail exists behind a quarantine?

Every step writes an entry: detection, the stated mismatch, the quarantine, and the eventual release or removal, each with a timestamp and actor. The log exports with the case, so compliance gets evidence rather than recollection.

Deduplication, answered.

Pages are compared across the whole production, across packets. Exact copies match even when scan quality differs; near-matches get a confidence score that reflects how much of the page is identical. High-confidence sets collapse in 1 click, and anything ambiguous is held for review.

Yes. That is the core case. A file merged from the provider, the payer, and prior counsel typically repeats the same visits; in a representative 342-page, 2-packet production, 11 duplicate pages were found and collapsed to one canonical record.

Yes. The canonical page inherits every copy's provenance: source packet, position, and Bates range. Citations that pointed to a collapsed copy resolve to the canonical page, so chronologies, reports, and exports keep working.

They are never auto-merged. A near-duplicate gets flagged with the differing content shown side by side, because a changed word between 2 copies can be an amended record. Suspected alterations route to Record Version & Alteration Detection for a closer look.

Both. Confirmed exact sets can be collapsed one at a time or all at once, and every collapse (single or bulk) is logged with the reviewer, timestamp, and affected pages, and can be reversed.

Related capabilities

Adjacent features on the same platform: every output source-linked and cited to page.

Related features

Deduplication is 1 pass in a larger intake cleanup: these run alongside it.

Find out how much of your file is repeats.

Upload one merged production and see the duplicate sets, scored and cited. Handled under our BAA; never used to train a model.