PilotFish Product Frequently Asked Questions

1. Is there any software that lets you integrate systems, applications and databases with different data formats?

Yes, middleware software such as PilotFish’s integration engine allows you to integrate systems, applications, databases and equipment, using any data format to any other kind of system or data format. (HL7, EDI, CDA, FHIR, XML…) PilotFish has the added advantage that users can accomplish this all graphically without any coding or scripting.

2. 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 you 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.

3. 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.

4. 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 your support team for assistance with any technical questions or challenges you encounter during your data conversion projects.

5. 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

6. 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?

7. 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.

8. 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.

9. 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.

10. 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.

11. 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.

12. 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.

13. 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.

14. 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.

15. 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.

16. 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.

17. 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, ACORD, XML and more with over 200+ B2B processors, transports, and listeners included out-of-the-box.

18. 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.

19. 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.

20. 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.

21. 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.

22. 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.

23. 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.