An EDI 837 file is the HIPAA-standard electronic claim that healthcare providers send to payers. It replaces paper claim forms like the CMS-1500 and UB-04. In this guide, we explain how 837 files work in healthcare, break the file down segment by segment, and give you an EDI 837 sample file to download and test with.
What Is the EDI 837 Health Care Claim Transaction Set?
The EDI 837 Health Care Claim Transaction Set is a standardized format for submitting healthcare claim information electronically. Healthcare providers use it to send claims to payers, such as insurance firms and government agencies. This transaction set ensures that all necessary details about patient care, procedures performed, and associated costs are communicated through accurate and timely claims processing.
EDI 837 Subgroups
The EDI 837 file includes various types of claims, including professional, institutional, and dental, making it a versatile tool in the healthcare billing process.
1. EDI 837P for Professionals
The (Professional) or 837X222A1 transaction set is used by healthcare professionals, such as doctors, therapists, and other individual practitioners, to submit claims for services rendered. This includes outpatient services, physician visits, and other professional healthcare services. The 837P format ensures that detailed information about the patient, services provided, and charges are accurately communicated to the payer.
2. EDI 837I for Institutions
The EDI 837I (Institutional) or 837X223A3 transaction set is used by healthcare institutions, such as hospitals and nursing facilities, to submit inpatient and outpatient services claims. This format captures comprehensive information about the patient’s stay, treatments received, and associated costs, enabling efficient processing and reimbursement by payers.
3. EDI 837D for Dental Practices
The EDI 837D ( Dental) or 837X224A3 transaction set is designed for dental practices to submit claims for dental services. It includes detailed information about dental procedures, patient details, and billing information. The 837D format ensures that payers process dental claims accurately and efficiently.
Benefits of Using the EDI 837 Transaction Set
Implementing the EDI 837 transaction set offers four primary benefits for healthcare providers and payers:
Efficiency and Speed: EDI 837 allows for faster claim submission and processing, reducing administrative delays and accelerating reimbursements. On average, medical providers save about 5 minutes per transaction, while dental providers save around 4 minutes per transaction, allowing more time to focus on patient care.
Accuracy: The standardized format of the EDI 837 transaction set minimizes errors and discrepancies in claim information, leading to fewer claim rejections and denials. This accuracy ensures that healthcare providers receive timely and correct payments.
Cost Savings: By eliminating the need for paper-based claims, EDI 837 reduces printing, mailing, and handling costs. The adoption of EDI 837 can lead to substantial cost savings, with the medical and dental sectors combined saving approximately $2.4 billion annually. Specifically, the medical industry can save $2.1 billion, while the dental industry can save $286 million.
Compliance: This compliance helps avoid potential legal issues and penalties, providing a secure and reliable method for processing claims.
EDI 837 Sample File (Free Download)
Below is a sample 837P (professional) claim in the X12 5010 format (005010X222A1). It’s a single office visit with two service lines. All names and IDs are made up, so you can use it to test parsers, mapping and validation.
Download the EDI 837 sample file (.txt)
ISA*00* *00* *ZZ*SUBMITTER01 *ZZ*RECEIVER01 *261015*1200*^*00501*000000101*0*T*:~
GS*HC*SUBMITTER01*RECEIVER01*20261015*1200*101*X*005010X222A1~
ST*837*0001*005010X222A1~
BHT*0019*00*CLM20261015001*20261015*1200*CH~
NM1*41*2*SAMPLE BILLING SERVICE*****46*SUB12345~
PER*IC*JANE DOE*TE*5555551234~
NM1*40*2*SAMPLE HEALTH PLAN*****46*PAYER678~
HL*1**20*1~
PRV*BI*PXC*207Q00000X~
NM1*85*2*EXAMPLE FAMILY CLINIC*****XX*1234567893~
N3*123 MAIN STREET~
N4*SPRINGFIELD*IL*62701~
REF*EI*123456789~
HL*2*1*22*0~
SBR*P*18*GRP12345******CI~
NM1*IL*1*SMITH*JANE****MI*ABC123456789~
N3*456 OAK AVENUE~
N4*SPRINGFIELD*IL*62704~
DMG*D8*19850214*F~
NM1*PR*2*SAMPLE HEALTH PLAN*****PI*PAYER678~
CLM*PATACCT001*150***11:B:1*Y*A*Y*Y~
HI*ABK:J069~
NM1*82*1*BROWN*ROBERT****XX*1987654328~
PRV*PE*PXC*207Q00000X~
LX*1~
SV1*HC:99213*100*UN*1***1~
DTP*472*D8*20261010~
LX*2~
SV1*HC:87880*50*UN*1***1~
DTP*472*D8*20261010~
SE*29*0001~
GE*1*101~
IEA*1*000000101~EDI 837 File Format: Segment-by-Segment Breakdown
Segment | Loop | Name | What it does | Value in the sample |
|---|---|---|---|---|
ISA | Header | Interchange Control Header | Opens the file and sets the sender, receiver, date and delimiters | Sender |
GS | Header | Functional Group Header | Groups transactions of one type ( | Version |
ST | Header | Transaction Set Header | Starts the 837 transaction | Control # |
BHT | Header | Beginning of Hierarchical Transaction | Sets the batch purpose and reference |
|
NM1*41 | 1000A | Submitter Name | Identifies who sends the file | Sample Billing Service |
PER | 1000A | Submitter Contact | Contact person for the file | Jane Doe, phone |
NM1*40 | 1000B | Receiver Name | Identifies the payer or clearinghouse receiving the file | Sample Health Plan |
HL*20 | 2000A | Billing Provider Level | Starts the billing provider hierarchy | HL 1 |
PRV | 2000A | Provider Specialty | Taxonomy code |
|
NM1*85 | 2010AA | Billing Provider Name | Billing provider and NPI | Example Family Clinic |
N3 / N4 | 2010AA | Billing Provider Address | Street, city, state, ZIP | Springfield, IL |
REF*EI | 2010AA | Billing Provider Tax ID | Employer identification number |
|
HL*22 | 2000B | Subscriber Level | Starts the subscriber (insured) hierarchy | HL 2 |
SBR | 2000B | Subscriber Information | Payer responsibility and relationship | Primary ( |
NM1*IL | 2010BA | Subscriber Name | Insured’s name and member ID | Jane Smith |
DMG | 2010BA | Demographics | Date of birth and gender | 1985-02-14, F |
NM1*PR | 2010BB | Payer Name | Insurance company and payer ID | Sample Health Plan |
CLM | 2300 | Claim Information | Claim ID, total charge, place of service | $150, office ( |
HI | 2300 | Diagnosis Codes | ICD-10 diagnosis codes |
|
NM1*82 | 2310B | Rendering Provider | Clinician who performed the service | Dr. Robert Brown |
LX | 2400 | Service Line Number | Numbers each service line | 1, 2 |
SV1 | 2400 | Professional Service | CPT/HCPCS code, charge, units |
|
DTP*472 | 2400 | Service Date | Date of service | 2026-10-10 |
SE | Trailer | Transaction Set Trailer | Closes the transaction with a segment count | 29 segments |
GE / IEA | Trailer | Group / Interchange Trailers | Close the group and the file |
|
How 837 Files Are Used in Healthcare
Under HIPAA, every covered provider that bills electronically must send claims as 837 files. In practice, a practice management or EHR system creates the 837 file and sends it to a clearinghouse. The clearinghouse checks it and forwards it to the payer. The payer confirms receipt with a 999 acknowledgment, reports claim status with a 277CA, and sends payment details back in an EDI 835 remittance. To see how enrollment, claims and payments fit together, read our guide to EDI 834, 835 and 837.
Workflow for the Exchange of EDI 837 File
The workflow for exchanging an EDI 837 file involves seven steps:
Claim Creation: Healthcare providers use their practice management or billing software to generate claim information.
EDI Conversion: The claim data is converted into the EDI 837 format using an EDI translator or software.
Transmission: The EDI 837 file is securely transmitted to the payer using an EDI VAN (Value-Added Network) or direct EDI connection.
Acknowledgment: The payer acknowledges receipt of the claim file, often using the EDI 999 or 277CA transaction sets.
Processing: The payer processes the claim, verifying the information and adjudicating the claim based on the coverage and policy rules.
Coordination of Benefits: If the patient has many insurance policies, the coordination of benefits process determines the order in which payers are responsible for covering the claim.
Response: The payer sends an EDI 835 transaction set (Health Care Claim Payment/Advice) to the provider, detailing the payment and any adjustments or denials.
Where 837 Fits In The EDI Sequence Flow (EDI 834 – EDI 837 – EDI 835)
Step 1: Enrollment and Eligibility (EDI 834) Scenario: A healthcare facility enrolls a new patient, Jane Smith, in a health plan.
Example: Jane Smith, a newly hired employee, selects a health insurance plan through her employer. The employer transmits an EDI 834 transaction to XYZ Health Insurance, which processes the enrollment and confirms it back to the employer.
Step 2: Claim Submission (EDI 837) Scenario: Jane Smith visits a healthcare provider for a routine check-up.
Example: The provider submits an EDI 837 transaction to XYZ Health Insurance, listing services such as a wellness exam, blood pressure screening, and routine lab tests.
Step 3: Claim Payment and Remittance Advice (EDI 835) Scenario: The healthcare provider receives reimbursement for Jane Smith’s visit.
Example: XYZ Health Insurance issues an EDI 835 transaction to the provider, detailing a payment of $350 for Jane Smith’s check-up, including an adjustment for a $50 co-pay and a $30 provider discount.
Automating Your EDI 837 Workflows with HealthEDI
The EDI 837 Health Care Claim Transaction Set is vital to the healthcare industry’s billing and reimbursement processes. By utilizing the EDI 837P, 837I, and 837D formats, healthcare providers can ensure accurate and efficient submission of claims.
HealthEDI offers an intuitive interface designed to simplify the creation, translation, and management of EDI 837 transactions. Featuring robust data mapping capabilities, the solution enables organizations to seamlessly map healthcare claims data to the EDI 837 format, ensuring accuracy and efficiency throughout the process. The EDI solution supports the creation of EDI messages in ANSI X12 standards, ensuring HIPAA compliance and interoperability across healthcare systems.
For organizations looking to streamline their healthcare claims processing and maintain compliance with multiple EDI standards, HealthEDI is the ideal solution. Schedule a personalized demo to experience firsthand how HealthEDI can optimize your healthcare claims management or contact our team for more information.
Automate Your EDI 837 Flows with HealthEDI
Streamline EDI 837 file exchange. Explore a no-code HIPAA-compliant solution for seamless healthcare EDI transactions.