Export Format Reference

Detailed specifications for each export format available in EDI Paisan.

EDI File Format

Downloaded EDI files are valid X12 documents.

File Extension

.edi — Standard EDI extension
.txt — Alternative text extension
.x12 — X12-specific extension

All contain the same content; choose based on your system's requirements.

Formatting Options

Option	Result
Standard	Continuous string, segments separated by `~` only
Line breaks	Newline after each segment terminator

Standard Format

ISA*00*          *00*          *ZZ*SENDER         *ZZ*RECEIVER       *240120*0800*^*00501*000000001*0*P*:~GS*HC*SENDER*RECEIVER*20240120*0800*1*X*005010X222A1~ST*837*0001*005010X222A1~...

Line Break Format

ISA*00*          *00*          *ZZ*SENDER         *ZZ*RECEIVER       *240120*0800*^*00501*000000001*0*P*:~
GS*HC*SENDER*RECEIVER*20240120*0800*1*X*005010X222A1~
ST*837*0001*005010X222A1~
...

Character Encoding

UTF-8 — Default encoding
ASCII — Pure 7-bit ASCII for maximum compatibility

EDI files use ASCII characters; UTF-8 is backward-compatible.

JSON Format

Structured JSON representation of parsed EDI data.

Full Parse Result

Complete structure preserving all data and hierarchy:

json

{
  "meta": {
    "fileType": "837P",
    "version": "005010X222A1",
    "parsedAt": "2024-01-20T15:30:00Z",
    "parser": "edipaisan-1.0"
  },
  "interchanges": [
    {
      "header": {
        "ISA01": "00",
        "ISA02": "          ",
        "ISA03": "00",
        "ISA04": "          ",
        "ISA05": "ZZ",
        "ISA06": "SENDER         ",
        "ISA07": "ZZ",
        "ISA08": "RECEIVER       ",
        "ISA09": "240120",
        "ISA10": "0800",
        "ISA11": "^",
        "ISA12": "00501",
        "ISA13": "000000001",
        "ISA14": "0",
        "ISA15": "P",
        "ISA16": ":"
      },
      "controlNumber": "000000001",
      "functionalGroups": [
        {
          "header": {
            "GS01": "HC",
            "GS02": "SENDER",
            "GS03": "RECEIVER",
            "GS04": "20240120",
            "GS05": "0800",
            "GS06": "1",
            "GS07": "X",
            "GS08": "005010X222A1"
          },
          "controlNumber": "1",
          "transactions": [
            {
              "controlNumber": "0001",
              "type": "837",
              "segments": [...],
              "loops": {...}
            }
          ]
        }
      ]
    }
  ],
  "summary": {
    "interchangeCount": 1,
    "groupCount": 1,
    "transactionCount": 1,
    "segmentCount": 156,
    "claimCount": 3,
    "serviceLineCount": 12,
    "totalCharges": 4500.00
  },
  "validation": {
    "valid": true,
    "errors": [],
    "warnings": [
      {
        "segment": "NM1",
        "position": 45,
        "code": "W001",
        "message": "Middle name not provided"
      }
    ]
  }
}

Structure Only

Hierarchical outline without raw data:

json

{
  "fileType": "837P",
  "structure": {
    "ISA": {
      "GS": {
        "ST": {
          "Loop 1000A": ["NM1", "N3", "N4", "PER"],
          "Loop 1000B": ["NM1"],
          "Loop 2000A": {
            "HL": "Billing Provider",
            "Loop 2010AA": ["NM1", "N3", "N4", "REF"],
            "Loop 2000B": {
              "HL": "Subscriber",
              "Loop 2010BA": ["NM1", "DMG"],
              "Loop 2010BB": ["NM1"],
              "Loop 2300": {
                "CLM": "Claim",
                "DTP": "Dates",
                "Loop 2400": ["LX", "SV1", "DTP"]
              }
            }
          }
        }
      }
    }
  }
}

File Summary

Statistics and metadata only:

json

