What is EDI?

If you've ever wondered what those cryptic files with tildes and asterisks are all about, you're in the right place. This guide explains EDI in plain English — no prior knowledge required.

---

The Simple Explanation

EDI (Electronic Data Interchange) is a standardized way for computers to exchange business documents electronically. Instead of faxing paper claim forms or mailing invoices, organizations send structured data files that computers can read and process automatically.

Think of it like this: if a phone call is two people talking, EDI is two computers talking — using a strict "language" they both understand.

---

Why Healthcare Uses EDI

Before EDI, healthcare billing was a nightmare of paper:

• 📄 Paper claim forms had to be printed, mailed, and manually entered
• ⏱️ Processing took weeks instead of days
• ❌ Errors were everywhere — typos, lost documents, illegible handwriting
• 💸 Costs were huge — postage, labor, storage

EDI solves these problems by letting healthcare providers and insurance companies exchange billing information electronically, instantly, and accurately.

The HIPAA Mandate

In 1996, HIPAA (Health Insurance Portability and Accountability Act) didn't just create privacy rules — it also mandated that healthcare organizations use standardized electronic formats for certain transactions. This is why everyone in US healthcare uses the same EDI standards.

The specific standard used is called X12, managed by the Accredited Standards Committee (ASC). Healthcare transactions follow the X12 5010 version, with specific implementation guides for each transaction type.

---

What EDI Files Look Like

Here's a snippet of a real EDI file (an 837 professional claim):

ISA*00*          *00*          *ZZ*CLEARINGHOUSE  *ZZ*PAYERID        *240115*1230*^*00501*000000001*0*P*:~
GS*HC*SENDER*RECEIVER*20240115*1230*1*X*005010X222A1~
ST*837*0001*005010X222A1~
BHT*0019*00*BATCH001*20240115*1230*CH~
NM1*41*2*ABC MEDICAL GROUP*****46*123456789~
...

Looks intimidating? That's because EDI was designed for computers, not humans. Each line (called a segment) starts with a code like NM1 or CLM, followed by data elements separated by asterisks.

This is exactly why tools like EDI Paisan exist — to translate this machine language into something you can actually read and understand.

---

Common Healthcare EDI Transactions

Code	Name	What It Does
837	Claim	Sends billing claims from providers to payers
835	Remittance	Returns payment details and explanations from payers
270	Eligibility Inquiry	Asks "Is this patient covered?"
271	Eligibility Response	Answers with coverage details
276	Claim Status Inquiry	Asks "What happened to my claim?"
277	Claim Status Response	Provides claim processing status
278	Prior Authorization	Requests/approves services in advance

The most common files you'll encounter are 837 (claims going out) and 835 (payments coming back).

---

The Journey of a Claim

Here's how EDI flows through a typical healthcare billing cycle:

┌─────────────────┐     ┌──────────────────┐     ┌─────────────┐
│  Provider EHR   │────▶│  Clearinghouse   │────▶│   Payer     │
│                 │ 837 │                  │ 837 │             │
└─────────────────┘     └──────────────────┘     └─────────────┘
                                                        │
┌─────────────────┐     ┌──────────────────┐           │
│  Provider EHR   │◀────│  Clearinghouse   │◀──────────┘
│                 │ 835 │                  │      835
└─────────────────┘     └──────────────────┘

1. Provider creates a claim in their EHR/billing system
2. System generates an 837 file and sends it to a clearinghouse
3. Clearinghouse validates, maybe reformats, and forwards to the payer
4. Payer processes the claim and sends back an 835 file with payment details
5. Payment information flows back through the clearinghouse to the provider

---

Key EDI Concepts

Envelopes

EDI files use a nesting structure, like envelopes within envelopes:

• Interchange (ISA/IEA) — The outer envelope identifying sender/receiver
  • Functional Group (GS/GE) — Groups related transactions
    • Transaction Set (ST/SE) — An individual transaction (one claim, one payment, etc.)

Segments

Each line in an EDI file is a segment. Segments start with a code and contain data elements:

NM1*IL*1*SMITH*JOHN****MI*12345678901~
│   │  │ │     │       │  └─ Member ID
│   │  │ │     │       └─ ID Type (Member ID)
│   │  │ │     └─ First Name
│   │  │ └─ Last Name
│   │  └─ Person (vs Organization)
│   └─ IL = Insured/Subscriber
└─ NM1 = Name segment

Delimiters

EDI files use special characters to separate data:

• * (asterisk) — Element separator
• ~ (tilde) — Segment terminator
• : or ^ — Component separator (for sub-elements)

Different files might use different delimiters — the ISA segment defines which ones are used.

---

A Brief History

Year	Milestone
1960s	Early EDI developed for transportation and retail
1979	ANSI ASC X12 standards committee formed
1996	HIPAA mandates EDI standards for healthcare
2000	HIPAA 4010 version becomes standard
2012	HIPAA 5010 version (current) takes effect
Today	X12 continues evolving; healthcare still runs on 5010

---

How EDI Paisan Helps

Working with raw EDI files is like reading a foreign language. EDI Paisan acts as your translator:

• See structure clearly — Navigate claims and segments in a visual tree
• Understand meanings — Every code and value is labeled with its description
• Find what you need — Search by patient name, claim ID, or segment type
• Keep data private — Everything runs in your browser; your files never leave your computer

Whether you're troubleshooting a rejected claim, splitting a large batch file, or just trying to understand what's in an 835 payment file, EDI Paisan makes it accessible.

---

Next Steps

Ready to dig in?

• Quick Start Guide — Upload and explore your first file
• Upload Your First File — Step-by-step walkthrough
• 837 Claims Overview — Understand claim files
• 835 Remittance Overview — Understand payment files
• Supported File Types — All transaction types we support

---

Common Questions

Do I need to understand EDI to use EDI Paisan?
Nope! EDI Paisan handles the translation. But understanding the basics (like what you've read here) will help you find what you're looking for faster.

Is EDI only used in healthcare?
No — EDI originated in transportation and retail. But healthcare has its own specific implementation guides (the "005010X..." codes you see) that follow HIPAA requirements.

Why does EDI look so old-fashioned?
Because it is! The X12 format was designed in the 1970s-80s when data storage was expensive and simplicity mattered more than readability. It's survived because it works — and changing standards in healthcare is incredibly difficult.

Will EDI ever be replaced?
There are newer standards like FHIR (for clinical data) and discussions about modernizing billing, but X12 EDI will likely remain the backbone of healthcare billing for years to come.