Video Key Moments

• 00:00 EDI SNIP4+ overview
• 00:37 EDI SNIP4+ workflow
• 00:54 SNIP 1-7 validation
• 01:01 EDI Codes Database
• 01:28 Assembly line process
• 02:01 Any source to target
• 02:30 Data mapping
• 03:30 Inline testing mode

X12 EDI HIPAA Integration: eiSuite EDI SNIP4+

eiSuite EDI SNIP4+ is a solution suite for X12 EDI HIPAA data integration that combines thorough validation, optional external code set maintenance and support for healthcare X12 EDI transactions.

[Try the Free 90-day Trial]     [Talk to an Expert]

Inside the SNIP4+ Pipeline

SNIP Rules Validation

• During SNIP validation, a rules file defining SNIP rules is parsed during validation
• The rules file is generated from X12 schemas and documentation and is included inside the SNIP Validation Processor

External Code Set Maintenance Option

• The EDI Codes Database is a separate application offered via an optional yearly subscription
• It continuously polls for code sets used during SNIP validation
• When updates are found, they are pushed to the server, curated and generated into a code file used in the eiConsole configuration of the SNIP Validation Processor

Operational Visibility with eiDashboard

• eiDashboard is positioned as part of the workflow where a message is transformed to XML and then validated before being sent out of the system
• The page also describes real-time operational insights with dynamic reporting and data visualization tools

Supported Healthcare X12 EDI Transaction Sets

eiSuite EDI SNIP4+ supports healthcare X12 EDI transaction sets including: EDI 270, 271, 275, 276, 277, 278, 820, 824, 834, 835, 837-P, 837-D, 997, 999 and TA1

Build Interfaces Visually in eiConsole and run them on eiPlatform

eiSuite EDI SNIP4+ is designed to integrate with PilotFish eiPlatform as a headless runtime environment. Interfaces can be configured visually with no coding or scripting required using eiConsole for X12 EDI.

Example Interface Pattern: Multiple Sources to Multiple Targets

Within eiConsole, interfaces can be built using a graphical assembly line process that supports “Any Source to Any Target.” The demo example includes multiple Sources with dedicated Listeners.

Source Inputs in the Example

1. A Provider’s CSV file is picked up by the Directory/File Listener and transformed from CSV to XML
2. A Hospital’s HL7 ADT messages picked up by an HL7 LLP Listener and converted from HL7 to XML
3. A Payer’s EDI X12 flat file picked up by an SFTP Listener and transformed to XML
4. A Solution Provider’s JSON file collected by a RESTful Web Service Listener and transformed into XML

Target Transformations in the Example

1. XML to DB using the Database SQL Transport
2. XML to JSON using the Web Service HTTP Post Transport
3. XML to EDI using the HTTP Post Transport

Target Systems in the Example

1. A Quality Measures Data Store receives database SQL formatted data
2. A Quality Reporting System obtains data in JSON format
3. An EDI Claims Web Service processes EDI formatted data

A Complete Solution Suite for X12 EDI HIPAA Integration with Validation and
Code Set Maintenance that Supports All Transactions

Additional Technical Details

• Choose a Listener or Adapter from a drop-down menu featuring 40+ Built-in Listeners
• Use a 3-pane drag & drop Data Mapper where users drag Source data and Target data into a central mapping panel
• Route messages to one or more Targets using XPaths or a Load Balancer with debug tracing and transaction monitoring
• Reuse the Data Mapper again when additional transformations are needed for the Target System
• Name Target Systems, add metadata and select representative icons for Targets
• Use eiConsole Inline Testing Mode for end-to-end testing, with the ability to start and stop tests at any stage, review results, adjust and retest
• After testing, deploy interfaces to an eiPlatform runtime and export as discrete configuration files for production

FAQ

Does PilotFish’s eiConsole standardize incoming data to XML before processing?

What SNIP levels are supported?

Does SNIP4+ validate against external code sets?

How are EDI external code sets kept current?

Which X12 EDI healthcare transaction sets are supported?

Check out our FAQ pages for more.

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