{
  "fileName": "claims_batch_2024-01-20.edi",
  "fileSize": 45678,
  "fileType": "837P",
  "version": "005010X222A1",
  "created": "2024-01-20T08:00:00",
  "statistics": {
    "interchanges": 1,
    "functionalGroups": 1,
    "transactions": 1,
    "claims": 47,
    "serviceLines": 123,
    "uniquePatients": 42,
    "uniqueProviders": 3,
    "totalCharges": 125000.00,
    "dateRange": {
      "earliest": "2024-01-01",
      "latest": "2024-01-15"
    }
  },
  "validation": {
    "valid": true,
    "errorCount": 0,
    "warningCount": 2
  }
}

XML Format

Structured XML representation of parsed EDI data. Mirrors the JSON export with identical data in XML syntax using kebab-case tag names.

Tag Naming

Object properties are converted from camelCase to kebab-case:

JSON Property	XML Tag
`controlNumber`	`<control-number>`
`functionalGroups`	`<functional-groups>`
`byteOffset`	`<byte-offset>`

Arrays use singular child tags: <segments> contains <segment> elements.

Full Parse Result

xml

<?xml version="1.0" encoding="UTF-8"?>
<edi-export>
  <metadata>
    <exported-at>2026-03-23T15:30:00.000Z</exported-at>
    <format>edi-parse-result</format>
    <version>1.0</version>
  </metadata>
  <data>
    <parse-result>
      <delimiters>
        <element>*</element>
        <component>:</component>
        <segment>~</segment>
      </delimiters>
      <segments>
        <segment>
          <id>ISA</id>
          <elements>
            <element>ISA</element>
            <element>00</element>
            <!-- ... -->
          </elements>
          <raw-text>ISA*00*...</raw-text>
          <index>0</index>
          <byte-offset>0</byte-offset>
          <byte-length>106</byte-length>
        </segment>
      </segments>
      <interchanges>
        <interchange>
          <control-number>000000001</control-number>
          <sender-id>SENDER</sender-id>
          <receiver-id>RECEIVER</receiver-id>
          <functional-groups>
            <functional-group>
              <control-number>1</control-number>
              <functional-id>HC</functional-id>
              <transaction-sets>
                <transaction-set>
                  <control-number>0001</control-number>
                  <type>837</type>
                </transaction-set>
              </transaction-sets>
            </functional-group>
          </functional-groups>
        </interchange>
      </interchanges>
      <errors/>
    </parse-result>
  </data>
</edi-export>

File Summary

xml

<?xml version="1.0" encoding="UTF-8"?>
<edi-export>
  <metadata>
    <exported-at>2026-03-23T15:30:00.000Z</exported-at>
    <format>edi-file-summary</format>
    <version>1.0</version>
  </metadata>
  <data>
    <file-summary>
      <file-name>claims_batch.edi</file-name>
      <file-size>45678</file-size>
      <counts>
        <interchanges>1</interchanges>
        <functional-groups>1</functional-groups>
        <transaction-sets>1</transaction-sets>
        <segments>156</segments>
        <claims>47</claims>
        <service-lines>123</service-lines>
      </counts>
      <validation>
        <error-count>0</error-count>
        <warning-count>2</warning-count>
        <is-valid>true</is-valid>
      </validation>
    </file-summary>
  </data>
</edi-export>

For more details and use cases, see the XML Export guide.

CSV Format

Tabular data for spreadsheets and databases. CSV export is currently available for 835 remittance files only.

General Specifications

