Back to Pilotfish Home

Product FAQ

PilotFish Product Frequently Asked Questions

PilotFish offers modern and robust solutions that enable data integration between any and all systems, standardized formats, applications, databases, operating systems and platforms. PilotFish delivers seamless integration regardless of the mix of systems, communications protocols, or standards in use (HL7 2.x and 3.x, FHIR, JSON, XML, CCD/CDA, HIPAA X12 EDI, etc.). Supporting legacy systems as well as the newest technologies is no problem. In fact, PilotFish is the only healthcare integration solution you’ll ever need.

Note: If your focus is Healthcare EDI or HL7 transactions, visit our X12 EDI FAQ or HL7 FAQ web pages.

What is PilotFish Software?

PilotFish is middleware software, and an integration framework that is modern and robust. PilotFish enables data integration of anything to anything – applications, databases, equipment and services using any communications protocol. PilotFish offers specific support for industry standards such as HL7 including 2.x, 3.x and FHIR, X12 EDI and ACORD XML and other standard formats such as XML, CSV, XLS/XLSX, JSON, PDF, Flat Files and Binary.

What is PilotFish used for?

PilotFish integration solutions are used to enable the integration of disparate systems using industry and XML standards. The PilotFish Integrated Development Environment (IDE) features a graphical automated interface assembly line process that allows users to build manage and maintain interfaces without any coding or scripting.

How does an interface engine work?

Interface engines are software architected to receive incoming messages and route them to the appropriate target information systems. They also translate the messages into formats that the receiving system can understand. Standardized protocols are employed for exchanging data. Efficient tools for parsing and data validation and up-to-date application software are expected.

What is an interface engine in healthcare?

Interface Engines in healthcare are software systems for exchanging healthcare information in use cases involving disparate systems communicating over different protocols. They must adeptly handle data transformation and exchange of not only large batch-oriented data and HL7 2.x and other version messaging, but also highly conversational XML and JSON APIs – including HL7 FHIR.

What is a healthcare integration engine?

A Healthcare Integration Engine is a software system designed to exchange disparate healthcare information between the systems in the healthcare ecosphere communicating over different protocols. They handle data transformation and exchange of not only large batch-oriented data and all versions of the HL7 messaging standard as well as highly conversational XML and JSON APIs, including HL7 FHIR.

What file types can be processed by PilotFish?

PilotFish is capable of processing X12 EDI, XML, CSV, JSON, PDF, HL7, FHIR, NCPDP, ACORD files and many others. See Product Specifications.

What are the benefits of using PilotFish’s integration engine for Healthcare Payers?

PilotFish’s integration engine for healthcare payers provides a comprehensive solution for healthcare payer integration, with benefits such as rapid interoperability, support for healthcare standards, and easy deployment. Additionally, the platform is designed to streamline healthcare payer operations, improve CMS compliance, and reduce costs.

What is integration engine software?

Integration engine software is a software program and its components architected to process data received from source systems, translate the messages into formats required by receiving target systems, and then route the data to the identified targets. Think nerve center, traffic cop or hub to manage all the data flows between the disparate and multiple technologies in an IT environment.

What standards and terminologies does PilotFish support in the healthcare industry?

PilotFish is designed for comprehensive adaptability, supporting a wide range of health-related standards including X12 EDI, NCPDP, HL7, CDA, and FHIR. Additionally, it is proficient in various health-related terminologies like LOINC, SNOMED, CPT, HCPCS, ICD-10, and RXnorm, among others. This extensive support ensures seamless integration for a multitude of healthcare applications.

Is PilotFish software used for Healthcare Payer Solutions?

Yes, PilotFish provides software solutions for healthcare payer integration and claims processing. PilotFish’s integration engine for payers helps streamline healthcare payer operations, improve CMS compliance, and manage EDI solutions. PilotFish’s suite of integration engine solutions delivers rapid interoperability in virtually every area of healthcare, including healthcare payer integration. PilotFish’s software is utilized by 90% of the top insurers and leading health payers, and its proven EDI claims processing solutions for Property & Casualty insurers and Health Payers address the needs of healthcare payers. PilotFish has also partnered with healthcare tech companies to provide best-of-breed integration software purpose-built for facilitating the interoperability of disparate systems for healthcare payers.

How does PilotFish compare to other integration platforms?

