Smart Mapping
Uses transaction-aware structured fields, labeled columns, supported loop ownership, and a defined row grain. It is easier to filter, summarize, validate, and export for downstream analysis.
EDI Parser
Parse supported X12 EDI files into structured, readable data with transaction-aware Smart Mapping or source-ordered Raw segments.
Up to 3 successfully processed files per day included. Failed, malformed, or unsupported attempts do not permanently consume the allowance. No account required.
Browser-local processing: EDI parsing and Smart Mapping run in the browser. EDI contents are not uploaded to or stored by the application server.
What does an EDI parser do?
Raw X12 is a sequence of segments and elements separated by characters declared in the file. An EDI file parser identifies those boundaries and makes the content readable by software.
For supported transactions, Smart Mapping goes further: it recognizes transaction structure, follows supported hierarchy and loop context, and turns source values into labeled fields and transaction-specific rows.
CLP*12345*1*500*420*80*12*PAYER123*11~Patient Control Number: 12345Claim Status Code: 1 — Processed as primaryCharge Amount: 500Payment Amount: 420Patient Responsibility Amount: 80
Synthetic example only. CLP01 is the patient/submitter control number; the payer claim control number is a different CLP element.
How EDI parsing works
- Select a file in the shared EDI application.
- Detect delimiters and read ordered segments and elements.
- Recognize the transaction and implementation where supported.
- Build Smart or Raw rows using the selected mode.
- Preview and export the resulting rows as needed.
Smart Mapping vs Raw segments
Both modes begin with the same browser-local segment parsing, but they answer different questions.
Raw segments
Preserves source order and exposes each segment tag and element without the transaction-specific Smart schema. Use it to inspect original segment breadth or content outside current mapped-field boundaries.
Support boundary: Smart Mapping is a bounded transaction-specific projection, not a lossless reconstruction or exhaustive implementation-guide parser. If transaction-specific Smart Mapping is unavailable, the application may fall back to source-ordered Raw segment output.
Preview structured EDI results
After parsing, the shared application shows labeled columns, transaction-specific rows, and total row and column metadata. Guest and Free users can inspect the first 100 rows; rows beyond the preview remain part of ordinary exports.
Structured rows keep related business values together so a human can compare claims, services, members, eligibility responses, or acknowledgments without manually counting element positions. Field labels also make it easier to spot blank values and scan repeated records. The preview represents the selected file and mode; it does not add data, infer values that are absent from the source, or certify that the transaction is compliant.
Readable output
Review detected output types, mapped field names, row counts, and a Compact Summary where that transaction supports one.
Useful exports
Download ordinary parsed data as CSV, Excel, JSON, or XML. Parsing structures the data; conversion serializes those rows into the selected file format.
Supported Smart Mapping transactions
The online EDI parser supports the following healthcare X12 transaction families under the current documented mapping boundaries.
Version-aware routing: Smart subtype mapping recognizes 837P X222A1, 837I X223A2, and 837D X224A2. Exact Smart routing applies to 834 X220A1, 270/271 X279A1, 277CA X214, and 999 X231/X231A1. The 835 mapper uses transaction-aware heuristic detection aligned to supported X221/X221A1 semantics. Other 837 references may retain shared generic claim context without subtype service mapping.
Parser, converter, validator, viewer, and editor
Parser vs converter
A parser interprets EDI into structured rows and fields. The EDI workspace then converts those rows into CSV, Excel, JSON, or XML.
Parser vs validator
The parser shows what structured data is present. The EDI Validator reports issues found by supported enabled checks.
Parser vs viewer
Smart Mapping provides transaction-aware interpretation. The EDI Viewer is focused on direct 835/837 segment and element inspection, including pasted text.
Parser vs editor
Parsing reads and structures data. Editing modifies the mapped representation; the full Data Editor is an advanced Pro workspace feature.
Pro adds unlimited product processing, the full Data Editor/workspace, Full Analysis, saved layouts, and validation-report exports. Pro does not change parser fidelity.
EDI parser FAQ
What is an EDI parser?
An EDI parser reads X12 segments and elements and turns supported transaction structures into labeled fields and rows that are easier to inspect and use.
What is the difference between Smart Mapping and Raw segments?
Smart Mapping applies transaction-aware structured fields for supported transactions. Raw segments preserve source order and expose each segment tag and element without the transaction-specific Smart schema.
Can I parse an EDI file without an account?
Yes. Guest access includes up to 3 successfully processed files per day without an account. Failed, malformed, or unsupported attempts do not permanently consume the allowance.
Which X12 transactions are supported?
Smart Mapping supports 835, 837P, 837I, 837D, 834, 270, 271, 277CA, 999, 850, 855, 810, 856, 940, 945, 997, 846, 852 under the current documented transaction and version boundaries.
Does parsing validate the file?
Parsing identifies and structures content. The separate validator applies enabled structural and transaction-specific checks to supported source and mapped output.
What is the difference between an EDI parser and converter?
Parsing interprets EDI into structured rows and fields. Conversion exports those rows into formats such as CSV, Excel, JSON, or XML.
Is my EDI file uploaded to the server?
EDI parsing and Smart Mapping run in the browser. EDI contents are not uploaded to or stored by the application server.
Can I export parsed EDI to CSV, Excel, JSON, or XML?
Yes. Ordinary parsed-data exports are available as CSV, Excel, JSON, and XML under the existing product allowance.