Skip to content
PilotFish Logo

Integration/Interface Engine Demo: eiConsole for Healthcare

Integrate Anything to Anything with PilotFish

Interoperability issues? Solved.

This video provides a quick, visual overview of the PilotFish eiConsole for Healthcare and how it helps teams build, test and deploy integration routes across HL7, FHIR and X12 EDI, plus APIs, databases and cloud or on-prem systems.

Try the Free 90-day Trial Talk to an Expert

scheduleVideo Key Moments

30-second summary

  • Integrate systems, apps, devices and databases using a common XML-based model
  • Import EDI, HL7 v2, HL7 v3, FHIR, CDA plus common enterprise formats
  • Use 30+ built-in protocols for cloud, on-prem and hybrid connectivity
  • Accelerate HL7 and X12 work with inline documentation, friendly naming and test mode
  • Deploy routes for unattended execution, monitoring and reporting, optimized for Docker containers

Integrate Anything to Anything

Use eiConsole to connect and orchestrate data flows across:

  • Systems and applications
  • Databases and data warehouses
  • Medical devices and equipment
  • Cloud services and on-prem environments

One-to-one, one-to-many, many-to-many routes are supported, using a consistent transformation approach.

Integrate Anywhere to Anywhere

Support common healthcare deployment patterns:

  • Cloud to cloud
  • Cloud to ground
  • Ground to ground

Import Any File Format

Common formats teams use with eiConsole include:

  • X12 EDI
  • HL7
  • HL7 FHIR
  • CCD, CDA
  • CSV and flat files
  • XML and JSON
  • Excel XLS, XLSX
  • NCPDP
  • HTML
  • WSLD
  • PDF, ZIP, binary payloads
  • SOAP payloads and WSDL-backed services
  • COBOL copybook sources in legacy environments

Connect with Built-in Communication Protocols

Connect to endpoints without custom code for every integration. Typical categories include:

  • APIs and services: RESTful Web Service, SOAP Web Service
  • Directory and identity: LDAP
  • Email: SMTP, POP3 / IMAP
  • Secure transport and remote access: SSH, SSL
  • Messaging and queues: JMS, MSMQ, MQTT, WebSphere MQ
  • Databases: Mongo DB, MySQL, Oracle DB, MS SQL Server, DB2, Postgres
  • Network and web: HTTP Get, HTTP Post, Sockets, TCP/IP, UDP
  • Healthcare and legacy: VistA RPC, EMR API
  • B2B EDI transport: AS2
  • Runtime and integration utilities: Command-Line, RMI

Use Healthcare and Industry Standards

Work with standards your teams already rely on:

  • HL7, HL7 FHIR
  • X12 EDI
  • DICOM
  • CCD/CDA
  • NCPDP
  • ACORD
  • XML and JSON as universal interchange formats

Get Productive with HL7 Features

  • Friendly naming: replace cryptic field names with readable labels
  • HL7 parser: handle unknown segments and capture data for transformation
  • Inline HL7 documentation: load HL7 versions and browse vocabulary in the mapper
  • Graphical test mode: test at any stage and inspect output quickly

X12 EDI Features and Components

  • Friendly naming for segments and elements for faster onboarding
  • Inline EDI documentation including field details and code lists
  • Format builder to parse and read X12 transactions more quickly
  • SNIP validation support: Types 1–3 out of the box, Types 4–7 available as an add-on
  • Graphical test mode: validate changes without slow release cycles

Deployment and operations

Routes built in eiConsole are designed to move cleanly into production:

  • Deploy for unattended execution using the PilotFish runtime environment
  • Monitor message flow, failures and throughput with operational visibility tooling
  • Support hot deploy patterns for reduced downtime
  • Works great in Docker containers

Why PilotFish

  • Reduce time to first interface with visual route design and reusable components
  • Standardize transformation using an XML-centric integration model
  • Scale across healthcare formats and protocols without rebuilding from scratch
  • Improve maintainability with test mode and inline documentation

FAQ

What is eiConsole for Healthcare? expand_more

eiConsole is PilotFish’s graphical integration IDE used to build and test routes that move data between healthcare systems using HL7, FHIR, X12 EDI plus APIs, files and databases.

What healthcare formats can I process with eiConsole? expand_more

Common formats include HL7, FHIR, X12 EDI, CDA and CCD, plus XML, JSON, CSV, Excel and PDFs.

How does the “common model of integration” help? expand_more

Incoming data is normalized into an XML representation so mapping, routing and validation can be applied consistently across different source formats.

Can I validate X12 EDI and support SNIP rules? expand_more

Yes. SNIP Types 1–3 are available out of the box and Types 4–7 are available as an add-on, depending on your licensing and workflow needs.

Does eiConsole support hybrid integration across cloud and on-prem systems? expand_more

Yes. eiConsole is commonly used for cloud-to-cloud, cloud-to-ground and ground-to-ground routes so you can connect SaaS apps, internal databases and on-prem healthcare systems in the same integration architecture.

How do teams reduce build time and long-term maintenance for new interfaces? expand_more

Teams typically speed delivery by reusing connectors and transformations, leveraging friendly naming and inline documentation and using graphical test mode to validate changes at each stage before deploying to production.

Check out our FAQ pages for more

If you’re curious about the software features, free trial, or even a demo – we’re ready to answer any and all questions. Please call us at 813 864 8662 or click the button.

Contact Us

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