# Medical Record Deduplication Software > Medical record deduplication that finds duplicate pages across merged provider files, confidence-scores every match, and collapses them to 1 canonical record. Canonical page: https://medrecords.ai/product/medical-record-deduplication/ --- NewWe now read the actual MRI and CT imaging — not just the radiologist's 1-page report. [See how →](https://medrecords.ai/product/imaging/) [Home](https://medrecords.ai/) ›[Product](https://medrecords.ai/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. [Test a file ](https://medrecords.ai/test-a-file/?src=product-medical-record-deduplication) [Book a demo](https://medrecords.ai/demo/) 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 11 duplicates Found in one 342-page, 2-packet production One click To collapse a confirmed duplicate set Nothing deleted Collapsed pages are hidden and logged, never destroyed ### 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 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 — refax — exact · collapse Progress note — second copy — exact · collapse Referral letter — one line differs — near-duplicate · hold The differing line is shown **side by side** before anything collapses. ### Confidence-scored, then collapsed — by you. Exact matches collapse in one 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. Nothing silently deleted ### 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 ](https://medrecords.ai/product/record-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 One click per set. The canonical page keeps every copy's provenance, and the collapse is logged. ### Who dedupes with it. Anyone who pays for pages twice — in review cost or reviewer attention. [ Law firms Productions shrink to the pages that matter, with Bates citations intact. For law firms ](https://medrecords.ai/solutions/law-firms/) [ IME & QME evaluators Evaluators read each visit once, not 3 times across 3 packets. For medical evaluators ](https://medrecords.ai/solutions/medical-evaluators/) [ TPAs & case management Per-page review costs stop paying for the same page twice. For TPAs ](https://medrecords.ai/solutions/tpas/) FAQ ### Deduplication, answered. Pages are compared across the whole production, not just within one packet. 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 one 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. [ Co-Mingled Records Detection Pages from the wrong patient flagged and quarantined before analysis. Explore ](https://medrecords.ai/product/co-mingled-records-detection/) [ Supplemental Record Review New batches arrive pre-deduplicated and flagged where they agree, conflict, or add. Explore ](https://medrecords.ai/product/supplemental-record-review/) [ Record Version & Alteration Detection Near-duplicates that differ get scrutiny, not a silent merge. Explore ](https://medrecords.ai/product/record-alteration-detection/) [ Bates Numbering & Stamping Numbering that holds through sorting, dedup, and production. Explore ](https://medrecords.ai/product/bates-numbering-stamping/) ### 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. [Test a file ](https://medrecords.ai/test-a-file/?src=product-medical-record-deduplication) [Book a demo](https://medrecords.ai/demo/) [All capabilities ](https://medrecords.ai/product/)