PilotFish’s Integration Platform consistently wins over other integration platforms such as MuleSoft’s Anypoint Platform and ECMap in terms of lower cost, higher ROI, and ease-of-use. Additionally, PilotFish’s integration engine is built on Java and supports linking internal and external business applications, making it a suitable option for medium to large enterprises. Overall, PilotFish’s Integration Platform offers a cost-effective and user-friendly solution for businesses looking to integrate their systems and applications.

Who is a MuleSoft competitor for the Anypoint Platform?

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. PilotFish’s integration suite costs a whole lot less than Anypoint too, as well as delivering a whole lot more. Read the details. MuleSoft vs PilotFish – Which One Comes Out on Top?

MuleSoft vs PilotFish

How does PilotFish minimize IT overhead in comparison to competitors like Mirth?

PilotFish is engineered for maximum flexibility and minimal coding requirements, ensuring easy integration with existing systems and significantly reducing IT workload. Its intuitive graphical interface further simplifies integration processes, offering a user-friendly solution that lessens the learning curve and IT strain, particularly in routine integrations. Review our PilotFish Competitive Advantages article.

Does PilotFish offer a Software as Service model (SaaS)?

PilotFish solutions can be deployed in the cloud or on-premises, but a SaaS model is not available. PilotFish does provide initial setup and training services.

How frequently does PilotFish update its software to adhere to the latest industry standards?

PilotFish conducts annual major updates and additional minor releases throughout the year to ensure compliance with the latest industry standards. See PilotFish Release Notes.

How flexible is the triggering system for transformations in PilotFish?

PilotFish offers a highly flexible triggering system for transformations, allowing configurations based on a variety of conditions, including specific data attributes.

What enables PilotFish to integrate with APIs for workflow automation?

PilotFish’s integration with APIs for workflow automation is enabled by its flexible architecture, which supports triggering processes based on data availability and specific events to enhance operational efficiency.

How does PilotFish seamlessly integrate data from diverse sources and formats?

PilotFish’s integration engine effortlessly processes data from various sources and formats, automating data transformation and normalization to align with client and trading partner system requirements.

Can PilotFish’s Listener component manage various communication protocols and data transformations?

Absolutely, the PilotFish Listener component expertly manages an extensive array of communication protocols and executes macro operations on incoming data, enhancing flexibility in data receipt and preprocessing.

Can PilotFish support multiple data sources and targets, and how does it handle data routing?

Yes, PilotFish can handle multiple data sources and targets. It uses a highly configurable routing mechanism to differentiate and process data accordingly, which can be tailored to meet specific workflow requirements during the setup. Watch this video demo with HL7, X12 EDI, FHIR input data sources and then JSON and a database as the target formats.

Can PilotFish’s integration engine be used to integrate with non-healthcare entities?

PilotFish’s integration platform suite of products enables the integration of anything to anything, anywhere and in any way. Additionally, our integration engine is being leveraged by virtually every stakeholder in healthcare, including data analytics and revenue cycle providers, channel partners and manufacturers. PilotFish’s software handles X12 EDI, HL7, FHIR, NCPDP, CCDA, ACORD, XML and more with over 200+ B2B processors, transports, and listeners included out-of-the-box.

Can PilotFish’s integration tools be applied in industries other than data integration and do they cater to a technical user base across various sectors?

Yes, PilotFish’s integration tools are versatile and applicable across multiple industries, catering to technical users with diverse integration needs. Whether you work in healthcare, finance, insurance, or any other sector requiring data conversion, PilotFish’s tools can be tailored to suit your technical requirements, making them a valuable asset in various domains.

Does PilotFish enable real-time data integration and live reporting?

Absolutely, PilotFish facilitates instantaneous data exchange and provides the eiDashboard a web-based application for dynamic, real-time reports and dashboards.

Why is long-term viability important when selecting PilotFish as your integration platform?

Long-term viability is crucial because it ensures that PilotFish remains a robust and adaptable solution for your integration needs. The platform supports every principal healthcare standard and data source, such as X12 EDI, NCPDP, HL7, CDA, FHIR, and XML. It’s designed to seamlessly accommodate emerging standards and formats, ensuring your investments are future-proof.

Can PilotFish redirect claims to third-party processors?

