Lido splits large scanned medical record packets, chart bundles, release-of-information outputs, and transferred records, by patient, encounter date, or document type. What arrives as a 200-page PDF becomes individual, labeled files ready for your EHR, records archive, or audit binder.
.png)
.png)
Scanned medical records arrive as large, undifferentiated PDFs. Splitting them by patient, encounter, or document type is a necessary but labor-intensive step before records can be filed, shared, or used in audits. Lido reads the content to determine split points and names the output files automatically.
Medical records arrive as large multi-page PDFs from a scanner, a records release vendor, a transferring provider's EHR, or a paper chart digitization project. A single file may contain records for multiple patients or multiple encounters for one patient. Lido receives these files from a watched folder or upload and begins processing immediately.
Page-level content analysis identifies where each document begins. Headers like "Discharge Summary," "Progress Note," "Radiology Report," and "Lab Results" signal a new document. Patient name and date-of-service fields signal a new patient or encounter. Separator sheets, common in release-of-information outputs, are detected and used as split points.
Each split document is classified: progress note, discharge summary, radiology report, operative report, lab results, medication list, consultation note, or other. Classification is based on document header, content structure, and section headings. Unclassified documents are labeled "Unknown" and flagged for manual review.
From each document, Lido extracts patient name, patient ID or MRN, date of service, ordering or attending physician, and document type. This metadata is used to generate structured file names — "Smith_John_MRN12345_2026-03-14_DischargeSummary.pdf", and to route each file to the correct patient folder in your archive or EHR.
Individual split documents are saved to a structured output folder organized by patient, then by encounter date, then by document type. Or they are pushed via API to your EHR document management module. A processing manifest lists every split document, its source page range, extracted metadata, and destination path, for audit and reconciliation purposes.
Upload a batch and get structured output in minutes.
Multi-patient or multi-encounter chart bundles from paper chart digitization projects. Split by patient and encounter, classified by document type within each encounter.
Record release PDFs generated by your EHR or a ROI vendor, often containing records for a specific date range across all document types for one patient.
Records received from a prior provider or hospital system, often scanned in bulk from a paper chart or exported as a single PDF from a different EHR.
Hospital inpatient records including admission H&P, progress notes, orders, nursing notes, labs, and discharge summary, often spanning dozens of pages per admission.
Record packets assembled for payer audit, RAC review, or accreditation survey. Split and labeled so specific document types can be located quickly during the audit.
Historically scanned paper charts from closed practices or chart conversion projects. Lido applies the same splitting and classification logic regardless of how old the records are.
A 300-page chart bundle arrives from a transferring hospital for a newly admitted patient. The health information management team opens the PDF, scrolls through page by page, identifies where the discharge summary starts (page 47), where the operative reports begin (page 112), and where the labs end (page 298). They manually crop sections, save individual files, rename each file, and upload to the correct patient chart. For three bundles per day across a busy HIM department, this is 2–3 hours of work that produces no clinical value, just organized files.
Lido reads each page's content to identify document boundaries, classifies each split document, extracts patient and encounter metadata, and names output files with structured identifiers. A 300-page bundle is processed in minutes. Your HIM team reviews the classification manifest, corrects any misclassifications, and confirms the filing, instead of spending hours manually extracting documents from a PDF.
| Feature | Lido | Manual splitting |
|---|---|---|
| Detect document boundaries from page content automatically | ✓ | ✗ |
| Classify each split document by type (progress note, lab, imaging, etc.) | ✓ | ✗ |
| Extract patient and encounter metadata for structured file naming | ✓ | ✗ |
| Route split files to the correct patient folder automatically | ✓ | ✗ |
| Generate a processing manifest for audit and reconciliation | ✓ | ✗ |
| Scroll through the PDF and manually cut-and-save each section | ✓ | ✓ |
Split, classify, and file chart bundles automatically. Your HIM team handles exceptions, not page counts.
A regional hospital receives transferred records from referring facilities for 25 new admissions per week. Chart bundles from 12 different EHR systems arrive in varying formats. Lido splits each bundle by document type, extracts encounter metadata, and routes individual files to the correct inpatient chart in the hospital's EHR within minutes of receipt.
An HIM team is digitizing a warehouse of legacy paper charts from a practice acquisition. 180,000 pages of scanned records need to be split, classified, and filed to patient charts. Lido processes the batch continuously, classifying each document and flagging records that cannot be matched to an active patient for manual review.
A billing company receives record requests from payers for audit review. Each request covers 10–40 claims, each requiring specific document types. Lido splits the record packets by claim and document type so the audit response binder can be assembled without manually locating each document.
A practice group with 8 locations acquired three practices over 5 years. Two locations still use a legacy EHR that exports records as single-patient PDF bundles. Lido splits and classifies these bundles and delivers structured files compatible with the group's primary EHR import format.
%20(1).svg)
