Back to Pilotfish Home

EDI Parsing and Validation FAQ

EDI Parsing and Validation Questions

1. What is HIPAA SNIP Validation?

HIPAA SNIP validation is applied to X12 EDI documents to ensure the EDI data is HIPAA-compliant. Each succeeding WEDI-SNIP Type 1-7 increases the strictness of data constraints. Support of the higher SNIP levels (SNIP Types 4-7) in an EDI solution helps to ensure robust validation and HIPAA EDI compliance checks.

2. How are EDI X12 files validated?

Several parts of an EDI message can have problems that corrupt or invalidate the message contents. The EDI specification includes SNIP Types 1-7 (SNIP Levels) that define checks to make sure a given EDI message is EDI compliant and passes specific criteria for being well-formed. PilotFish provides SNIP validation out-of-the-box for Types 1-3 and Types 4-7 as an add-on. An additional EDI SNIP Validation Processor provides a preliminary overall sanity check.

3. How do you map and validate EDI 837 claim transactions to a database using an integration engine?

An Integration engine, or interface engine, allows you to send and receive messages, convert them to XML or another common format, validate them and map the contents of the EDI 837 transaction to a database. You can also create and generate the EDI 999 acknowledgment. To see this process in action with PilotFish’s Integration Engine watch the EDI 837 Claims Processing Integration video.

EDI X12 Tools for Integration Video

EDI 837 Claims Processing Integration

4. What tool parses EDI 837 and EDI 835 data to an SQL database?

Pilotfish’s eiConsole Interface Engine can configure interfaces to parse EDI 835 and EDI 837 messages and transform them into SQL inserts. Read more about X12 EDI Parsing.

5. How do you build EDI 270 transactions?

In the PilotFish Data Mapper, EDI messages can be graphically constructed into specific XML representations that the EDI Transformation Module can then convert into properly structured EDI messages.

6. Can the eiConsole for X12 by PilotFish map EDI 837, EDI 278 and other transactions to FHIR resources?

Yes, the PilotFish Mapper in the eiConsole for X12 can map any X12 or EDI transaction to any target transaction, resources such as FHIR, and API’s. The Data Mapper can also connect and map directly to SQL database tables.

7. How does EDI integration work?

Interface engines integrate EDI data formats to target systems by transforming them first into a common format. EDI mapping is how the EDI source data is mapped from a common form to related target data fields, converted and output as XML, Excel, JSON, other EDI formats and other specified formats.

8. Can I create EDI inquiry file (270/271) from Excel data?

Yes, as long as the XLS file has all the data needed to generate X12 EDI 270/271 transactions you can use PilotFish to map the Excel fields to the 270/271 fields using XML and XSLT. Then you can transform the XML to EDI. You can do this for any X12 transaction.

9. What tool will validate EDI SNIP 1 and 2 files and debug exceptions in those files coming from our customers?

We recommend the eiConsole with the X12 EDI bundle (the bundle can be selected when you download the software or a free trial). The eiConsole can handle SNIP Type 1-7 (SNIP Level 1-7) validations.

This is a unique website which will require a more modern browser to work! Please upgrade today!