Back to Pilotfish Home

EDI X12 Parsing

PilotFish Built-In EDI X12 Parser Converts Any EDI X12 File

PilotFish’s eiConsole for EDI X12 fully integrated components include its powerful built-in EDI X12 Parser. The PilotFish EDI X12 Interface Engine Solution offers fully-featured integrated components built into each stage of the eiConsole’s graphical Automated Interface Assembly Line process. With out-of-the-box functionality, the eiConsole has the capability to read, parse, validate and transform EDI X12 from any source or trading partner to XML. The eiConsole’s EDI X12 Parsing capabilities are exposed and enabled simply by selecting EDI Transformer via a drop-down in the graphical Interface Assembly Line’s Transformation Module.

Automated EDI X12 Parsing, Validation and Transformation to XML

The eiConsole for EDI X12 Transformation Module is intuitive, visual and understandable with no coding required. The EDI X12 Format Builder loads a rich data dictionary for EDI transactions. The Format Builder includes field-level documentation and friendly field names. Source EDI X12 is validated while parsing. Enhancements deal with additional details about the structure, such as loop contexts.

The powerful PilotFish EDI X12 Parser approach allows developers to focus on business logic rather than on how to parse arcane EDI formats. You will quickly find non-technical business users can do up to 90% of the configuration work. Going forward, interface reuse slashes timelines for implementations, updating and maintenance.


No-Problem Parsing EDI X12 Real World Deviations and Differences with PilotFish EDI X12 Parser

The built-in eiConsole EDI X12 Parser easily navigates the inherent complexities and variability encountered in EDI X12 transaction sets. While EDI X12 formats are based on the published standards – in the real world, deviations and differences between EDI X12 transactions are the norm.

 It is to be expected that EDI X12 transaction sets have acceptable deviations or subsets. Additionally, you can expect each EDI X12 transaction to be different per trading partner even though based on its X12 standard. You’re highly likely to have different segments in each set.

Additionally, some third parties you are working with maintain their own EDI implementation (companion) guides for vendors to follow. There are many allowable variations that would all result in “compliant” EDI X12.

The PilotFish Transform component takes whatever a particular source system gives you and successfully converts it to a common representation. The EDI X12 Transformer component converts EDI X12 messages to XML, performing parsing and validation along the way.


Easy Codeless Transformations of Your EDI X12 Data into XML 

EDI Parsing 837 XML Data Transformation

Configuration of the EDI X12 Transform stage is easy and fast.

Each source system specified in the assembly line process has its own source transform associated with it. Users start by specifying the EDI transaction’s TR3 table data for use in validation naming and structuring of data. Next, useful built-in features may be selected via drop-downs or click-on options. Here are just two:

Code Definitions – Users can enable code definitions to get more contextual information whenever EDI code values are used, such as in a REF or NM1 segment. (Note: These added code definitions will only be applied to those codes defined in the EDI X12 implementation guides and not any external code sets, like ICD-10 or national zip code sets.)


EDI to XML File Transformation with Descriptive Name Option

Useful built-in features may be selected via drop-downs or click-on options.

Friendly Naming – The Friendly Naming feature provides friendly human-readable names and meanings. The created XML via these options is very useful in allowing EDI messages to be understood easily.


Looping “No Issue” with Loop Contexts Enhancements

Looping contexts (as specified in the EDI X12 implementation guides) are included and used by the PilotFish X12 Parser. EDI X12 Implementation Guides stipulate the exact format for each EDI X12 transaction set, such as medical claims or invoices. The EDI file structure contains loops, segments, elements and composite elements. Loops contain segments, a segment contains data elements and elements may contain other elements (composite elements). The rules govern: 

  • Blocks of segments grouped together and known as loops
  • Sequence and positions at which segments or loops can appear
  • Number of times a segment or a loop can repeat at the same position
  • Whether a segment or a loop is mandatory or optional

These loops help to organize the XML that is produced by the PilotFish EDI X12 Transformation module, as well as provide a more complete representation of the EDI being transformed. This enhanced XML structure is also very helpful when mapping the EDI-XML in the eiConsole for X12 Data Mapper.


Leverage Built-In Automatic SNIP Validations

PilotFish’s X12 Parser leverages built-in support to automatically perform SNIP validations to incoming EDI as it is processed, including Type 1 – integrity testing, Type 2 – requirement testing & Type 3 – balancing. For example, adding up all the values for claims and then specifying how you want those validation results to be produced. With this enhanced functionality, compliance issues in the data can be flagged for faster identification and correction.


SNIP Validation Level Selection in EDI X12 Transaction Processing

Automatically perform SNIP validations to incoming EDI as it is processed

Each level can be applied independently, though Type 1 (basic EDI syntax checking) is recommended by default when applying higher levels. Normally when a violation is encountered, the EDI X12 Transformer will throw an error and end. Checking the ‘Add elements for violation errors’ option in configuration will instead add additional XML elements describing the SNIP validation, where it occurred and what the offending data was. This way, minor errors in element values won’t result in outright rejection and can be dealt with as needed. This validation error information is also necessary for producing meaningful 999 acknowledgment messages.


Speed Up Configurations and Save 1000’s of Hours in EDI X12 Integrations

Once the PilotFish EDI Transformer is configured, it’s ready to convert your source EDI X12 data to XML.

You can rely on the PilotFish EDI X12 Parser to have dealt with parsing issues of compliant or non-compliant EDI X12 transactions. PilotFish’s EDI X12 Parser processes will identify errors, incorrect values, incorrect segment and element usages, etc. PilotFish’s EDI parsing, validating and transformation functionality helps you take steps to ensure quality, yet not slow down production.

For more than 18 years, PilotFish has successfully met the thousands of challenges (large and small) of EDI X12 interface configuration and implementation in the healthcare ecosystem. Experience the ease-of-use and dramatically speed up configurations with the PilotFish EDI X12 Interface Engine’s built-in Transform Module and EDI X12 Parser. We invite you to take advantage of PilotFish’s eiConsole for EDI X12 by downloading a full FREE 90-Day Trial Version of our software.

For more information please call us at 813 864 8662 or click the link below to email us.

X12, chartered by the American National Standards Institute for more than 35 years, develops and maintains EDI standards and XML schemas.

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