X12 EDI File Viewer for Healthcare Transactions
The viewer renders 835 (ERA) and 837 (claim) files in a user-friendly format without EDI artifacts. All other transactions are rendered as a list of EDI segments. You can see many examples of various EDI file types here.
Note: This version of the viewer has a file size limit and other limitations.
Sign up for a trial of an unrestricted HIPAA-compliant version.
You can see the demo of the unrestricted version here.
Upload your X12 EDI file and click “Parse.” You can also copy/paste your EDI text into the text box below. Click “Download CSV” to convert your EDI to CSV. You can find the explanation of the CSV columns here.
Interested in parsing/converting X12 EDI files to JSON/CSV in bulk? Check out our EDI converters and parsers; you can use our API or the command line tool.
What’s new:
- Attachment (PWK) columns are now part of the export.
- You can now export/convert 835/837 directly to Excel format without having to go through CSV. Click “Download CSV/Excel” and select an Excel option.
- Total adjustment amount column in the payment list; rendering of assignment participation code, delay reason code and other fields.
- CSV column description and X12 EDI mapping (data dictionary) for 835 and 837P
- Improved parsing of 810 and many other non-healthcare transactions.
- Improved reporting of parsing warnings with segment and line numbers
- CSV export for 837I (institutional/hospital claims)
- DRG and other institutional columns in the CSV file layout for 835
- New release of our EDI Converter with the ability to customize CSV output format.
- You can now export only key fields for 835 and 837, select “Download CSV/Key Fields”
- Conversion to CSV/Excel, with the support for 835 and 837P, directly from the UI
Note on data privacy and HIPAA: We do not store uploaded files. They are deleted automatically as soon as a file is rendered.
However, this is a free tool; do not use it to view PHI. Consider upgrading to out paid version instead.
Note on copy/paste EDI fragments: if the ISA segment is not part of the input, the parser will use * as the element separator, ~ as the segment terminator, and : as the component element separator.
We’re constantly improving the viewer; please sign up for our updates below: