Appearance
XML Export
Export your parsed EDI data as well-formed XML documents. XML export mirrors the JSON export feature — same data, same structure — in a format suited for enterprise systems, XSLT transformations, and XML-native workflows.
Overview
| Attribute | Details |
|---|---|
| Tier | Pro |
| File Types | All (837P, 837I, 835, 270, 271, 999) |
| Preview | Free — first 250 lines visible before download |
| Processing | Client-side (your data never leaves the browser) |
Export Types
| Type | Contents | Use Case |
|---|---|---|
| Full Parse Result | Complete structure with all segments, elements, hierarchy | System integration, data transformation |
| Structure Only | Hierarchical outline without raw segment data | File structure analysis, documentation |
| File Summary | Statistics, counts, validation results | Reporting, dashboards |
| Split Metadata | Information about split chunks (when applicable) | Batch tracking |
How to Access
- Load an EDI file
- Click Export in the toolbar
- Scroll to the XML Export section
- Click one of the export options
Preview Before Download
For Full Parse Result, clicking the button opens a preview modal showing the first 250 lines of the generated XML. This lets you inspect the output before downloading.
- Free tier: Preview is visible with a watermark. Upgrade to Pro to download.
- Pro tier: Preview plus full download button.
XML Structure
All XML exports include an XML declaration and optional metadata wrapper.
Metadata Envelope
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>
<!-- Full parsed data here -->
</parse-result>
</data>
</edi-export>Full Parse Result Example
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>
<element> </element>
<!-- ... all ISA elements ... -->
</elements>
<raw-text>ISA*00* *00*...</raw-text>
<index>0</index>
<byte-offset>0</byte-offset>
<byte-length>106</byte-length>
</segment>
<!-- ... all segments ... -->
</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>
<segment-count>156</segment-count>
</transaction-set>
</transaction-sets>
</functional-group>
</functional-groups>
</interchange>
</interchanges>
<errors/>
</parse-result>
</data>
</edi-export>Structure Only Example
xml
<?xml version="1.0" encoding="UTF-8"?>
<edi-export>
<metadata>
<exported-at>2026-03-23T15:30:00.000Z</exported-at>
<format>edi-structure</format>
<version>1.0</version>
</metadata>
<data>
<structure>
<delimiters>
<element>*</element>
<component>:</component>
<segment>~</segment>
</delimiters>
<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>
<segment-count>156</segment-count>
</transaction-set>
</transaction-sets>
</functional-group>
</functional-groups>
</interchange>
</interchanges>
<total-segments>156</total-segments>
<errors/>
</structure>
</data>
</edi-export>File Summary Example
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>
<transaction-types>
<transaction-type>
<type>837</type>
<count>1</count>
</transaction-type>
</transaction-types>
<validation>
<error-count>0</error-count>
<warning-count>2</warning-count>
<is-valid>true</is-valid>
</validation>
</file-summary>
</data>
</edi-export>Tag Naming Convention
XML tags use kebab-case converted from the JSON property names:
| JSON Property | XML Tag |
|---|---|
controlNumber | <control-number> |
senderId | <sender-id> |
functionalGroups | <functional-groups> |
byteOffset | <byte-offset> |
rawText | <raw-text> |
transactionSets | <transaction-sets> |
Array items use the singular form of the parent tag:
<segments>contains<segment>children<interchanges>contains<interchange>children<errors>contains<error>children
Use Cases
- Enterprise integration — Feed into systems that consume XML (HL7, FHIR adapters, ESBs)
- XSLT transformation — Apply stylesheets to transform EDI data into custom formats
- Reporting — Import into XML-native reporting tools
- Archival — Self-describing format with metadata envelope
- Interoperability — Exchange parsed EDI data with XML-based trading partners
JSON vs. XML: Which to Choose?
| Factor | JSON | XML |
|---|---|---|
| File size | Smaller | Larger (~2x) |
| Web/JavaScript | Native | Requires parsing |
| Enterprise/Java/.NET | Supported | Native |
| XSLT/XPath | Not supported | Full support |
| Human readability | Good | Good |
| Schema validation | JSON Schema | XSD |
Choose JSON for web apps, APIs, and JavaScript-based workflows. Choose XML for enterprise systems, XSLT pipelines, and XML-native tools.
Related Documentation
- Export Options Overview — All export formats
- Export Formats Reference — Detailed format specs
- Pro Tier — Export features included