Yes, PilotFish can route claims to any third-party processor as required. For example, If you need the claim sent via FTP, PilotFish can drop a file anywhere it is required. The PilotFish product suite includes 40+ Listeners/Adaptors that ship with the product and an Open API, which allows for the creation of custom adapters using Java or .NET.

Does PilotFish support ITX and SPLUNK integrations for file conversions?

Yes, PilotFish includes ITX or “Interpreted Text” compatibility and has built-in Splunk Listeners and Processors for immediate Splunk integration.

Can PilotFish manage both medical and pharmaceutical benefit eligibility verifications?

Yes, PilotFish efficiently processes eligibility inquiries for both medical and pharmaceutical benefits, ensuring comprehensive validation and support for clinical transactions. See our Pharmacy Claims Processing or NCPDP Integration Solution case studies as examples.

What is considered a ‘message’ in the PilotFish Integration Engine system?

Within the PilotFish Integration Engine, a ‘message’ refers to any distinct transaction processed by the system. This encompasses a variety of data formats and communication protocols, including HL7, EDI, JSON messages, HTTP requests, and other data exchange methodologies.

How does PilotFish manage bidirectional communication for complex data updates, such as updating a Care Plan?

In PilotFish, bidirectional communication is facilitated through configurable pipelines designed for robust data exchange. Depending on the complexity of the updates—like those involved in a Care Plan—these pipelines may be adapted to support asynchronous processes, ensuring accurate and timely data synchronization across systems.

Does the PilotFish integration engine require a database to operate?

The PilotFish integration engine does not require a database for basic operations. However, a database is necessary if you plan to use archival services or additional features such as the eiDashboard.

What methods enable external systems to trigger executions in PilotFish?

External systems can trigger executions in PilotFish via HTTP posts among other methods, facilitating seamless integration with a variety of external systems.

Can PilotFish automate the updating and processing of Excel files received and sent via SFTP?

Yes, PilotFish automates the updating and processing of Excel files received via SFTP, with the ability to handle and adapt to various file formats from different providers, and then push the updated files back to an SFTP server.

Does PilotFish support MQ connections (Message Queuing) for both inbound and outbound transactions?

Yes, PilotFish provides out-of-the-box support for MQ, enabling direct connections for both picking up and delivering messages in inbound and outbound transactions.

Can external applications, databases, or APIs access PilotFish configurations?

Yes, PilotFish allows external systems such as applications, databases, or APIs to interact with its configurations through supported callouts, lookups, etc. at any point in the workflow, facilitating versatile integration options.

Can PilotFish manage re-enveloping and control sequencing for outbound transactions to different trading partners?

PilotFish efficiently manages the re-enveloping of outbound files and assigns correct control numbers for each transaction, ensuring that every trading partner receives files with the appropriate sequence numbers.

What is the best data mapper?

The best data mapper allows users to visually map data using drag & drop and without any coding or scripting. PilotFish offers a data mapping component as part of its integration solution that does just that. PilotFish’s data mapper features a sophisticated 3-pane visual drag & drop mapper that allows users to do anything that they can do programmatically in the graphical view. The PilotFish data mapper makes users more productive and offers reusability for HL7, HIPAA EDI, XML, NCPDP, CCDA and other message types. It can handle any data mapping task from simple to complex without coding/scripting or users can work directly in the XSLT view. Watch the video to see it in action.
Data Mapper – Drag & Drop

Data Mapper – Drag & Drop

How user-friendly is PilotFish’s Data Mapper for non-technical users?

PilotFish’s Data Mapper component, powered by XSLT, provides intuitive graphical mapping ideal for non-technical users, along with direct code editing capabilities for advanced transformations, accommodating all user proficiency levels.

Does PilotFish support both bulk and real-time data validation?
Absolutely. PilotFish excels in both bulk and real-time validation, featuring a user-friendly interface that facilitates swift validations with instant results.

Is data validation with PilotFish processed locally on the client’s servers or on PilotFish servers?

With PilotFish, validation is conducted entirely within the client’s server environment, ensuring data privacy and security. There is no transfer of data to PilotFish servers for validation purposes. The software operates seamlessly in the client’s infrastructure, with the only external communication being for license verification.

Does PilotFish support single sign-on (SSO)?

