Experience Exactly Why PilotFish is Superior
PilotFish consistently wins in side-by-side evaluations ranking higher in overall ease-of-use, depth of functionality and time to configure, test and deploy integrations.
With PilotFish’s Graphical Automated Interface Assembly line process and open APIs, interfaces can be created and maintained at unprecedented speed. No coding, no scripting is required.
Note: PilotFish’s base licensing includes every component we offer – all our Processor, Listener and Transport Adapters and all supported data formats – at no extra cost.
See PilotFish in action.
"PilotFish is extremely flexible, intuitive and easy to use. There are so many different methods to transform messages. There are videos, tutorials and extensive documentation to consult on how to use this product even after training. The team at PilotFish is also very responsive for any questions."
Featured Videos
In this demo, we build a 278 prior authorization route in the eiConsole, convert FHIR JSON to XML, map it to X12 278 using XSLT, validate it against SNIP 1–3, test it inline, and then deliver it to a target endpoint. The same template scales to additional trading partners with minor tweaks.
Watch video
Watch our graphical Data Mapper perform in this quick demo. Coding or scripting is not required. Data formats are transformed in minutes utilizing PilotFish’s exclusive 3-pane data mapper. The Data Mapper design allows you to drag & drop to create even the most challenging mappings.
Watch video
Discover eiSuite EDI SNIP4+, the ultimate X12 EDI HIPAA integration suite. It supports all healthcare X12 transaction sets with advanced validation and real-time data insights, SNIP 1-7 validation and optional code set maintenance.
Watch video
Unlock the full potential of EDI 837 data integration, or any X12 EDI transaction, with the powerful eiConsole. Handle EDI 837 data from the Source to Target Systems in our 7-stage process with data mapping, rule-based routing and various connectivity protocols.
Watch videoBrowse Our Videos
Browse through the videos below or select by Video Type or Data Format.
25 of 25 videos
No results match your filters
Try adjusting or clearing your filters.
In this demo, we build a 278 prior authorization route in the eiConsole, convert FHIR JSON to XML, map it to X12 278 using XSLT, validate it against SNIP 1–3, test it inline, and then deliver it to a target endpoint. The same template scales to additional trading partners with minor tweaks.
Watch video
Watch our graphical Data Mapper perform in this quick demo. Coding or scripting is not required. Data formats are transformed in minutes utilizing PilotFish’s exclusive 3-pane data mapper. The Data Mapper design allows you to drag & drop to create even the most challenging mappings.
Watch video
Discover eiSuite EDI SNIP4+, the ultimate X12 EDI HIPAA integration suite. It supports all healthcare X12 transaction sets with advanced validation and real-time data insights, SNIP 1-7 validation and optional code set maintenance.
Watch video
Unlock the full potential of EDI 837 data integration, or any X12 EDI transaction, with the powerful eiConsole. Handle EDI 837 data from the Source to Target Systems in our 7-stage process with data mapping, rule-based routing and various connectivity protocols.
Watch video
Tutorial of EDI 834 data conversion with PilotFish’s advanced integration tools. Transform CSV, XLS (Excel), or TXT to an EDI 834 format (Benefit Enrollment and Maintenance). Also the reverse, CSV to EDI 834 conversion.
Watch video
The PilotFish eiConsole IDE is a graphical integrated development environment for the rapid configuration of any healthcare interface. You’ll walk through the 7 stages of interface building with HL7 and X12 EDI data sources that are routed to a database and a web service.
Watch video
This video demonstrates a data route with multiple input sources with different protocols – HL7, X12 EDI and FHIR JSON. With PilotFish, any data format is easily written to multiple target database sources after being normalized.
Watch video
Build, test, maintain and deploy all of your X12 EDI integration interfaces with the PilotFish eiConsole. Routes in this Quick Tour are built with X12 EDI, HL7 and FHIR JSON feeds, transformed into XML and database statements for multiple locations.
Watch video
EDI 837 messages (or any other X12 EDI transactions) are routed, validated and tested in the eiConsole for EDI X12 by PilotFish. The eiConsole is a powerful interface engine with special tools built-in to handle X12 EDI transactions (all of them) and also HL7, FHIR JSON and any other protocol or standard.
Watch video
The PilotFish eiConsole for X12 EDI strips away the technical complexity of parsing, validating, mapping and producing X12 EDI files and EDI documents. PilotFish provides SNIP validation out-of-the-box for Types 1-3 and for Types 4-7 as an add-on. Validate healthcare X12 EDI data, translate it and map it to or from any other application.
Watch video
As a select distribution partner of X12, the Pilotfish Integration Solution offers a suite of productivity-boosting features that strip away the technical complexity of parsing, validating, mapping and producing X12 EDI files. The video shows how an interface can be organized as multiple routes, built stage by stage. EDI 837 and 999 are used as examples, but this workflow applies to any X12 transaction.
Watch video
Build, test, maintain and deploy all your X12 EDI integration interfaces. This video demonstrates a supply chain EDI route ingesting purchase orders with EDI 850 and EDI 855 transactions.
Watch video
Graphically Configure, Map and Test Healthcare Interfaces Using Any Data Format or Connectivity In this demo, you will see how PilotFish eiConsole supports rapid interface configuration for HL7, FHIR and X12 EDI, including mapping, end-to-end testing, deployment and operations.
Watch video
Connect Anything to Anything with the eiConsole for Healthcare (HL7 2.x & 3.x, X12 EDI, FHIR JSON, CCDA, DICOM, NCPDP, etc.). Define your Source and Target systems with a click and then configure the step-by-step interface assembly line to define the mechanics of the data flow and deployment.
Watch video
See how PilotFish accelerates HL7, FHIR and X12 EDI integration with visual configuration and inline testing.
Watch video
Many of the unique capabilities of the eiConsole for Healthcare are demonstrated in this video. Here HL7 2.x data comes from a hospital over LLP. Via a drop-down, the HL7 2.x version is identified. Then the video takes you through the logical transformation steps. The data output is sent to a measures store or database.
Watch video
View an example of EHR/EMR integration for medical equipment and solution providers via PilotFish’s Graphical Automated Interface Assembly Line process and open APIs. Note that PilotFish processors perform high-level operations on data, right after it comes in the system or right before it goes out, such as decryption, character conversion or compression.
Watch video
In this demo you will see how to take an HL7 v2 message template in the eiConsole for Healthcare, convert the inbound HL7 into XML, then map it into a custom XML structure using the built-in Data Mapper. You will also learn how to run an inline test to validate the output before moving the transformation to production.
Watch video
Data Mapping to an HL7 Message Template in eiConsole In this demo, you will see how to take a sample HL7 v2 message from an implementation guide or vendor spec, load it as a target template, and then map custom source data into that HL7 structure using PilotFish’s Data Mapper.
Watch video
HL7 Parsing Component of the eiConsole for Healthcare In this demo, you see how PilotFish eiConsole parses real-world HL7 v2.x messages that include non-standard segments, vendor extensions and modified field structures. I
Watch video
Transforming and mapping HL7 data can be challenging due to the scope and complexity of the HL7 data dictionary. This process is simplified in the HL7 data mapper by providing inline access to the HL7 vocabulary through the format builder component.
Watch video
This video demo shows PilotFish’s eiConsole using the HL7 “Friendly Name” option to make HL7 v2 messages easier to read, interpret, and map. Instead of working with dense HL7 segment and field identifiers, Friendly Names converts the message to a clearer XML view. This makes segments, fields and components appear with human-readable labels.
Watch video
Healthcare Interface Engine Overview: Build, Test & Deploy Integrations This overview video walks through how PilotFish clients use eiConsole to design interfaces, validate message flows, test changes safely and deploy integrations to production with a repeatable process. I
Watch video
In this demo, you will see how the PilotFish eiConsole is used to build a purchase order ingestion workflow that receives an EDI 850, decrypts and transforms it into XML, validates key business totals, updates a database and generates an EDI 855 Purchase Order Acknowledgment for delivery to downstream systems.
Watch video
Build an HIE Interface with HL7 v2 and CDA Data (Database Target) In this eiConsole for Healthcare demo, we build an HIE-style interface that ingests CDA plus HL7 v2 and writes normalized data into a database. The example shows CDA coming in via (S)FTP and HL7 arriving over LLP, with both flows ending in database inserts.
Watch videoSchedule a personalized demo designed around your data, standards and environment.
No credit card required · No obligation · Enterprise support included
