Simplifying X12 EDI Integration with an Engine that Understands the Standard

The eiConsole for X12 EDI handles any X12 transaction using the same Assembly Line and mapping tools. The video uses representative healthcare X12 examples, yet the same approach applies to enrollment claims, payments, supply chain and other X12 based exchanges.

PilotFish supports SNIP 1–3 out of the box, with additional support for SNIP 4–7 as an add-on through the EDI SNIP Validation Processor. This allows you to enforce structural, situational and semantic checks, along with external code set validation.

Yes. The X12 EDI parser can process non-standard compliant EDI. You can import partner samples, build maps around their specific dialect and still take advantage of validation mapping and monitoring.

No. The eiConsole is designed so that much of the work is configuration driven. Analysts use the Assembly Line UI visual mappers and drop-down selectors. Developers still have full access to the generated XSLT and configuration files when custom logic is required.

You configure and test routes in eiConsole, then promote configuration files to the eiPlatform runtime. eiPlatform runs routes unattended, supports hot deployment and integrates with eiDashboard for monitoring, reporting and alerting. This fits well into Docker based deployments.

The Integration Engine with Built-In Knowledge of X12 EDI Schemas and Standards

For over 24 years, PilotFish, a leader in integration engine and EDI solutions, has been helping organizations connect and exchange data with disparate systems. For more than 35 years, X12 has been developing and maintaining EDI standards plus XML schemas. PilotFish is pleased to announce both its partnership with X12 and the eiConsole for X12 EDI.

This offering combines PilotFish best of breed data transformation and mapping components with X12 standards artifacts to create a powerful X12 EDI software solution.

Parse, Validate Map and Produce EDI Files and Documents

The eiConsole for X12 hides much of the technical complexity involved in parsing, validating, mapping and producing X12 EDI files and documents.

PilotFish provides SNIP validation out of the box for Types 1–3, with Types 4–7 available as an add-on. With these capabilities, the eiConsole becomes a single tool that can validate healthcare X12 EDI data, translate it and map it to or from any other application.

The eiConsole lets you integrate with any database, system, device or application. It is system, platform and database agnostic and can be deployed on-site or in the cloud. The software is architected to handle the nuances of each industry’s information exchange and data semantics. The eiConsole for X12 extends this capability with comprehensive support for X12 EDI data.

The eiConsole also provides instant connectivity with a large library of built in connectors. When you need a protocol that is not in the library, you can add support using the Open API or the .NET bridge.

Configuring an EDI Interface in 7 Stages with the eiConsole

In the eiConsole, interfaces are configured using a graphical automated Assembly Line with no coding or scripting required. This approach makes data integration accessible enough that business analysts can perform up to 90 percent of interface development.

You start by configuring source and target systems. In the Source System stage, you choose from built in icons or add custom icons, then label the source so you can identify it later. In the Target stage, you select and label target icons and can add as many sources and targets as needed.

In the Listener stage, you select a connectivity protocol from a drop-down of built in connectors. Each connector has a configuration panel with default settings that make setup straightforward.

The Listener stage is also where processors are configured. Processors operate on all incoming data and can handle tasks such as encoding, changes, encryption, decryption, compression, decompression and metadata handling. More than 100 processors are built in, with the option to add custom ones.

PilotFish uses a common model approach. Once data is received in the Source Transform stage, it goes through a two-step conversion process. First, an automated transformer converts the raw content to XML when needed. Then the data is mapped using XSLT.

X12 EDI Transformation Module

Pre-built transformation modules can be configured through simple settings. These modules accept a wide range of standard data types and output XML. Among these modules is the EDI Transformation Module, which converts EDI to XML and allows XML validation during processing.

Validation for SNIP Types 1–7 is handled by the rules-driven EDI SNIP Validation Processor. SNIP Types 1–7 define checks that ensure each EDI message is compliant and well formed. PilotFish provides SNIP validation for Types 1–3 by default and makes Types 4–7 available as an add-on.

The eiConsole for X12 EDI parser can parse even nonstandard EDI, so you can work with feeds that do not strictly adhere to the specification. Once the Transformation Module is configured with SNIP validation, you move to the X12 EDI Data Mapper.

X12 EDI Data Mapper and X12 Format Builder

The eiConsole Data Mapper provides a three-pane graphical drag & drop mapping environment. The source tree appears on the left, the target on the right and the middle pane is where you define mappings and logic.

The mapper includes a palette of XSLT structures and functions. This palette allows you to implement conditional logic, looping and table based lookups as well as many other operations.

While the tool is graphical, the underlying artifacts are W3C-compliant XSLT. At any time, you can toggle between the graphical view and the code view.

Productivity tools in the Data Mapper include built in format readers. You can select the EDI format reader or others to instantly read data structures. From there, you choose a specific X12 transaction from a drop-down list. You can also build formats from internal data sources or from external schema files.

You can start mappings from scratch or generate a baseline by importing vendor specific examples. This makes it easier to meet each endpoint’s requirements.

The Data Mapper includes the Friendly Name Option, which provides human readable names for EDI records and segments. Inline documentation and code tabs help users who are less familiar with EDI.

A built in testing mode lets you load sample data and run tests. After testing, you return to the main route grid and continue configuration.

Routing and Monitoring EDI Transactions

After the Source Transform stage, you reach the Route stage. Here, you add routing rules that send transactions either to all targets or to selected targets based on XPath expressions.

You can also add Transaction Monitoring, which includes email alerts, error route triggers and SNMP traps.

In the Target Transform stage, you apply transformations that shape data to match each receiving system. As in the Source Transform stage, you can use transformation modules to read data or the Data Mapper to produce the desired target format.

In the Transport stage, a configuration panel opens where you choose from built in adapters such as Database SQL Transport, along with many other options.

Testing Your EDI Interface

Once the interface is configured, you can test it graphically end-to-end using Testing Mode. You can start or stop tests at any stage and view the output at each step. Testing Mode highlights errors so you can adjust the configuration and retest until the interface is ready for production.

After testing the eiConsole for X12 simplifies deployment. Configurations are stored as files on the file system. You can copy these files to another server, use the eiConsole drag and drop deployment, or deploy through the eiDashboard, which provides web-based operational reporting and management.

The eiConsole for X12 offers a broad range of EDI features and capabilities that significantly reduce the complexity of parsing, validating, mapping and producing EDI files.

Additional X12 EDI Information and Free Trial

For more information about PilotFish EDI tools, visit the X12 EDI Integration, EDI Parsing, and X12 EDI Data Mapping pages. You can also view the X12 EDI Tools Technical Video Demonstration and review X12 EDI case studies.

To experience the eiConsole for X12 EDI firsthand, download the free 90-day trial. The trial includes access to the EDI SNIP Validation Processor and EDI Identification Processor. With the Quick Start Tutorial, you can complete an end-to-end interface in less than 20 minutes and see how easy it is to work with the PilotFish integration engine.