Typically single sign-on is outside the scope of what our software does and is the responsibility of the IT infrastructure/security team. However, PilotFish can communicate complex web API calls with our API XL features. So, if something uses SSO (usually something with tokens) we can likely communicate with it. If a user wanted to create some web app using PilotFish we could probably build out an SSO authentication scheme, specifically, that would be via a route configuration.

What information does PilotFish require to initiate an eligibility transaction, is it just basic patient demographics?

PilotFish requires a clear understanding of the data schema and a sample file to effectively initiate an eligibility transaction, ensuring accurate processing.

What is SNIP Validation?

SNIP validation applies one to seven WEDI-defined industry-standard levels or types of verification. Each succeeding level increases the strictness of data constraint, i.e. SNIP Type 4 enforces SNIP Types 1-3. WEDI SNIP Validation tests how closely an EDI document adheres to the schemas defined in the X12 EDI standard.

How extensive is the data mapping customization required in PilotFish for interfacing between diverse systems?

After the initial setup within the PilotFish Integration Engine, mapping data between similar systems typically requires only minimal customization. Subsequent integrations often necessitate slight modifications tailored to the specific requirements of each system involved. Watch our 2-minute Data Mapping Demo Video.

Does PilotFish provide pre-configured mappings for HL7 and EDI transactions?

PilotFish does not offer pre-configured mappings for specific transactions like HL7 or EDI as standard. However, the system includes base formats and a comprehensive suite of tools that facilitate efficient customization of mappings.

Can PilotFish perform database queries during transactions to enrich data transformations?

Yes, PilotFish supports querying databases during transactions to dynamically enrich data during the transformation process.

How can PilotFish handle complex logic, such as using database query results to transform incoming data?

PilotFish allows for the execution of complex logical operations within its mapping layer. Users can incorporate data from database queries directly into the transformation process, either through the mapping functions or by embedding SQL commands for more advanced data manipulation.

Must messages be converted to XML before transformation in PilotFish?

Yes, in PilotFish, messages must first be converted to XML because the data mapper is only compatible with XML.

How does PilotFish manage and prevent overlap of sequence numbers?

PilotFish ensures that sequence numbers do not overlap by managing them within its transformation engine using XSLT. This approach provides precise control and accurate tracking of transaction sequence numbers.

Can the eiPlatform be deployed across various server environments, including cloud-based infrastructures?

Our eiPlatform offers versatile deployment options across multiple server environments, such as on-premises, hybrid, and fully cloud-based solutions, guaranteeing smooth integration with any infrastructure.

What is the preferred deployment environment for PilotFish?

PilotFish offers clients the freedom to choose their ideal deployment environment. Whether it is a physical server installation or utilizing a cloud platform like Amazon Web Services (AWS) or Google Cloud, the choice is yours.

Can I deploy the PilotFish software on a Linux environment without using products like IBM WebSphere?

Yes! PilotFish software can be effortlessly installed on any Linux environment supporting Java 17 and the recent Jakarta server API, like Tomcat. To get started, check out our Knowledge Hub for technical documentation or contact us for technical support.

How efficiently does PilotFish handle large files? Are there any file size constraints?

PilotFish is engineered to adeptly manage large files. The size limit depends on various factors, including server resources. It’s possible to process large files efficiently by chunking them if necessary.

Is the PilotFish solution scalable to accommodate future expansions, such as adding more facilities or data sources?

Yes, the solution is designed to be scalable. PilotFish can support future expansions by incorporating additional data sources and facilities without requiring a comprehensive system overhaul. See our Product Specs for a quick overview.

Does the PilotFish eiDashboard facilitate executive-level dashboards and monitor business activities? Is it scalable to accommodate growth and new systems?

Yes, PilotFish’s eiDashboard enables advanced executive dashboard functionality and business activity monitoring. It is designed to scale with your business, adapting seamlessly to new systems and data sources, ensuring sustainable integration solutions.

Does PilotFish provide user and testing interface environments such as UAT, PSUP, SIT and PROD?

Yes, PilotFish offers the capability to set up and manage different environments for development, testing, and production. Each of these environments can be configured with the required settings, data, and access controls.

Can small to mid-sized businesses leverage PilotFish’s Integration Engine effectively?

Absolutely. PilotFish’s Integration Engine is designed for scalability, making it suitable for organizations of any size. It also supports agent deployment tailored for specific client environments.

How does PilotFish enable real-time data collection without affecting system performance?

