EDI X12 Tools Exclusively in the eiConsole
The PilotFish EDI X12 Integration Engine Solution offers fully-featured integrated components built into the eiConsole for X12’s exclusive graphical automated interface assembly line process. PilotFish’s eiConsole for X12 includes more EDI X12 specific functionality and tools for EDI transformation than any other product on the market. With PilotFish, unlike competitors, there is no additional cost to access components or features.
Out-of-the-box, PilotFish effortlessly handles trading partner versions of the X12 transactions, HIPAA X12 data formats and rules, conversion to XML, output in any format, and any communication protocol. No coding or scripting is required. No matter how complex, integrations are handled by the same methodology with PilotFish each and every time – removing the dependency on who created an interface.
PilotFish’s EDI middleware is being leveraged throughout healthcare – for claims processing, authorizations, benefit enrollments, eligibility requirements, acknowledgments and more.
The eiConsole’s 7-stage graphical automated assembly line process and visual drag & drop Data Mapper deliver unrivaled and proven ease-of-use. Business users can easily accomplish up to 90% of configuration.
Robustly architected with features, extensibility, scalability, and performance you can count on, PilotFish is the only EDI X12 Interface Engine that includes this complete integrated suite of EDI X12 integration tools.
PilotFish’s EDI X12 Built-In Components and Integration Tools
As a select distribution partner of X12 and with access to X12 standards artifacts, PilotFish is able to deliver the industry’s most robust solution for rapid and efficient parsing, mapping, validation and production of any X12 standards message.
EDI X12 Format Builder
Provides automatic processes to parse and read in any EDI X12 transactions
The eiConsole’s Format Builder loads a rich data dictionary for EDI transactions. The Format Builder includes field-level documentation and the friendly field names option. Source EDI X12 is validated while parsing.
EDI X12 Friendly Names Option
Provides human-readable names for “cryptic” EDI records and segments
With the eiConsole’s Friendly Name option, EDI elements can be augmented with human readable, descriptive names as outlined in the HIPAA implementation guides. The Friendly Names feature provides much-needed context when working with large EDI files or those with many repeating loops.
Lenient EDI X12 Parser
Easily consumes highly variable compliant and non-compliant EDI X12
PilotFish’s powerful lenient EDI X12 Parser, an EDI transformation module, easily navigates the complexities and variability encountered in HIPAA EDI X12 transaction sets and sub-sets, trading partner variation and non-compliant EDI. The lenient parser can parse unknown segments and capture data for subsequent conversion and manipulation. The lenient EDI X12 Parser identifies, flags and/or fixes errors, incorrect values, incorrect segment and element usages, etc.
EDI X12 Inline Documentation
Saves time with inline documentation easy access and convenience
PilotFish’s eiConsole provides implementation-specific inline documentation and context to ease the mapping process. When selecting an EDI segment or element, the ‘Doc’ tab will provide notes relating to the meaning of that element. The ‘Codes’ tab will describe acceptable coded values for that element, as well as provide an additional description.
EDI X12 Looping Contexts
Inclusion of Looping Contexts aids and organizes EDI-XML and XML-EDI mapping
PilotFish’s eiConsole includes looping contexts as specified in the X12 EDI HIPAA implementation guides. These loops help to organize the XML that is produced, as well as provide a more complete representation of the EDI being transformed. This enhanced XML structure is also very helpful in mapping EDI-XML in PilotFish’s visual drag & drop Data Mapper.
Validates X12 messages during processing for structure and SNIP 1-3
SNIP validations are applied to incoming EDI as it is processed in PilotFish’s eiConsole. The eiConsole currently supports the SNIP types that are defined entirely in the X12 TR3 Table Data, which includes validation types 1-3.
EDI X12 Interface Reuse
Interface templates and vendor-specific samples speed up EDI X12 mapping
PilotFish’s eiConsole enables multiple patterns for reuse including: cloning & tweaking existing interfaces; utilizing a library of existing templates to select the closest to what is required for a new interface; using an existing interface as-is for multiple integration points and chaining “standard” interfaces with implementation-specific variants.
EDI X12 Inline Testing & Debugging
Enables testing at any stage in the transformation process
PilotFish’s inline graphical testing and debugging component allows users to test and debug directly from the eiConsole with no extra hardware as well as no “wait time” for compilation and deployment. Testing can be started or stopped at any stage. Test results and errors can be viewed at any stage. The eiConsole supports complete inline end-to-end integration testing of developed interfaces before deployment.
EDI X12 Data Mapper XSLT View
Enables toggle to XSLT view of mapping if desired
The XSLT view in PilotFish’s EDI X12 Visual Data Mapper lets users work in XSLT if and when desired, with changes made immediately available in the graphical view.
PilotFish’s eiConsole for EDI X12 simplifies and streamlines EDI transformations and integration, automating repeatable tasks and significantly speeding up implementation and deployment. PilotFish implementations typically take a few weeks, not months upon months. Interfaces going forward can often be configured in less than 30 minutes.
Leading organizations in virtually every area of healthcare are benefitting from PilotFish. We invite you to learn more by visiting the EDI Case Studies section.