Claim Splitting

EDI Paisan's splitting feature breaks large EDI files into smaller pieces — by claim, by subscriber, by provider, or by transaction. Essential for clearinghouse file size limits, targeted resubmissions, and isolating problem claims.

---

What Is Claim Splitting?

Claim splitting divides a single EDI file into multiple valid files, each containing a subset of the original data. Every output file includes proper envelopes (ISA/IEA, GS/GE, ST/SE) with updated control numbers.

For example, an 837 file with 500 claims can become:

• 500 individual claim files
• 50 files with 10 claims each
• Files grouped by rendering provider
• Files grouped by subscriber

Each output file is fully valid X12 and ready for submission or processing.

---

Why Split Files?

File Size Limits

Many clearinghouses impose size limits (often 5MB or 10MB). Split large files into manageable chunks that meet your trading partner's requirements.

Targeted Resubmission

Got a rejection on one claim? Split it out, fix it, and resubmit — without touching the other 499 claims in the file.

Isolating Problem Claims

When you need to troubleshoot specific claims, split them into individual files for focused analysis.

Provider-Specific Routing

Some clearinghouses require separate files per rendering provider or billing provider. Split automatically by provider NPI.

Payment Reconciliation

Split 835 files by check to match individual payments with bank deposits.

Claim-Level Workflows

Need to process claims one at a time? Split an 837 by claim and feed individual files to your workflow system.

---

Split Modes

EDI Paisan offers different split modes depending on the transaction type.

Universal Modes (All File Types)

These modes work with any X12 file:

Mode	What It Does	Use Case
By Parts	Divide into N equal parts	File size limits
By Transaction	One file per ST...SE envelope	Transaction-level processing
By Group	One file per GS...GE envelope	Functional group separation
By Interchange	One file per ISA...IEA envelope	Trading partner isolation

837 Claim-Specific Modes

For 837 professional (837P) and institutional (837I) claims:

Mode	What It Does	Use Case
By Subscriber	Each subscriber with their dependent claims	Patient-centric workflows
By Claim	Each claim becomes a separate file	Individual claim submission
By Rendering Provider	Group by rendering provider NPI	Provider-specific clearinghouses
By Payer	Group all subscribers by their payer	Payer-specific routing or analysis

835 Payment-Specific Modes

For 835 remittance advice files:

Mode	What It Does	Use Case
By Check	Each check/EFT payment	Check-level reconciliation
By Payment	Each claim payment becomes a file	Payment posting workflows
By Payer	Group by payer organization	Payer-specific analysis
By Provider	Group by payee/provider	Multi-provider practices

---

Re-Enveloping

When files are split, EDI Paisan creates proper envelopes for each output file:

What Gets Updated

Segment	Element	Description
ISA	ISA13	Unique interchange control number
GS	GS06	Unique functional group control number
ST	ST02	Transaction set control number
SE	SE01	Accurate segment count
GE	GE01	Accurate transaction count
IEA	IEA01	Accurate functional group count

What Stays the Same

• Sender/receiver identifiers (ISA05-08)
• Functional identifier code (GS01)
• Version/release (GS08)
• Original date/time stamps
• All claim content

Control Number Management

Free tier uses preview control numbers (random, may not be unique across sessions).

Pro tier uses production-ready, database-backed sequences that guarantee uniqueness and persist across sessions.

---

Tier Requirements

Feature	Free	Pro	Enterprise
Preview split results	✅	✅	✅
Download split files	❌	✅	✅
Production control numbers	❌	✅	✅
Batch download (ZIP)	❌	✅	✅

Free tier users can preview what splitting would produce — see the count, examine individual chunks in the viewer. To download split files, you'll need Pro or higher.

---

How Splitting Works

1. Upload your file — Load any supported EDI file
2. Choose split mode — Select how you want to divide the file
3. Preview results — See chunk count and examine each piece
4. Download — Export individual files or all chunks as a ZIP

All processing happens in your browser. Files never leave your computer.

Step-by-step guide →

---

Common Workflows

Clearinghouse Submission

Large 837 (15MB) → Split by Parts (3) → Three 5MB files → Submit separately

Reprocessing Denials

835 with denials → Identify denied claim IDs → Split original 837 by claim → Fix specific claims → Resubmit

Provider Distribution

Multi-provider 837 → Split by Rendering Provider → Route to provider-specific clearinghouses

Payer-Specific Routing

Multi-payer 837 batch → Split by Payer → Route each file to payer's clearinghouse

Payment Reconciliation

Large 835 → Split by Check → Match individual files to bank deposits

---

Best Practices

Before Splitting

• Validate first — Make sure the original file is valid X12
• Note the totals — Record original claim/service line counts for verification
• Back up — Keep the original file in case you need it

After Splitting

• Verify counts — Sum of split chunks should equal original
• Spot check — Open a few split files to confirm content
• Test submission — Try one file before submitting all

Control Numbers

• Production use — Always use Pro tier for files you'll submit to clearinghouses
• Testing — Free tier preview numbers are fine for internal testing

---

Limitations

Splitting Preserves Structure

Splitting never breaks a claim in the middle. The smallest unit is:

• 837: One claim (CLM loop with all service lines)
• 835: One claim payment (CLP with all SVC lines)

Memory Considerations

Very large files (100MB+) may strain browser memory. For enterprise-scale batch splitting, contact us about API access.

Original File Unchanged

Splitting creates new files. Your original file is never modified.

---

Related Documentation

• How to Split Files — Step-by-step guide
• Splitting by Payer — Detailed guide for payer-based splitting
• Pro Tier — Download and export features
• 837P Reference — Understanding claim structure
• 835 Reference — Understanding payment structure