PilotFish ensures optimal system performance by querying data from a reporting database instead of the production database. This approach allows for real-time or near-real-time data collection without compromising the performance of existing systems.

What are the deployment options for PilotFish’s software, and how do they integrate with cloud operations?

PilotFish’s software offers flexible deployment options, including cloud-based and on-premises installations. Operating on an on-demand model similar to AWS, the software’s cloud deployment is designed to optimize resource usage, allowing for cost-effective scaling and minimal impact on existing cloud operations.

How does PilotFish support configuration management across different environments like Development, QA, and Production?

PilotFish supports distinct environments such as Development, QA (Quality Assurance), and Production. It provides a robust mechanism for users to promote configurations from one environment to another on a transactional basis, ensuring seamless transitions and integrity across stages.

How does PilotFish handle multi-threading for transactions to prevent bottlenecks?

PilotFish supports multi-threaded transaction processing, effectively preventing bottlenecks and ensuring efficient handling of high transaction volumes, particularly during peak periods such as Monday mornings.

How is PilotFish software licensed?

PilotFish offers a dual licensing model: The Integrated Development Environment (IDE) is licensed on a per-concurrent-user basis, while the runtime engine is licensed for each production instance.

How much does PilotFish cost?

PilotFish makes licensing simple. We do not charge per connection, per interface or per transaction. The monthly minimum for an on-demand license of the eiPlatform (Java runtime) is $3075 with a concurrent user license of the eiConsole (IDE) at $375 per month.

Does PilotFish charge per connection?

No, PilotFish operates on a volume-based licensing model with a minimum monthly fee, charging by the minute beyond the total volume of a 4-core 16-gigabyte server.

Does PilotFish build integrations for clients using the eiConsole?

Yes, we do. Some customers outsource everything to us so that we configure their interfaces for them. Others use our products to configure their own interfaces using our training and some technical support.

How is PilotFish pricing determined? Is it based on transaction volume or resource usage?

PilotFish pricing is not directly tied to the number of transactions but rather to the resources required to support your workflow. This may involve adding more memory or cores to your server as needed.

Does licensing PilotFish require in-house IT coders for data cleanup before integration, or does PilotFish provide this service?

PilotFish manages all aspects of data manipulation, including cleansing and preparation for integration. Our comprehensive implementation services include custom integration builds, training for client teams, and collaborative support. This flexibility means that clients do not necessarily need their own IT coders for data preparation.

What is required on the client’s side to implement and maintain the PilotFish solution?

Clients are required to fill out an Interface Requirements Form to specify their integration needs. Training on interface management and maintenance is available, with options for ongoing support contracts. After initial interfaces are set up, the maintenance effort is expected to be low, with most issues arising from external factors like network issues or third-party system updates.

What types of support and resources does PilotFish offer to assist technical users of their integration tools?

PilotFish provides an array of resources to support technical users of their integration tools. These include documentation, video tutorials, and access to a dedicated support team. You can find these resources on our website or reach out to our support team for assistance with any technical questions or challenges you encounter during your data conversion projects by using the Contact Us form.

How does PilotFish handle updates to standards set by organizations such as CMS?

PilotFish actively updates its schemas in response to changes in standards by authoritative bodies like CMS (Centers for Medicare and Medicaid Service), contingent upon the specific licensing plan selected by the customer. This ensures that users remain compliant with the latest regulations and standards.

What support does PilotFish provide for initial interface build-outs?

PilotFish provides comprehensive support for initial interface development, including full setup and delivery services, as well as training to enable self-sufficiency. See PilotFish Services.

Can the entire team access the PilotFish eiDashboard?

The PilotFish eiDashboard can be accessed by the entire team, with configurable user permissions that allow for read-only access, enabling team members to view dashboards without making changes.

Is a separate PilotFish license required to isolate each customer when bundled with other software?

When bundling PilotFish with other software, a separate instance and corresponding restricted license are required for each customer to ensure isolation.

Can multiple users access the PilotFish solution on a single server?

Yes, multiple users can access the PilotFish solution on a single server either by obtaining individual licenses or by configuring a virtual desktop environment for concurrent usage.

Does PilotFish allow for configurable user access levels per environment, such as Read, Read/Write, and Read/Write/Admin?

Yes, PilotFish supports configurable user access levels within different environments through its web-based monitoring tool, the eiDashboard.

