# PDF Sorting & Merging Software > PDF sorting and merging for medical records: merge a raw batch of separate PDF productions into 1 clean, ordered, page-numbered file, duplicates gone. Canonical page: https://medrecords.ai/product/pdf-sorting-merging/ --- 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/) › — PDF Sorting & Merging PDF SORTING AND MERGING SOFTWARE ## A stack of PDFs in. One sorted, merged file out. PDF sorting and merging software merges a raw batch of separate PDF productions into one clean, ordered, page-numbered file, using the same rule-based sorting engine as Document Sorting & Packet Builder. Duplicates are removed along the way, and the original source documents are preserved untouched. [Test a file ](https://medrecords.ai/test-a-file/?src=product-pdf-sorting-merging) [Book a demo](https://medrecords.ai/demo/) Adams, Timothy · Case #IME-4812 Merge queue Packet A — provider production 214 pgs Packet B — prior records 139 pgs 11 duplicates removed Merged file — chronological 342 pages ED visit, County Medical — p.1 · was B-p.4 Consult, Pinnacle Ortho — p.61 · was A-p.12 PT eval, Cedar Valley — p.152 · was A-p.98 p.140 quarantined — unreadable scan Source map attached 2 packets → one file Any number of sources, one output 11 duplicates caught Logged and removed, never silently 342 pages, renumbered Original source cited on every page ### Drop the whole production, however it arrived. Records never show up as one tidy PDF. They arrive as provider productions, prior packets, faxes, and re-scans — overlapping, out of order, and partly duplicated. The medical record PDF organizer reads every incoming file, detects duplicate pages across all of them, and merges what's left into one clean file. Duplicates detected across sources, not just within one file Unreadable pages quarantined for review, never silently dropped Dedup log Lab results, Cedar Valley — appears in both packets kept A · dropped B Referral letter — re-faxed copy, lower quality kept best scan Billing statement — identical pages, both packets kept A · dropped B All **11 duplicates** logged with what was kept, what was dropped, and why. Sort order Chronological — Provider — Category # — Date — Document — Source 1 Mar 18 ED visit record B-p.4 2 Apr 02 Ortho consult A-p.12 3 Apr 16 PT evaluation A-p.98 4 May 07 Procedure note A-p.131 ### Sort orders that match how the file gets read. Chronological for the reviewer working the history, by provider for deposition prep, by category when billing and imaging need to sit together. The order is rule-based, not model-improvised, so the same batch sorted twice comes out identical — every time. Chronological, provider, or category — switch any time Continuous page numbering applied after the sort ### The Packet Builder engine, doing its simplest job. Plainly: this is built on the same engine as [Document Sorting & Packet Builder](https://medrecords.ai/product/document-sorting-packet-builder/) . Packet Builder assembles curated, rule-driven packets for review and production; sorting and merging is that same engine answering the blunter request — one raw batch in, one clean file out. Which means your merged file and your built packets always follow the same sort rules. No 2 tools disagreeing about page order. One engine, 2 outputs Rule-based sorting engine segments · dedupes · orders · numbers PDF Sorting & Merging Raw batch → one ordered file Packet Builder Curated packets for review & production Audit-grade by design ### The merge never loses the paper trail. Most PDF mergers destroy provenance: once combined, nobody can say where page 61 came from. Here every page in the merged file keeps its original-source citation — which production it arrived in and its page number there. Duplicates are logged, not vaporized, so the file stays legally defensible when a page is disputed. [See how citations work ](https://medrecords.ai/product/citations/) Source map — Adams, T. · #IME-4812 Merged p.61 — where did it come from? · Source production — Packet A · Page in source — A-p.12 · Duplicate of — B-p.77 (dropped) p.140 quarantined — unreadable in both sources flagged, not dropped ### From loose PDFs to one working file. 3 steps — no desktop PDF wrangling. 01 Upload the batch Drop every PDF at once — productions, faxes, re-scans. No pre-sorting, no renaming. 02 Deduplicate and sort Duplicates are detected across sources and logged; pages are ordered by your chosen sort rules. 03 One numbered file out A merged, continuously numbered PDF with a source map citing where every page came from. ### Who merges files with it. Anyone who has ever received a records production in 9 PDFs and a fax. [ IME organizations One ordered file per exam, so the evaluator never re-sorts the referral packet. For IME orgs ](https://medrecords.ai/solutions/medical-evaluators/) [ Law firms Productions from every provider merged into one citable record for the case. For law firms ](https://medrecords.ai/solutions/law-firms/) [ TPAs & case management Every claim file in the same order, regardless of how the records arrived. For TPAs ](https://medrecords.ai/solutions/tpas/) [ Insurance carriers Clean, deduplicated files feeding review, with the dedup log for the audit trail. For carriers ](https://medrecords.ai/solutions/insurance-carriers/) FAQ ### Sorting and merging, answered. Yes — that's the core job. Provider productions, prior packets, faxes, and scans arrive as separate PDFs in different states; the engine reads each one, deduplicates pages across all of them, and merges everything into a single ordered file. 11 duplicate pages across 2 packets is a normal Tuesday. Chronological, by provider, or by category — the same rule-based sort orders as Document Sorting & Packet Builder, because it is the same engine underneath. Rules, not guesses, decide the order, so the same batch sorted twice comes out identical. Yes. Every page in the merged output carries its original-source citation — which incoming file it came from and its page number there. Nothing about the merge breaks the paper trail, which matters the moment anyone disputes a page. Same engine, simpler job — and we'd rather tell you that than pretend otherwise. Packet Builder assembles curated, rule-driven packets; PDF sorting and merging is that engine doing its most requested chore: one raw batch in, one clean file out. The merged file gets one continuous page numbering, applied after sorting and deduplication, so citations like "p.140" mean the same thing to everyone holding the file. The original numbering of each source is preserved in the source map, and Bates stamping is available when the file is headed for production. ### Related capabilities. Merging is step one — here's what usually happens next. [ Document Sorting & Packet Builder The parent engine — curated, rule-driven packets for review and production. See Packet Builder ](https://medrecords.ai/product/document-sorting-packet-builder/) [ Medical Record Bookmarking A navigable PDF outline generated from the same sort rules that ordered the merge. See bookmarking ](https://medrecords.ai/product/medical-record-bookmarking/) [ Bates Numbering & Stamping Production-ready Bates stamps applied to the merged, ordered file. See Bates stamping ](https://medrecords.ai/product/bates-numbering-stamping/) ### Send us your messiest batch of PDFs. Upload a raw production and get back one sorted, merged, page-numbered file with its source map — or book a quick demo. Handled under our BAA; never used to train a model. [Test a file ](https://medrecords.ai/test-a-file/?src=product-pdf-sorting-merging) [Book a demo](https://medrecords.ai/demo/) [All capabilities →](https://medrecords.ai/product/)