Delimiter: Comma (,)
Text qualifier: Double quote (")
Line ending: CRLF (\r\n) for Windows compatibility
Encoding: UTF-8 with BOM (for Excel)
Header row: Always included

835 Payment CSV Schemas

Claims Export

Column	Description	Example
`claim_id`	Provider's claim identifier	CLM001
`payer_claim_id`	Payer's control number	123456789
`patient_name`	Patient full name	SMITH, JOHN
`patient_id`	Member ID	MEM123456
`service_date`	Date of service	2024-01-10
`billed_amount`	Total charges	1500.00
`allowed_amount`	Payer's allowed	1350.00
`paid_amount`	Amount paid	1200.00
`patient_resp`	Patient responsibility	150.00
`adjustment_total`	Total adjustments	150.00
`status_code`	Claim status	1
`status`	Status description	Processed Primary

Service Lines Export

Column	Description	Example
`claim_id`	Parent claim ID	CLM001
`line_number`	Service line #	1
`procedure_code`	CPT/HCPCS	99213
`modifier_1`	Primary modifier	25
`modifier_2`	Secondary modifier
`service_date`	Date of service	2024-01-10
`units`	Quantity	1
`billed_amount`	Line charges	125.00
`allowed_amount`	Allowed	112.50
`paid_amount`	Paid	100.00
`adjustment_amount`	Adjustments	25.00

Adjustments Export

Column	Description	Example
`claim_id`	Claim ID	CLM001
`line_number`	Service line (0=claim level)	1
`group_code`	Adjustment category	CO
`reason_code`	CARC code	45
`reason_desc`	CARC description	Charges exceed fee schedule
`amount`	Adjustment amount	25.00
`remark_code`	RARC code	N130
`remark_desc`	RARC description	Consult payer website

PDF Format

Printable reports generated via your browser's print dialog.

How it works: EDI Paisan renders reports as formatted HTML. Use your browser's Print function (Ctrl+P / Cmd+P) to save as PDF or print directly. This approach works across all browsers without requiring additional software.

Specifications

Page size: Letter (8.5" x 11")
Margins: 0.75" all sides
Font: Sans-serif (Arial/Helvetica)
Color: Monochrome-friendly

Report Sections

┌─────────────────────────────────────────────┐
│  EDI Paisan                                 │
│  [Report Type] Summary                      │
│  Generated: January 20, 2024 3:30 PM        │
└─────────────────────────────────────────────┘

Content (varies by report type)

Tables, summaries, and detailed breakdowns as applicable.

┌─────────────────────────────────────────────┐
│  Page 1 of 3        Generated by EDI Paisan │
└─────────────────────────────────────────────┘

Import Compatibility

JSON

Node.js: JSON.parse()
Python: json.loads()
Java: Jackson, Gson
C#: System.Text.Json

XML

Java: JAXB, DOM4J, Jackson XML
C#/.NET: System.Xml, XDocument
Python: xml.etree.ElementTree, lxml
XSLT: Apply transformations with any XSLT processor
XPath: Query with standard XPath expressions

CSV

Excel: Open directly or Data → From Text/CSV
Google Sheets: File → Import
Python: pandas.read_csv()
SQL: LOAD DATA INFILE or import wizard

EDI

Standard X12 parsers
Clearinghouse portals
Practice management systems

Export Options Overview — When to use each format
Pro Tier — Export features included

Export Format Reference ​

EDI File Format ​

File Extension ​

Formatting Options ​

Standard Format ​

Line Break Format ​

Character Encoding ​

JSON Format ​

Full Parse Result ​

Structure Only ​

File Summary ​

XML Format ​

Tag Naming ​

Full Parse Result ​

File Summary ​

CSV Format ​

General Specifications ​

835 Payment CSV Schemas ​

Claims Export ​

Service Lines Export ​

Adjustments Export ​

PDF Format ​

Specifications ​

Report Sections ​

Header ​

Content (varies by report type) ​

Footer ​

Import Compatibility ​

JSON ​

XML ​

CSV ​

EDI ​

Related Documentation ​

Export Format Reference

EDI File Format

File Extension

Formatting Options

Standard Format

Line Break Format

Character Encoding

JSON Format

Full Parse Result

Structure Only

File Summary

XML Format

Tag Naming

Full Parse Result

File Summary

CSV Format

General Specifications

835 Payment CSV Schemas

Claims Export

Service Lines Export

Adjustments Export

PDF Format

Specifications

Report Sections

Header

Content (varies by report type)

Footer

Import Compatibility

JSON

XML

CSV

EDI

Related Documentation