What is involved in a typical startup process with PilotFish?

The typical startup process with PilotFish varies based on the client’s technical team experience but generally includes a 94-hour program of implementation, training, and mentorship. This comprehensive approach covers building the client’s first interface, followed by training and mentorship, supported by daily and weekly status meetings. The entire process can be completed in as little as 10 weeks.

What does the transition process from IBM Trading Manager to PilotFish involve?

The transition from IBM Trading Manager to PilotFish includes customized training, the potential development of a proof of concept (POC) and collaborative support throughout the migration process.

What robust security measures are in place for PilotFish’s data integration?

PilotFish ensures HIPAA compliance with stringent security measures to safeguard PHI (Protected Health Information), utilizing encryption and secure data handling protocols.

Does Pilotfish manage the intricate aspects of connectivity, such as the initial handshake, signatures, authentication, token generation, and signature checks?

Absolutely, PilotFish takes care of all these aspects. We handle various security protocols, including Single Sign-On (SSO), certificates, basic authentication, and Transport Layer Security (TLS). All these components are seamlessly integrated into our system.

How does PilotFish handle error management and notifications for failed transactions?

PilotFish has mechanisms for monitoring inactivity and errors, including connection timeouts. It can send notifications through various methods, such as email alerts or SMS (via external services like AWS SNS), when transactions fail or when there is inactivity beyond a configured threshold.

What is the level of complexity involved in configuring routing rules and monitoring transactions for errors in PilotFish?

PilotFish’s routing layer enables a straightforward setup of message flow rules. The robust Transaction Monitoring feature streamlines error management by directing exceptions to a specific error route for centralized oversight and simplified troubleshooting.

Does PilotFish offer the functionality for bulk reporting of validation errors, especially when dealing with a large number of files?

PilotFish’s system primarily handles validations per transaction. However, part of the solution suite includes the eiDashboard, a separate web application that can be used for bulk reporting. The powerful eiDashboard enables users to run queries on failures and results, providing in-depth insights from a comprehensive database. However, each file’s validation report must be viewed individually unless configured for aggregated viewing.

Can PilotFish manage real-time transaction certificate renewals and provide notifications?

Yes, PilotFish can be configured to monitor SSL/TLS certificate validity in transactions and as an option, you can automatically notify administrators when a certificate is approaching its expiration date.

What security measures does PilotFish use for secure data transfer of sensitive healthcare information?

PilotFish ensures the security of healthcare data transfers by utilizing VPN tunnels and HTTPS connections, incorporating robust data encryption within its middleware capabilities.

What functionalities does the PilotFish audit trail feature offer?

The PilotFish audit trail feature includes configurable message archiving. Additionally, the eiDashboard supports detailed logging and enables users to resubmit messages after resolving any issues, enhancing traceability and operational recovery.

How does PilotFish support monitoring, logging, and alerting in the eiConsole IDE?

PilotFish eiConsole users can use log4j2 for advanced logging customization within the application. PilotFish also offers the eiDashboard for comprehensive monitoring. Additionally, users can leverage external tools like Datadog for enhanced alerting capabilities, as well as other platforms, underscoring the need to build a robust support framework around it.

Does PilotFish offer a REST or SFTP Listener available for data connectivity?

Yes, PilotFish features a RESTful Web Service Listener for optimal data connectivity, which can be deployed within the client’s environment to facilitate secure data reception via HTTPS. We also have an FTP/SFTP Listener with many configuration options.

Does PilotFish offer a callback mechanism to confirm data insertion?

Yes, PilotFish supports both synchronous and asynchronous integration approaches, with real-time responses and callbacks to verify data insertion.

Does PilotFish offer a database connector for direct database insertions?

Yes, PilotFish supports a variety of protocols, including direct database insertion. We can establish connections to any service as needed by our clients.

Is it possible to connect the PilotFish eiDashboard with Active Directory (AD) for user authentication?

Definitely! You can connect the PilotFish eiDashboard with Active Directory (AD), enabling streamlined user authentication and access control.

Does the PilotFish eiDashboard allow viewing of associated files or transactions?

Yes! The PilotFish dashboard has been designed with users in mind, enabling them to trace and access associated files or transactions based on specific metadata or attributes. If the necessary metadata is tagged appropriately, users can easily view the correlated files. For a deeper dive, explore our eiDashboard features.

