If you’re not familiar with Electronic Data Interchange (EDI) format, it can be difficult to work with (to say the least). It’s no wonder we get asked all the time if we can convert EDI to Excel or tables or spreadsheets. We’re always up for a good EDI challenge, so we decided to develop a pre-built translator to map EDI messages to Excel. This tool was developed for those working with healthcare 5010 payment and claims.
Here’s how you would go about translating Excel to EDI or vise versa.
Many of our clients are interested in this for reporting on or correlating 837 and 835 data, claim balancing, or repricing. We developed our own Excel spreadsheet layout as the starting point for the EDI translation. If you can arrange for encounter data into the Excel columns of our T-Connect spreadsheet, you can produce a valid EDI file. We set up a folder where your team can drop in an Excel file and receive and EDI file.
Option 1: Go from T-Connect Excel tables to EDI using our pre-built map.
Use the T-Connect SDK C# EDI Parser to translate from a spreadsheet to Excel.
The T-Connect Healthcare Software Development Kit (SDK) comes with our parsing engine, validation, and prebuilt maps to and from excel. Simply arrange your data in our T-Connect spreadsheet format and drop it in the translator folder to receive a valid EDI X12 File. This ideal for enabling those less familiar with EDI format so they can make modifications in excel then translate back to EDI or vise versa.
Option 2: C# Developers can work with our powerful EDI object model to access our parsing and validation tools.
The field names match industry standards of the TR3 specs. This saves developers time spent looking up values. We also provide searching and traversing methods not available in other products. We make it super easy to access data elements.
Just upload an existing EDI X12 file. T-Connect SDK parses it into our X12 object model structure for C# developers. Then you can code against the various segments, loops, and data elements. T-Connect will automatically apply your edits and write out your new X12 EDI file!
Option 3: For C# developers that are not as familiar with EDI, we have created a Line of Business C# object library.
When you’re not familiar with the typical X12 EDI file syntax translating EDI files can be very time consuming. That’s why we created our Line of Business Object to provide more familiar data labels such as ‘Subscriberid’ instead of the EDI 200B. This makes coding against the API easy and efficient.
Just code against our LOB. Set your fields and logic with easily understood object naming conventions (Non-X12). T-Connect SDK automatically maps to our X12 object model. Then it writes out the new ANSI X12 EDI file. This can also be done in reverse order taking existing EDI files to an LOB object.
We feel we have the best EDI C# parser on the market. Healthcare developers get excited talking about our products, we’d be happy to show you why in a live demo or trial of T-Connect SDK.