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, ACORD, HIPAA X12 EDI, etc.). Supporting legacy systems as well as the newest technologies is no problem. In fact, PilotFish is the only 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.

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

2. 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 $3800 with a concurrent user license of the eiConsole (IDE) at $375 per month.

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

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

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

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

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

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

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

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

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

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

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

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

15. PilotFish vs MuleSoft, what are the results?

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?

PilotFish vs MuleSoft

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

17. 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 would need to be viewed individually unless configured for aggregated viewing.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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