Does PilotFish process the entire stack and then transmit it through a RESTful service when addresses change?

Yes, PilotFish manages the entire process. However, the necessary services for sending must be provided to us.

Does PilotFish operate exclusively at the application layer without involving the network layer?

That’s correct. In PilotFish, all operations occur at the application layer. From the moment we receive a message, we manage it until it’s successfully delivered to the intended recipient.

Does PilotFish offer analytics and reporting on data integration aspects such as errors, document flow, transmission volumes and related metrics?

Yes, PilotFish’s eiSuite, which includes the eiDashboard, delivers web-based analytics and reporting on various aspects of data integration, including documents, errors, and transaction volumes. It also allows monitoring and analyzing the documents that pass through the integration engine. This includes tracking the number of documents, types of documents and any transformations or routing.

Can PilotFish offer real-time data collection without compromising the performance of existing systems?

Yes, PilotFish ensures efficient real-time or near-real-time data collection by operating off the reporting database, thereby eliminating any negative impact on the performance of your production database.

How can users monitor resource usage in the PilotFish system?

Users can monitor resource usage in the PilotFish system by utilizing the eiDashboard, which provides detailed usage metrics.

What distinguishes transaction logs from show logs in PilotFish?

In PilotFish, transaction logs are specific to individual transactions and are stored in a database, providing a detailed view of each transaction. Show logs, on the other hand, consist of written EIP log files that are saved on disk, offering a general overview of operations.

Does the PilotFish eiDashboard serve the development environment or monitor runtime environments?

The PilotFish eiDashboard is an analytics tool specifically designed to monitor runtime environments. It provides capabilities for tracking audit logs, transactions, and overall health within the integration ecosystem.

What reporting capabilities does PilotFish provide for tracking successful and failed transactions?

PilotFish provides comprehensive reporting capabilities that allow users to monitor both successful and failed inbound and outbound transactions, ensuring detailed visibility into the transactional flow. See eiDashboard.

Does the eiDashboard support real-time monitoring and alert configuration for system health and transaction issues?

The eiDashboard supports real-time data monitoring and can be configured to alert users about stuck transactions and system health indicators, including memory and CPU utilization and other monitoring tailored to specific needs.

How can I configure the eiConsole to have access to more memory in order for it to appropriately be able to handle larger interfaces and transactions?

You can increase the memory available to the eiConsole by adding or updating the eiConsole.vmoptions parameter in the configuration file in the install folder. Once this setting is changed, the eiConsole will have to be restarted for it to use the newly changed value. An example value is shown below to give the eiConsole access to 2560 Mbytes of memory.
Set the maximum RAM available to the application -Xmx2560m

HL7 Interface Engine IDE Features


Can PilotFish aggregate data for customized dashboards catering to diverse user profiles?

Indeed, PilotFish can aggregate and distribute data across customized dashboards designed for a variety of user profiles with the eiDashboard, ensuring access to pertinent and actionable insights tailored to individual roles and requirements.

Is there a list of special characters that are not supported in PilotFish during data transformations?

By default, PilotFish processes data using the UTF-8 encoding standard. Any characters outside of that character set could potentially cause transformation problems. PilotFish can be configured to use other encodings, if necessary. Additionally, any characters that could invalidate XML or XSLT will need to be escaped to avoid transformation problems.

Does PilotFish’s integration platform support Snowflake, the cloud-based data warehouse?

Yes, PilotFish can load data into Snowflake with the Snowflake JDBC driver. View the more detailed documentation on how to connect Snowflake in PilotFish’s eiConsole.

Does PilotFish Support IPv6 protocol?

Yes, PilotFish products support IPv6 connections. Java applications support both IPv4 and IPv6 automatically. PilotFish products are Java-based. Here is a Networking IPv6 User Guide that you may find helpful.

How does PilotFish enable extensibility through custom development?

PilotFish allows seamless integration with custom Java code, enabling the creation of custom processors and listeners. The tool also supports versatile scripting in a variety of languages such as Ruby and Python, which provides additional flexibility to extend functionality as needed.

Does PilotFish offer a specialized tool or studio for interface development?

Yes, we do. PilotFish provides a dedicated development tool or studio, allowing developers to install it on their laptops for efficient interface development. Learn more about the eiConsole IDE.

