30-second summary
- Build healthcare interfaces using a 7-stage assembly line workflow in eiConsole
- Configure protocols quickly using 40+ Listeners and 35+ Transports
- Transform data into XML, map visually and validate during development
- Deploy to eiPlatform for unattended execution and monitor in eiDashboard
Build an interface using the Automated Interface Assembly Line
The Automated Interface Assembly Line is designed to make integration work repeatable and fast, using a consistent set of stages that guide configuration from source to deployment.
7 stages in eiConsole:
- Source System: Name and document the source system and its context.
- Listener: Select how data is received, then configure it using the built-in panel.
- Source Transform: Declare the incoming format, then normalize data into XML for consistent downstream processing.
- Route: Apply routing rules and optionally configure transaction monitoring.
- Target Transform: Configure the target format and open the Data Mapper for visual mapping.
- Transport: Choose the outbound protocol and configure transmission settings.
- Testing and Debug: Run inline tests, inspect data at each stage, then finalize for production deployment.
Deployment and Operations
Save route configurations to the file system for controlled promotion across environments
- Deploy to eiPlatform for unattended execution
- Monitor throughput, message details and operational KPIs in eiDashboard
Works great in Docker containers.
Why PilotFish?
- Faster time to first interface using a guided assembly-line workflow
- Lower maintenance using visual configuration, reusable transforms and consistent routing patterns
- Vendor-neutral integration across healthcare standards and legacy formats
- Production visibility with eiDashboard monitoring and reporting
FAQ
What is an interface engine in healthcare integration?
An interface engine is software that connects systems, transforms data formats and routes messages between endpoints to support interoperability across applications, databases and standards.
How do you test interfaces before production?
You can run inline tests during development, inspect data through each stage and validate expected outputs before deploying to production.
Does PilotFish require custom code to build interfaces?
PilotFish supports low-code interface development with visual configuration, reusable transforms and drag and drop mapping. Custom code can be added when needed but many interfaces can be delivered without heavy scripting.
What is the difference between eiConsole, eiPlatform and eiDashboard?
eiConsole is used to configure and test interfaces, eiPlatform runs interfaces in production, and eiDashboard provides monitoring, reporting and operational visibility.
Can PilotFish support both real-time and batch integration?
Yes. PilotFish supports real-time message processing and scheduled or batch workflows depending on protocol, routing and operational requirements.
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.
X12, chartered by the American National Standards Institute for more than 35 years, develops and maintains EDI standards and XML schemas.