PilotFish Delivers Broad Support for X12 EDI Transaction Integration

The X12 EDI format was developed by ASC X12 (Accredited Standards Committee X12) and primarily serves the US industry. A surge in the number of end-users in insurance, finance, healthcare, government, pharmaceutical and medical device industries and others has fueled the growing demand for modern, cost-effective EDI integration solutions and services. As a select distribution partner of X12 and with access to X12 standards artifacts, PilotFish delivers the industry’s most robust solution for rapid and efficient parsing, mapping, validation and production of any X12 standards message.

PilotFish’s eiConsole for X12 EDI graphical Automated Interface Assembly Line process easily handles connecting Anything to Anything – including legacy systems and newer technologies. The built-in eiConsole for X12 EDI’s Data Mapper comes equipped with a powerful EDI Format Builder. Within the data mapper, users need only enter the external schema file or the external EDI file name of the transaction they want to work with. It is a simple process, taking just seconds to read in the transaction. Once the transaction set is loaded, users can begin the graphical drag & drop mapping process.

Note: For healthcare-specific X12 data integration, visit PilotFish’s Healthcare Focused Website.

Select an External Schema File or External EDI File to Read in the Transaction Format

X12 EDI usage involves message syntax and standard, messaging protocol and transports.

EDI messages consist of an envelope and a hierarchical series of structural elements. PilotFish’s graphical Automated Interface Assembly Line process at the Data Mapper stage using XML syntax makes it very easy to transform and exchange EDI formats by employing XSLT, the W3C standard language defined to enable transformations of XML documents.

Common Types of Supply Chain & Cross-Use Transactions

• EDI 180 Return Notification and Authorization
• EDI 810 Invoice
• EDI 820 Payment Order and Remittance Advice
• EDI 824 Application Advice
• EDI 832 Price/Sales Catalog
• EDI 846 Inventory Inquiry and Advice
• EDI 850 Purchase Order
• EDI 855 Purchase Order Acknowledgment
• EDI 856 Advance Shipping Notice
• EDI 860 Purchase Order Change
• EDI 864 Text Message
• EDI 997 Functional Acknowledgment
• EDI TA1 Interchange Acknowledgment

Building EDI 850 & 855 Interface

EDI Message Basics

EDI messages begin with a header identifying the kind of message being sent. That header is followed by a number of components called segments. These are provided in the sequence specified by the message specification. Each segment is further divided into fields, which contain a value using a data type specified by the standard.  Messages, segments and fields are delimited by special characters which vary depending upon the standard. Fields may be further subdivided into components and subcomponents.  A single segment or group of segments can repeat (these are called loops in the X12 world), allowing complex structures to be communicated.

Segments begin with a 2 or 3 letter code like ST or ISA. Some segments are mandatory, while some are not. The mandatory segments of X12 are:

• ISA – interchange header that contains information about the sender and recipient.
• GS – functional group header segment of a set of X12 documents of the same document type (transaction set): includes information (codes) about the functional group (sender, recipient, and date/time).
• ST – transaction set header segment marking the start of a transaction set.
• SE – transaction set trailer segment marking the end of a transaction set.
• GE – functional group trailer segment of the same transaction set -includes information on the number of functional groups and control group number (marks end of a group of transaction sets).
• IEA – end of the interchange – including interchange control reference number and information on the number of functional groups.

The hierarchical structure of an EDI message enables transaction sets/messages and groups to be batched. Even if an interchange contains only one transaction set/message and only one group, that interchange is structured with the same basic structural elements that it would have if it were batched, with the exception that there would not be multiple transaction set/message or group elements.

By embedding its in-depth knowledge of the X12 schemas and standards within the eiConsole and eiPlatform product suite, PilotFish delivers breakthrough productivity-boosting features that strip away the technical complexity of parsing, validating, mapping and producing X12 EDI files.

For more on PilotFish’s EDI tools and resources, go to X12 EDI Data Mapping and the main X12 EDI Integration page.

We invite you to take advantage of PilotFish’s full version, FREE 90-day Trial Download of the eiConsole for X12 EDI. Users can try out our new EDI Transformation Module and Format Builder. With the Quick Start Tutorial, users can complete an end-to-end interface in less than 20 minutes and get a real sense of the ease-of-use of PilotFish’s solutions and software. See detailed product documentation & tutorials in the PilotFish Online Resource Center.

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