Besides the GUI, does PilotFish provide a command-line interface (CLI) for detailed interfacing?

Yes, PilotFish offers the eiDashboard as a separate product. It provides real-time data inspection, reporting, and graphical interfaces, in addition to the GUI. The eiDashboard is included as part of the on-demand license.

Where can I get the mandatory nodes of ACORD?

If you are using the ACORD Model Viewer from PilotFish, the nodes that are “required” by the schema are indicated with a green checkmark. However, we recommend reviewing trading partner and transaction-specific implementation guides, as the required fields for specific message types are typically more relevant (and extensive) than what the schema itself offers.

Is PilotFish optimized for efficient search performance?

Yes, PilotFish utilizes several architectural elements that contribute to efficient search. These include Optimized Data Indexing, Scalable Database Management and Caching Mechanisms for fast, precise data retrieval. Advanced Search Query Capabilities allow users to filter and retrieve data based on things like transaction IDs, dates, specific content within messages, error codes etc. Real-time processing and parallel techniques ensure currency of data and system robustness, while efficient resource management guarantees system sustainability during search operations.

How does PilotFish accommodate unique client requirements beyond its existing capabilities?

PilotFish prides itself on its architecture’s extensibility and flexibility. Custom functionalities can be seamlessly integrated through its Open API, using either Java or .Net, minimizing the need for extensive custom development.

How can email triggers be configured for queued jobs in PilotFish?

In PilotFish, email triggers for queued jobs are configured through the eiConsole, not the eiDashboard. Necessary information for setting up these triggers is accessible during the route building process.

Can regular transformations be scheduled within PilotFish?

Yes, PilotFish supports the scheduling of regular transformations as part of its headless runtime capabilities, allowing for unattended operations that can be configured as needed.

How does PilotFish automate data processing from Azure Data Factory to Snowflake?

PilotFish automates data processing between Azure Data Factory and Snowflake by seamlessly managing data transformations and ensuring data integrity throughout the process. See our product spec sheet.

How does PilotFish manage envelope control numbers and enforce duplication rules with configurable data retention?

Yes, PilotFish can easily set up these types of actions in our data mapper, which utilizes XSLT since all inbound data is transformed into XML once ingested (behind the scenes with no latency). For example, PilotFish would use a key to perhaps group ISA segments by control number, use match to select all ISA segments and then iterate over those. We would then run a check to find any control numbers appearing more than once and indicating a duplicate within that loop.

Can PilotFish reject messages at the file, group, or transaction levels such as ISA/IEA, GS/GE, or ST/SE?

PilotFish can reject messages at various levels—file (ISA/IEA), group (GS/GE), and transaction (ST/SE)—using XSLT to tailor conditions for each scenario. Examples include rejecting messages with incorrect sender/receiver IDs at the ISA level, mismatched group numbers at the GS/GE level, or missing segments at the transaction level. PilotFish configures and executes these rejections through detailed error handling routines, including EDI 999/997 responses or other customized error routing methods.

Can input and output folders, file extensions, or queues be configured in PilotFish?

PilotFish allows for extensive customization of data handling settings, including the ability to configure input and output folders, file extensions, and queues to meet specific integration requirements.

What options does the eiDashboard offer for managing historical data and short-term retention without an external database?

The eiDashboard provides a built-in H2 database to manage historical data and support short-term data retention when an external database is not available and options for configuring data retention according to a client’s requirements.

Does PilotFish provide a user interface for trading partner configuration?

PilotFish does not include a built-in user interface for configuring trading partners directly. However, it supports database integration for managing trading partner information and potentially, a custom front-end system could be developed to facilitate this process.

How is trading partner data managed in PilotFish without a built-in UI?

In PilotFish, trading partner data is managed through environment properties or by interfacing with a database via JDBC. This setup enables dynamic management and adjustments of data based on specific conditions.

If you have any additional questions or require further assistance, please don’t hesitate to contact our customer support team. Click on the button or jump into a chat.

X12, chartered by the American National Standards Institute for more than 35 years, develops and maintains EDI standards and XML schemas.
HL7®, HEALTH LEVEL SEVEN®, CCD®, CDA®, and FHIR® are trademarks of Health Level Seven International.

This is a unique website which will require a more modern browser to work! Please upgrade today!