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.
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. Licensing is based on maximum hardware configuration or on an on-demand model where you only pay for the time you use (similar to the AWS model). A monthly subscription is under $3,450 for a 4 core/16GB hardware configuration.
3. 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.
4. 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.
5. 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?
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.